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

[Nathan Torkington <gnat@frii.com>]

Gurusamy Sarathy writes:
> I wish we could do PARSE::BEGIN, PARSE::END, RUN::BEGIN, and END::RUN
> (or even {BEGIN,END}::{PARSE,RUN}).  Maybe that's what we oughtta
> do.

The discussion on this seems way out of proportion to its importance.

I can't see why STOP/INIT are any worse than READY or the other
suggestions so far.  All require you to know about compile- vs
run-time in order to be used meaningfully, and once you know their
relationship to the compiler, STOP and INIT are no more arbitrary
than any others.

Nat
(If change must happen, though, then I like BEGIN_PARSE END_PARSE
BEGIN_RUN END_RUN because packages have nothing to do with when code
is executed.  The PARSE/RUN dichotomy is simple enough for people to
be taught, and is crucial to understanding how much of Perl works, so
I don't see that as a problem.  BEGIN and END can be grandfathered as
aliases for BEGIN_PARSE and END_RUN)

---

References to:

Damian Conway <damian@cs.monash.edu.au>
Gurusamy Sarathy <gsar@ActiveState.com>

---

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

---