Re: Euphoria features
On Mon, 15 Nov 1999 07:11:52 -0500, Irv Mullins <irv at ELLIJAY.COM> wrote:
>----- Original Message -----
>From: Everett Williams <rett at GVTC.COM>
>To: <EUPHORIA at LISTSERV.MUOHIO.EDU>
>Sent: Monday, November 15, 1999 3:10 AM
>Subject: Re: Euphoria features
>
>
><snip>
>> Also, in Euphoria, I would like to know where
>> to you would go. The only thing that resembles a label or address in
>> Euphoria is a procedure name. If you goto a procedure, where will you
>> return to. If you goto a function name to whom will you return the value
>> and where will you return to. It appears that Euphoria was designed
>> to be goto proof. Now, we need not only goto's, but labels.
>
>Well of course we need labels. How else will I be able to write wonderful,
>meaningful, bugfree, useful code like:
>PERFORM LBL2X4 THRU LBL4X5 VARYING X BY 6
>
>Regards,
>Irv
Irv,
Just remember that when that showed up in COBOL, it was meant to
replace the goto for all except the most extreme circumstances. Fortran
at the time had no easy way to return from a routine to where that routine
had been called from unless the routine was made external, separately
compiled, and linked or dynamically called. The THRU created really
nasty order dependencies, so moving a routine became hazardous. We
recommended that programmers put a label at the beginning of a routine
and one at it's end with block coding style(we already had the example
of ALGOL...I think, the first block coded language). We allowed no
further branching outside that block and no code was allowed to flow
THRU a block. The block had to be performed. Still, in all a major
improvement over FORTRAN.
Everett L.(Rett) Williams
rett at gvtc.com
|
Not Categorized, Please Help
|
|
