Re: Resurection of routine_id forward referencing
>
>
> > For myself, I would like have the ability to code things in the
> > order that I prefer - not the order that someone else decides is
> > good coding practice. Its the euphoria parsers job to figure it out
> > - if that means multiple passes through the code then so be it. You
> > can code the way you want - lets allow everyone that same liberty.
> >
> > If my code is not pretty for someone else, too bad. Unless the
> > someone else is paying for my code and has stipulated the style up
> > front - again, too bad. I code things to get something done, not to
> > teach coding style, so will code in the way that makes the most
> > sense for me.
>
> Euphoria is designed to be interpreted from top to bottom. Any given
> line of code may only reference code above it, not below. That is
> simply how Euphoria operates. Top-to-bottom. If a line of code can
> reference code below it, then this goes against how Euphoria operates.
> That is why Rob considered it a bug and chose to not allow it.
>
> If the current Euphoria code functionality doesn't comply with how you
> code, then perhaps Euphoria isn't for you. It makes one pass over the
> code and begins executing it from the beginning and stops at the
> bottom.
The interpreter can still make only one pass thru before execution,
and have forward referencing. I've suggested how to do this before:
if it's not resolved as a backwards reference, place it in a que, then
at the end attempt to resolve the que, when done resolving, dump
the que to the .err file.
Water is a option in lakes, but as people drown in it, i think it
should not be an option. Sheesh.
Kat
|
Not Categorized, Please Help
|
|
