Re: Are STOP and INIT good names? (was Re: [PATCH pod/perlmod.pod 5.005_63] Special Blocks For Less Than Gurus)

[Gurusamy Sarathy <gsar@ActiveState.com>]

On Mon, 24 Jan 2000 12:06:42 PST, Larry Wall wrote:
>damian@conway.org writes:
>: Sarathy wrote:
>: 
>:    > I'd agree that STOP is not exactly as enlightening as
>:    > RUN_WHEN_COMPILATION_STOPS().  If you get any better ideas, let me know.
>: 
>: I think:
>: 
>: 	BEGIN	# Begin processing
>: 	READY	# Ready to run (must have finished processing to be ready)
>: 	INIT	# Initializing (must be running to initialize)
>: 	END	# End of execution (and complements BEGIN)
>: 
>: is the best set yet proposed.
>: 
>: Unlike other suggestions, it has a sequence whose logic is explicable to
>: non-gurus (therefore more likely to be correctly remembered by them).
>: How one would remember that STOP (or DOZE) comes between BEGIN and INIT is
>: beyond me.
>
>That's fine too.  Though, of course, the point of the typical READY
>block would be that it isn't really ready unless we do something else.

FWIW, I don't really like READY because of the above.  And probably because
it only makes sense when read as a verb (at least in my head).

I like DONE (as in "done with compilation"), which hasn't been proposed
yet, and which conveys the meaning that these things are a finishing point
for compilation, not a starting point for execution (which is what INIT is).

    BEGIN
    DONE
    INIT
    END

So, how about it?


Sarathy
gsar@ActiveState.com

---

Follow-Ups from:

Nick Ing-Simmons <nik@tiuk.ti.com>

References to:

Larry Wall <larry@wall.org>

---

[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index][Thread Index][Top&Search][Original]

---