Re: The Perl 6 Summary

2003-07-21 Thread Adam Turoff
On Mon, Jul 21, 2003 at 03:20:26PM +0100, Piers Cawley wrote: > Acknowledgements, Announcements and Apologies > First of all, I plead insanity for my mistake of last week's summary. > PONIE does not stand for 'Perl On New Internal Architecture', it > obviously stands for 'Perl On New Im

Re: Events

2003-07-18 Thread Adam Turoff
On Fri, Jul 18, 2003 at 01:06:03PM -0700, Damien Neil wrote: > Also, given that asynchronous IO is a fairly unpopular programming > technique these days (non-blocking event-loop IO and blocking > threaded IO are far more common), I would think long and hard before > placing support for it as a core

Re: [perl #21668] APL doesn't use sigils

2003-03-25 Thread Adam Turoff
On Tue, Mar 25, 2003 at 09:25:30PM -0500, Benjamin Goldberg wrote: > Adam Turoff wrote: > > On Mon, Mar 24, 2003 at 08:21:51PM -0500, Benjamin Goldberg wrote: > > > And what happens if a programmer wants to have two different > > > variables, of two different types,

Re: [perl #21668] APL doesn't use sigils

2003-03-25 Thread Adam Turoff
On Mon, Mar 24, 2003 at 08:21:51PM -0500, Benjamin Goldberg wrote: > And what happens if a programmer wants to have two different variables, > of two different types, with the same name, such as @data and %data? > > Without sigils, it cannot be done. Vast numbers of C, C++, C#, Java, Python, Lisp

Re: Perl6/Parrot status

2002-02-08 Thread Adam Turoff
On Thu, Feb 07, 2002 at 08:40:41PM -0500, Dan Sugalski wrote: > [...] I'm also trying to get a regular, if I'm > lucky every issue, Parrot/Perl 6 article in The Perl Review. Speaking on behalf of TPR, the only bottleneck here is providing a regular article/update on Parrot/Perl6 for each issue.

Re: Bytecode portablilty

2001-12-10 Thread Adam Turoff
On Sun, Dec 09, 2001 at 07:46:46PM -0500, Bryan C. Warnock wrote: > Proposal: > > For background, revisit my proposed Bytecode Format (v2) at > http:[EMAIL PROTECTED]/msg05640.html. > Although it is outdated, is gives a general gist of the direction of my > thinking. In particular, pay no heed t

Re: Parrot FAQ

2001-12-05 Thread Adam Turoff
On Wed, Dec 05, 2001 at 01:32:32PM -0500, Dan Sugalski wrote: > Right, but FORTH's not an interpreted language, generally speaking. No, but PostScript is. :-) (...as if that wasn't completely obvious...) Z.

Re: Parrot FAQ

2001-12-04 Thread Adam Turoff
On Tue, Dec 04, 2001 at 06:29:34PM -0800, Steve Fink wrote: > On Tue, Dec 04, 2001 at 04:11:58PM -0500, Dan Sugalski wrote: > > Seriously, there are real answers to a whole lot of design questions. Ask > > 'em and I'll get FAQable answers to 'em once and for all. > > Whee! Ok. Some of these are

Re: Parrot FAQ

2001-12-04 Thread Adam Turoff
On Tue, Dec 04, 2001 at 03:26:25PM -0500, Adam Turoff wrote: > Expect another update tonight or tomorrow. Here ya go. Same place as last time. 1 General Questions 1. What is Parrot? 2. Why "Parrot"? 3. Is Parrot the same t

Re: Parrot FAQ

2001-12-04 Thread Adam Turoff
On Tue, Dec 04, 2001 at 03:20:46PM -0600, Jonathan Scott Duff wrote: > On Tue, Dec 04, 2001 at 04:11:58PM -0500, Dan Sugalski wrote: > > Seriously, there are real answers to a whole lot of design questions. Ask > > 'em and I'll get FAQable answers to 'em once and for all. > > Could the FAQ be ma

Parrot FAQ

2001-12-04 Thread Adam Turoff
The beginnings of a Parrot FAQ can be found here: http://www.panix.com/~ziggy/parrot.html It'll be moved to dev.perl.org shortly, when there's more meat to it. Contents: 1 General Questions 1. What is Parrot? 2. Why "Parrot"? 3. Is Parrot th

Re: What is wrong with GCC's register transfer language?

2001-12-03 Thread Adam Turoff
On Mon, Dec 03, 2001 at 09:54:26PM +, Simon Cozens wrote: > On Mon, Dec 03, 2001 at 09:56:50PM +0100, Norbert Bollow wrote: > > Could you please mention the DotGNU project also? We're also building, > > among other things, a C# compiler and CLR runtime. > > I could do, but DotGNU is, as you

Re: What is wrong with GCC's register transfer language?

2001-12-03 Thread Adam Turoff
On Mon, Dec 03, 2001 at 01:20:42PM -0500, Bryan C. Warnock wrote: > On Monday 03 December 2001 12:31 pm, Nathan Torkington wrote: > > Terrence Brannon writes: > > > And then just write a RTL->JVM and RTL->CRL converter? > > > > I think it's time to collet these questions into a FAQ. Any volunteer

Re: basic parrot questions

2001-12-03 Thread Adam Turoff
On Mon, Dec 03, 2001 at 08:31:00AM -0800, Terrence Brannon wrote: > Also, I thought Parrot was not "stack-based" If that is the case > then why does Overview.pod say this: > > "Registers will be stored in register frames, which can be pushed and > popped onto the register stack. For instance, a

Re: RFC archive?

2001-02-20 Thread Adam Turoff
On Tue, Feb 20, 2001 at 04:58:11PM -0800, Matthew Cline wrote: > What's the URL for the RFC archive? http://dev.perl.org/rfc/ Z.

Re: Let's not be C-specific even if we use C (was Re: Meta-design)

2000-12-08 Thread Adam Turoff
On Thu, Dec 07, 2000 at 10:42:31PM -0500, Bradley M. Kuhn wrote: > What I seek is perl design documentation that allows someone to take the set > of PDD's and reimplement perl in another language. What will aid Perl reimplementations are the PDDs. C-Centrism in the PDDs is a moot point. > The

Re: Supporting architectures without native C support (was Re: Meta-design)

2000-12-07 Thread Adam Turoff
On Thu, Dec 07, 2000 at 10:23:55PM -0500, Bradley M. Kuhn wrote: > However, the JVM is a powerful environment for generalized bytecode and for > allowing bytecode of different languages to communicate. So's Microsoft vaporware ".NET platform". And the second version of that bytecoded runtime wi

Re: Proposal for groups

2000-12-05 Thread Adam Turoff
On Tue, Dec 05, 2000 at 08:21:23AM +, Alan Burlison wrote: > How about writing the documents in XML and having a 'perl specification' > DTD? With a bit of careful thought we will be able to do all sorts of > interesting stuff - for example if we tag function definitions we can > start cross-c

Re: Proposal for groups

2000-12-04 Thread Adam Turoff
On Mon, Dec 04, 2000 at 07:56:21AM +, Alan Burlison wrote: > How are you going to publish the design? Asking people to follow email > discussions and try to piece together what is proposed from that doesn't > seem a very optimal way to go about it. How about a design document > (format to be

Re: Guidelines for internals proposals and documentation

2000-11-15 Thread Adam Turoff
On Wed, Nov 15, 2000 at 04:20:58PM -0500, Dan Sugalski wrote: > I want perl 6's internal API to have the same sort of artistic integrity > that the language has. That's not, unfortunately, possible with everyone > having equal say. I'd like it to be otherwise, but that's just not possible > wit

Re: Guidelines for internals proposals and documentation

2000-11-15 Thread Adam Turoff
On Wed, Nov 15, 2000 at 04:42:58PM +, Nicholas Clark wrote: > On Wed, Nov 15, 2000 at 11:35:56AM -0500, Adam Turoff wrote: > > All PDDs (like RFCs) need to start with 'Status: Developing' by default. > > Since statuses like 'Standard', 'Rejected',

Re: Guidelines for internals proposals and documentation

2000-11-15 Thread Adam Turoff
On Tue, Nov 14, 2000 at 05:59:40PM -0500, Dan Sugalski wrote: > 6) Only a WG chair, pumpking, or one of the principals (i.e. Me, Nat, or > Larry, or our replacements) can mark a PDD as developing, standard, or > superceded. This doesn't sound right. All PDDs (like RFCs) need to start with 'Sta

Re: Threaded Perl bytecode (was: Re: stackless python)

2000-10-24 Thread Adam Turoff
On Tue, Oct 24, 2000 at 10:55:29AM -0400, Chaim Frenkel wrote: > I don't see it. > > I would find it extremely akward to allow > > thread 1: *foo = \&one_foo; > thread 2: *foo = \&other_foo; > [...] > > copy the &foo body to a new location. > replace the old

Re: Threaded Perl bytecode (was: Re: stackless python)

2000-10-23 Thread Adam Turoff
On Mon, Oct 23, 2000 at 11:03:12AM -0400, Chaim Frenkel wrote: > >>>>> "AT" == Adam Turoff <[EMAIL PROTECTED]> writes: > AT> It would also mean that if anything was overriden anywhere, no > AT> module code could be read in as bytecode, since it m

Threaded Perl bytecode (was: Re: stackless python)

2000-10-22 Thread Adam Turoff
On Sat, Oct 21, 2000 at 08:59:21AM -0700, Larry Wall wrote: > Joshua N Pritikin writes: > : http://www.oreillynet.com/pub/a/python/2000/10/04/stackless-intro.html > > Perl 5 is already stackless in that sense, though we never implemented > continuations. The main impetus for going stackless was

Re: Perl's parser and lexer will likely be in Perl (was Re: RFC 334 (v1) I'm {STILL} trying to understand this...)

2000-10-17 Thread Adam Turoff
On Tue, Oct 17, 2000 at 08:57:43PM -0400, Dan Sugalski wrote: > On Tue, 17 Oct 2000, Adam Turoff wrote: > > Dammit, I'm not finding the message in the thread, but someone casually > > mentioned writing the important bits of parsing Perl in Perl5, generating > > bytec

Re: Perl's parser and lexer will likely be in Perl (was Re: RFC 334 (v1) I'm {STILL} trying to understand this...)

2000-10-17 Thread Adam Turoff
On Tue, Oct 17, 2000 at 07:18:54PM -0400, Bradley M. Kuhn wrote: > Adam Turoff wrote: > > to write the Perl tokenizer in a Perl[56] regex, which is more easily > > parsable in C. All of a sudden, toke.c is replaced by toke.re, which > > would be much more legible to thi

Re: Perl's parser and lexer will likely be in Perl (was Re: RFC 334 (v1) I'm {STILL} trying to understand this...)

2000-10-17 Thread Adam Turoff
On Tue, Oct 17, 2000 at 06:53:47PM +1100, Jeremy Howard wrote: > Leon Brocard wrote: > > Hmmm, I wonder what kind of subset would be necessary - surely the > > most useful constructs are also the most complicated... > > We could learn quite a bit by looking through the code from > Parse::RecDescen

Re: RFC 227 (v1) Extend the window to turn on taint mode

2000-09-15 Thread Adam Turoff
On Fri, Sep 15, 2000 at 05:04:23PM -0400, Chaim Frenkel wrote: > > "DS" == Dan Sugalski <[EMAIL PROTECTED]> writes: > >> But these all lack command line switches that are passed to perl. > > DS> No, they don't. Not everywhere, certainly. Command-line switches > DS> can be passed to all of 'em

Re: RFC 227 (v1) Extend the window to turn on taint mode

2000-09-15 Thread Adam Turoff
On Fri, Sep 15, 2000 at 01:03:50PM -0400, Dan Sugalski wrote: > At 04:52 AM 9/15/00 -0400, Michael G Schwern wrote: > >On Fri, Sep 15, 2000 at 01:52:00AM -, Perl6 RFC Librarian wrote: > > > =head1 TITLE > > > > > > Extend the window to turn on taint mode > > > >As long as we're talking about t

Re: RFC 227 (v1) Extend the window to turn on taint mode

2000-09-15 Thread Adam Turoff
On Fri, Sep 15, 2000 at 01:04:50PM -0400, Dan Sugalski wrote: > At 01:15 AM 9/15/00 -0400, Adam Turoff wrote: > >On Thu, Sep 14, 2000 at 10:37:40PM -0400, Chaim Frenkel wrote: > > > I vaguely recall when Chip put that in. He worked pretty hard to > > > adjust the comman

Re: RFC 227 (v1) Extend the window to turn on taint mode

2000-09-14 Thread Adam Turoff
On Thu, Sep 14, 2000 at 10:37:40PM -0400, Chaim Frenkel wrote: > I vaguely recall when Chip put that in. He worked pretty hard to > adjust the command line/#! option processing. (Something about > unsafe operations already being done before the script is read.) The crux of my proposal/request is