Re: Declaring a Function Before it is used
On Thu, 30 Oct 2003 13:51:40 -0500, Robert Craig
<rds at RapidEuphoria.com> wrote:
>In practice, people would simply arrange their
>routines in random order, then keep adding
>declarations until the interpreter shuts up.
And if they had no need to add the declarations in the first place?
You are actually admitting here, that this is a problem, and the
second word of your answer is "off", the first being too rude to print
>
>I still think the advantages of
>"define-it-before-you-use-it" outweigh
>the nuisance of occasionally having to copy/paste
OCCASIONALLY?!!!!
Stop thinking about trivial programs.
>a routine to a new place. It may not be desirable
>in *every* program,
This happens in EVERY program over a few thousand lines.
>but when people know there are
>no exceptions to this rule,
If you are adamant on that, allow "forward func/proc xxx(whatever)".
Personally, I believe you don't _have_ to do it that way, but as Irv
said, it that's your philosophical requirement, so be it.
What you have now does not make people happy.
>it promotes the
>readability and maintainability of Euphoria
>programs in general.
Don't believe you could show even one case where that last statement
is true.
Pete
|
Not Categorized, Please Help
|
|
