Re: Nomenclature Question - BEGIN etc.

How about 'contingent blocks', because they are contingent on some event, without having to use the word 'event'. Richard TSa wrote: HaloO, Larry Wall wrote: Hmm, maybe "control event blocks" and "control events", then... I would call them flow blocks because this is where they are called

Re: Nomenclature Question - BEGIN etc.

HaloO, Larry Wall wrote: Hmm, maybe "control event blocks" and "control events", then... I would call them flow blocks because this is where they are called and what they influence: the flow of execution. This nicely matches the flow charts used to describe the control flow. The other term I

Re: Nomenclature Question - BEGIN etc.

On Thu, Apr 10, 2008 at 8:49 PM, Juerd Waalboer <[EMAIL PROTECTED]> wrote: > My suggestion: > > consequential blocks ...which would make other blocks inconsequential? Nuh-uh. -- Mark J. Reed <[EMAIL PROTECTED]>

Re: Nomenclature Question - BEGIN etc.

My suggestion: consequential blocks -- Met vriendelijke groet, Kind regards, Korajn salutojn, Juerd Waalboer: Perl hacker <[EMAIL PROTECTED]> Convolution: ICT solutions and consultancy <[EMAIL PROTECTED]>

Re: Nomenclature Question - BEGIN etc.

On Thu, Apr 10, 2008 at 7:41 PM, Brandon S. Allbery KF8NH <[EMAIL PROTECTED]> wrote: > On the other hand, that may be the answer right there: "when-blocks". We have those already: given...when. -- Mark J. Reed <[EMAIL PROTECTED]>

Re: Nomenclature Question - BEGIN etc.

Brandon S. Allbery KF8NH skribis 2008-04-10 19:41 (-0400): > On the other hand, that may be the answer right there: "when-blocks". No, this is a when block: when /foo/ { ... } :) -- Met vriendelijke groet, Kind regards, Korajn salutojn, Juerd Waalboer: Perl hacker <[EMAIL PROTECTED]

Re: Nomenclature Question - BEGIN etc.

On Apr 10, 2008, at 18:58 , Bob Rogers wrote: From: Larry Wall <[EMAIL PROTECTED]> Date: Thu, 10 Apr 2008 14:00:53 -0700 On Thu, Apr 10, 2008 at 03:41:19PM -0500, John M. Dlugosz wrote: Well, lessee. The Common Lisp spec calls them "situations" in the definition of (eval-when)...

RE: Nomenclature Question - BEGIN etc.

>-Original Message- >From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On >Behalf Of Mark J. Reed >Sent: Thursday, April 10, 2008 4:26 PM >To: [EMAIL PROTECTED]; perl6-language@perl.org >Subject: Re: Nomenclature Question - BEGIN etc. > >but "tag"

Re: Nomenclature Question - BEGIN etc.

From: Larry Wall <[EMAIL PROTECTED]> Date: Thu, 10 Apr 2008 14:00:53 -0700 On Thu, Apr 10, 2008 at 03:41:19PM -0500, John M. Dlugosz wrote: > >> Well, lessee. The Common Lisp spec calls them "situations" in the > definition of (eval-when)... That's not bad. FWIW, eval-when o

Re: Nomenclature Question - BEGIN etc.

On Thu, Apr 10, 2008 at 5:00 PM, Larry Wall <[EMAIL PROTECTED]> wrote: > > >> Well, lessee. The Common Lisp spec calls them "situations" in the > > definition of (eval-when)... > > That's not bad. Oh, sure, ignore it when I first said it, but let John quote me and allasudden it's notable.. :-)

Re: Nomenclature Question - BEGIN etc.

On Thu, Apr 10, 2008 at 03:41:19PM -0500, John M. Dlugosz wrote: > I've consolidated all the discussion into one reply: > > > >> The perldocs call them "Five specially named code blocks", The Camel > names them individually (e.g. BEGIN block). How about phase blocks? They > control in what phase

Re: Nomenclature Question - BEGIN etc.

I've consolidated all the discussion into one reply: >> The perldocs call them "Five specially named code blocks", The Camel names them individually (e.g. BEGIN block). How about phase blocks? They control in what phase of compilation/runtime the code runs in. >> I don't know, "phase" sound

Re: Nomenclature Question - BEGIN etc.

On Thu, Apr 10, 2008 at 04:38:27PM -0400, Brandon S. Allbery KF8NH wrote: > > On Apr 10, 2008, at 13:29 , John M. Dlugosz wrote: > >I might have misremembered, but i thought labels were followed by a > >colon in Perl 6. A quick scan of the docs... " > > > >It is illegal for a provisional subrouti

Re: Nomenclature Question - BEGIN etc.

On Apr 10, 2008, at 13:29 , John M. Dlugosz wrote: I might have misremembered, but i thought labels were followed by a colon in Perl 6. A quick scan of the docs... " It is illegal for a provisional subroutine call to be followed by a colon postfix, since such a colon is allowed only on an indi

Re: Nomenclature Question - BEGIN etc.

On Thu, Apr 10, 2008 at 01:35:57PM -0400, Mark J. Reed wrote: : As I read it, the original question was about the actual keyword - : e.g. the word "BEGIN" - as distinct from the block it's attached to. : Though I agree we need a general term for the latter, the name "event : block" seems to imply t

Re: Nomenclature Question - BEGIN etc.

As I read it, the original question was about the actual keyword - e.g. the word "BEGIN" - as distinct from the block it's attached to. Though I agree we need a general term for the latter, the name "event block" seems to imply that "BEGIN" et al are events, which might be ok or might cause confusi

Re: Nomenclature Question - BEGIN etc.

Mark J. Reed markjreed-at-mail.com |Perl 6| wrote: Now you've lost me. I was pretty sure that was the block name. AIUI, you can give arbitrary names to any block, and these names function the same way (i.e. can be used in flow control statements), but they also happen to control when the block

Re: Nomenclature Question - BEGIN etc.

On Thu, Apr 10, 2008 at 08:52:38AM -0700, jerry gay wrote: : On Wed, Apr 9, 2008 at 10:31 PM, John M. Dlugosz : <[EMAIL PROTECTED]> wrote: : > Consider the words that may be used to introduce a block for a special : > purpose, like : > : > BEGIN : > END : > INIT : > CATCH : > etc. : > : > Wha

Re: Nomenclature Question - BEGIN etc.

On Wed, Apr 9, 2008 at 10:31 PM, John M. Dlugosz <[EMAIL PROTECTED]> wrote: > Consider the words that may be used to introduce a block for a special > purpose, like > > BEGIN > END > INIT > CATCH > etc. > > What do you call those? They are not even "special named blocks" because > that is no

Re: Nomenclature Question - BEGIN etc.

On Thu, Apr 10, 2008 at 2:29 AM, Mark J. Reed <[EMAIL PROTECTED]> wrote: > On Thu, Apr 10, 2008 at 2:26 AM, Chas. Owens <[EMAIL PROTECTED]> wrote: > > It looks like they already have a name in S04: Closure traits*. > > > > * http://dev.perl.org/perl6/doc/design/syn/S04.html#Closure_traits > >

Re: Nomenclature Question - BEGIN etc.

On Thu, Apr 10, 2008 at 2:26 AM, Chas. Owens <[EMAIL PROTECTED]> wrote: > It looks like they already have a name in S04: Closure traits*. > > * http://dev.perl.org/perl6/doc/design/syn/S04.html#Closure_traits I don't know, it seems like any value might happen to both be a closure and have traits

Re: Nomenclature Question - BEGIN etc.

On Thu, Apr 10, 2008 at 2:16 AM, Mark J. Reed <[EMAIL PROTECTED]> wrote: > JMD> Consider the words that may be used to introduce a block for a special > JMD> purpose, like > JMD> > JMD> BEGIN > JMD> END > JMD> INIT > JMD> CATCH > JMD> etc. > JMD> > JMD> What do you call those? > > W

Re: Nomenclature Question - BEGIN etc.

JMD> Consider the words that may be used to introduce a block for a special JMD> purpose, like JMD> JMD> BEGIN JMD> END JMD> INIT JMD> CATCH JMD> etc. JMD> JMD> What do you call those? Well, lessee. The Common Lisp spec calls them "situations" in the definition of (eval-when)... JMD> They

Re: Nomenclature Question - BEGIN etc.

On Thu, Apr 10, 2008 at 1:31 AM, John M. Dlugosz <[EMAIL PROTECTED]> wrote: > Consider the words that may be used to introduce a block for a special > purpose, like > > BEGIN > END > INIT > CATCH > etc. > > What do you call those? They are not even "special named blocks" because > that is no

Nomenclature Question - BEGIN etc.

Consider the words that may be used to introduce a block for a special purpose, like BEGIN END INIT CATCH etc. What do you call those? They are not even "special named blocks" because that is not the block name (that already means something). --John