debugging program using GOTO heavily

#1

LOOP
BEGIN

GOTO INSERTREC
......

GOTO UPDATEREC
......

GOTO DONEXTREC
......

<<INSERTREC>>
....
NULL;

<<UPDATEREC>>
.....
NULL;

<<DONEXTREC>>
.....
NULL

END;

? WHEN PROCEDURE BRANCHES TO <<INSERTREC>> will the code in UPDATEREC
and Get executed unless i explicitly tell it to GOTO DONEXTREC

#2

Try it. Put a dbms_output after every goto label and see what gets
executed.

Regards
/Rauf

#3

"seanj" <seanjones (AT) optonline (DOT) net> wrote

Quote:

LOOP
BEGIN

GOTO INSERTREC
.....

GOTO UPDATEREC
.....

GOTO DONEXTREC
.....

INSERTREC
...
NULL;

UPDATEREC
....
NULL;

DONEXTREC
....
NULL

END;

? WHEN PROCEDURE BRANCHES TO <<INSERTREC>> will the code in UPDATEREC
and Get executed unless i explicitly tell it to GOTO DONEXTREC

avoid GOTO at all costs -- it always leads to poorly structured code

specific to your question, GOTO is not like a CASE or SWITCH statement (CASE
is supported in 9i, it would be a good alternative to GOTO) -- once PL/SQL
'goes to' there is no lingering or implied effect... code is processed
sequentially until another control structure is reached

++ mcs

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

debugging program using GOTO heavily

comp.databases.oracle.misc comp.databases.oracle.misc

debugging program using GOTO heavily - 12-13-2004 , 10:52 AM

Re: debugging program using GOTO heavily - 12-13-2004 , 02:58 PM

Re: debugging program using GOTO heavily - 12-13-2004 , 06:55 PM