Proposed sublist: flowcontrol

[skud]

I propose a sublist, perl6-language-flowcontrol, to discuss the
following:

- case/switch
- uri's looping stuff
- anything else related to flow control, from a language perspective

Let me know what you think or if you're interested in chairing this group
(uri? sounds like your kind of thing?)

K.


-- 
Kirrily Robert -- [EMAIL PROTECTED] -- http://netizen.com.au/
Open Source development, consulting and solutions
Level 10, 500 Collins St, Melbourne VIC 3000
Phone: +61 3 9614 0949  Fax: +61 3 9614 0948  Mobile: +61 410 664 994

Re: Proposed sublist: flowcontrol

[skud]

On Fri, Aug 04, 2000 at 01:07:07PM -0400, Uri Guttman wrote:

i like perl6-language-flow better.

Yeah, so do I.  I did wonder whether maybe it wasn't clear enough,
though.

  s - case/switch
try/catch

Any thoguhts on the errors sublist? should this be there, or in -flow,
or what?

/me takes 1 step forward.

anyone want to co-chair this? it will be a noisy group i expect and we
will be forking off many sublists quickly..

Can we predict any of these potential sublists?  Or rather,
sub-sublists.

My guess is that exceptions and case/switch will be the noisy ones.

K.

-- 
Kirrily Robert -- [EMAIL PROTECTED] -- http://netizen.com.au/
Open Source development, consulting and solutions
Level 10, 500 Collins St, Melbourne VIC 3000
Phone: +61 3 9614 0949  Fax: +61 3 9614 0948  Mobile: +61 410 664 994

Re: Proposed sublist: flowcontrol

[Damian Conway]

 i think damian's influence on perl6
 is our real triple top secret weapon. 

This realization has hit me on the head really hard.
My prediction is that Perl6 will have to be dual-credited.

I doubt it: Lucifer doesn't get a by-line on the Bible.

There's only one Larry. 
We're just fortunate that he's a sufficiently large value of one.

Damian

Re: Proposed sublist: flowcontrol

[Uri Guttman]

 "s" == skud  [EMAIL PROTECTED] writes:

  s On Fri, Aug 04, 2000 at 01:07:07PM -0400, Uri Guttman wrote:

  s - case/switch
   try/catch

  s Any thoguhts on the errors sublist? should this be there, or in -flow,
  s or what?

  s Can we predict any of these potential sublists?  Or rather,
  s sub-sublists.

  s My guess is that exceptions and case/switch will be the noisy ones.

exceptions will be loud. i think damian's switch solution is so good and
perlish, it will be a quiet victory. i think damian's influence on perl6
is our real triple top secret weapon. i thank $DEITY every day he is
working for the forces of good (perl) and not evil (pick one or more of:
@other_languages).

here are some immediate sublists i can envision (all below
perl6-language-flow):


errors  - exception handling, $!, $?, return val of system(), etc.

subs- all aspects of sub and method calls: named params,
  prototypes, want, etc.

some of those subs sub list have been proposed as new ones. i think they
should go under this parent list like perl6-language-flow-subs-want. BTW i do
wish we had picked lang instead of language. laziness, you know is an
positive attribute!

switch  - the usual suspects

dispatch- discuss support of the multiple ways to control
  dispatching of perl ops (event loops, threads,
  co-routines, etc.)

the dispatch list should eventually split off lists that focus on the semantic
details of each technology. the final RFCs from those lists will be
coordinated and hopefully presented as a unified design of the control
flow of Perl.

i think a very clean spec which encompasses all of our needs will be
doable. we just have to make the language features which support them as
perlish as possible. the major goal of this group is to create a clean
model of perl flow that can use any or all of the desired features with
no major performance penalties.

uri

-- 
Uri Guttman  -  [EMAIL PROTECTED]  --  http://www.sysarch.com
SYStems ARCHitecture, Software Engineering, Perl, Internet, UNIX Consulting
The Perl Books Page  ---  http://www.sysarch.com/cgi-bin/perl_books
The Best Search Engine on the Net  --  http://www.northernlight.com