Re: Backtracking through the source

2000-11-30 Thread David Grove
then... "either in perl, or in C" better? >From my understanding, "API" is the set of functions internal to Perl and PerlXS that allow C to access Perl internal structures, functions, etc., for the purpose (or effect) of "writing" "Perl" in "C" (SvPV(whatsis)). I'm talking about either writing i

Re: Backtracking through the source

2000-11-30 Thread Simon Cozens
On Thu, Nov 30, 2000 at 05:07:32AM +, David Grove wrote: > >From my understanding, "API" is the set of functions internal to Perl and > PerlXS that allow C to access Perl internal structures, functions, etc., > for the purpose (or effect) of "writing" "Perl" in "C" (SvPV(whatsis)). Uhm, no. A

Re: Backtracking through the source

2000-11-30 Thread David Grove
Simon Cozens <[EMAIL PROTECTED]> wrote: > On Thu, Nov 30, 2000 at 05:07:32AM +, David Grove wrote: > > >From my understanding, "API" is the set of functions internal to Perl > and > > PerlXS that allow C to access Perl internal structures, functions, etc., > > for the purpose (or effect

Re: Backtracking through the source

2000-11-30 Thread Simon Cozens
On Thu, Nov 30, 2000 at 11:54:31AM +, Simon Cozens wrote: > I categorically do *NOT* want perl6-internals to turn into a basic course in > compiler design, purely for the benefit of those who know nothing at all about > what they're trying to achieve. I'd like Perl 6 to be a masterwork, and >

Re: The external interface for the parser piece

2000-11-30 Thread Damien Neil
On Mon, Nov 27, 2000 at 05:29:36PM -0500, Dan Sugalski wrote: >int perl6_parse(PerlInterp *interp, >void *source, >int flags, >void *extra_pointer); Count me in with the people who prefer: int perl6_parse(PerlInterp *interp, Perl

Re: Backtracking through the source

2000-11-30 Thread Simon Cozens
On Wed, Nov 29, 2000 at 02:57:23PM -0500, Dan Sugalski wrote: > My only worry is, how do we reconcile this with the idea of > >Perl having an easily modifiable grammar and being a good environment for > >little-language stuff? > > That's a good question, and it depends on what Larry's thinking o

Re: Backtracking through the source

2000-11-30 Thread David Grove
It can be done any which way but loose, and I'm trying to keep my thinking flexible for any applied use in this sense. What I'm _doing_ for my own work at this point is simply making a creole filter (or source filter), and spitting out perl5 which is then sucked into eval_pv(). For this, I'd proba

Re: Backtracking through the source

2000-11-30 Thread Simon Cozens
On Thu, Nov 30, 2000 at 03:30:28AM +, David Grove wrote: > For this, I'd probably look for it to be writable either in perl or in api You keep using that word. I do not think it means what you think it means. -- Pray to God, but keep rowing to shore. -- Russian Proverb

Re: Backtracking through the source

2000-11-30 Thread Andy Dougherty
On Thu, 30 Nov 2000, Bryan C. Warnock wrote: > You don't want the compiler design to be a 'hands-on experiment' for us > inexperienced folk? That's not elitist, that's pragmatic. > > You don't want this to be a learning experience - (corrections, observations, > answers) - to the same? *That's

Re: The external interface for the parser piece

2000-11-30 Thread Dave Storrs
On Wed, 29 Nov 2000, Dan Sugalski wrote: > At 09:51 AM 11/29/00 -0800, Dave Storrs wrote: > >I have a feeling this is a stupid question, but I have to ask anyway. > > > >Do we really need to pass in a PerlInterp pointer? Or can perl6_parse > >just create one for itself if/when it needs one? I

Re: Backtracking through the source

2000-11-30 Thread Bryan C. Warnock
On Thu, 30 Nov 2000, Andy Dougherty wrote: > On Thu, 30 Nov 2000, Bryan C. Warnock wrote: > > > You don't want the compiler design to be a 'hands-on experiment' for us > > inexperienced folk? That's not elitist, that's pragmatic. > > > > You don't want this to be a learning experience - (correc

Re: The external interface for the parser piece

2000-11-30 Thread Dan Sugalski
At 07:29 AM 11/30/00 -0800, Dave Storrs wrote: >On Wed, 29 Nov 2000, Dan Sugalski wrote: > > > At 09:51 AM 11/29/00 -0800, Dave Storrs wrote: > > >I have a feeling this is a stupid question, but I have to ask anyway. > > > > > >Do we really need to pass in a PerlInterp pointer? Or can perl6_par

Re: Backtracking through the source

2000-11-30 Thread Bryan C. Warnock
On Thu, 30 Nov 2000, Simon Cozens wrote: > On Thu, Nov 30, 2000 at 11:54:31AM +, Simon Cozens wrote: > > I categorically do *NOT* want perl6-internals to turn into a basic course in > > compiler design, purely for the benefit of those who know nothing at all about > > what they're trying to ac

Re: The external interface for the parser piece

2000-11-30 Thread Nicholas Clark
On Tue, Nov 28, 2000 at 04:47:42PM -0500, Dan Sugalski wrote: > At 09:05 PM 11/28/00 +, Nicholas Clark wrote: >>On Tue, Nov 28, 2000 at 03:35:37PM -0500, Dan Sugalski wrote: Not sure: Dan: > is treated as if it points to a stream of bytes, where the first four are > the length o

Re: The external interface for the parser piece

2000-11-30 Thread Jarkko Hietaniemi
On a related note: a wrapper not completely unlike union sv_any_aligned_s { IV iv; NV iv; PV pv; void *vp; int (*dummy)(void) *fp; /* any others? */ }; should be used around SVs to ascertain that everything fits everywhere. -- $jhi++; # http://ww

Re: The external interface for the parser piece

2000-11-30 Thread Nick Ing-Simmons
Nicholas Clark <[EMAIL PROTECTED]> writes: >> Counted strings should probably just have either a platform-native int in >> front, or a 32-bit int in network format, both of which should be doable on >> any platform that perl deals with. > >I agree it's do-able. >What seems to me a good idea not

Re: The external interface for the parser piece

2000-11-30 Thread Nick Ing-Simmons
Nicholas Clark <[EMAIL PROTECTED]> writes: > >We're trying to make this an easy embedding API. Yes, and we are in danger of "premature optimization" of the _interface_. What we need to start with is a list of "what we need to know" - they may as well be separate parameters at this point - the

Re: The external interface for the parser piece

2000-11-30 Thread Jarkko Hietaniemi
On Thu, Nov 30, 2000 at 10:03:06AM -0600, Jarkko Hietaniemi wrote: > On a related note: a wrapper not completely unlike > > union sv_any_aligned_s { > IV iv; > NV iv; > PV pv; > void *vp; > int (*dummy)(void) *fp; > /* any others? */ > }; > > should be used ar

Re: The external interface for the parser piece

2000-11-30 Thread Dan Sugalski
At 10:20 AM 11/30/00 -0600, Jarkko Hietaniemi wrote: >On Thu, Nov 30, 2000 at 10:03:06AM -0600, Jarkko Hietaniemi wrote: > > On a related note: a wrapper not completely unlike > > > > union sv_any_aligned_s { > > IV iv; > > NV iv; > > PV pv; > > void *vp; > > int (*du

Re: Backtracking through the source

2000-11-30 Thread Dan Sugalski
At 05:07 AM 11/30/00 +, David Grove wrote: >Dan: In any PDD generated from this group, we really need to define for >the "semantically challenged" the terms that are used within it: No, I don't think that's appropriate. Any new terminology specific to the PDD should be defined, but that's it

Re: The external interface for the parser piece

2000-11-30 Thread Jarkko Hietaniemi
On Thu, Nov 30, 2000 at 11:23:11AM -0500, Dan Sugalski wrote: > At 10:20 AM 11/30/00 -0600, Jarkko Hietaniemi wrote: > >On Thu, Nov 30, 2000 at 10:03:06AM -0600, Jarkko Hietaniemi wrote: > > > On a related note: a wrapper not completely unlike > > > > > > union sv_any_aligned_s { > > > IV iv

Re: The external interface for the parser piece

2000-11-30 Thread Dan Sugalski
At 10:54 AM 11/30/00 -0600, Jarkko Hietaniemi wrote: >On Thu, Nov 30, 2000 at 11:23:11AM -0500, Dan Sugalski wrote: > > At 10:20 AM 11/30/00 -0600, Jarkko Hietaniemi wrote: > > >On Thu, Nov 30, 2000 at 10:03:06AM -0600, Jarkko Hietaniemi wrote: > > > > On a related note: a wrapper not completely u

Re: The external interface for the parser piece

2000-11-30 Thread Jarkko Hietaniemi
> > > Huh? You're not talking about using this union around, say, the IV slot in > > > a scalar, I hope... > > > >You hope in vain :-) If we still want to in perl6 to do (disgusting) > >things like (we do in perl5) > > > > - "intercast" pointers and integers > > - "intercast" integ

Re: Backtracking through meta swamp

2000-11-30 Thread Joshua N Pritikin
On Thu, Nov 30, 2000 at 08:33:35AM -0500, [EMAIL PROTECTED] wrote: > "Bryan C. Warnock" <[EMAIL PROTECTED]> wrote: > > On Thu, 30 Nov 2000, Simon Cozens wrote: > > > On Thu, Nov 30, 2000 at 11:54:31AM +, Simon Cozens wrote: > > > > I categorically do *NOT* want perl6-internals to turn into

Re: Opcodes (was Re: The external interface for the parser piece)

2000-11-30 Thread Dan Sugalski
At 05:59 PM 11/30/00 +, Nicholas Clark wrote: >On Thu, Nov 30, 2000 at 12:46:26PM -0500, Dan Sugalski wrote: > > (Moved over to -internals, since it's not really a parser API thing) > > > > At 11:06 AM 11/30/00 -0600, Jarkko Hietaniemi wrote: > > >Presumably. But why are you then still talkin

Re: Opcodes (was Re: The external interface for the parser piece)

2000-11-30 Thread Dan Sugalski
At 01:51 PM 11/30/00 -0500, Buddha Buck wrote: >At 05:59 PM 11-30-2000 +, Nicholas Clark wrote: >>On Thu, Nov 30, 2000 at 12:46:26PM -0500, Dan Sugalski wrote: > >(Note, Dan was writing about "$a=1.2; $b=3; $c = $a + $b") > >>$a=1; $b =3; $c = $a + $b >> >> >> > If they don't exist already, th

Re: Opcodes (was Re: The external interface for the parser piece)

2000-11-30 Thread Buddha Buck
At 02:27 PM 11-30-2000 -0500, Dan Sugalski wrote: >At 05:59 PM 11/30/00 +, Nicholas Clark wrote: >>On Thu, Nov 30, 2000 at 12:46:26PM -0500, Dan Sugalski wrote: >> > (Moved over to -internals, since it's not really a parser API thing) >> > >> > At 11:06 AM 11/30/00 -0600, Jarkko Hietaniemi wro

Re: Opcodes (was Re: The external interface for the parser piece)

2000-11-30 Thread Chaim Frenkel
> "DS" == Dan Sugalski <[EMAIL PROTECTED]> writes: >> The "add" op would, in C code, do something like: >> >> void add() { >> P6Scaler *addend; >> P6Scaler *adder; >> >> addend = pop(); adder = pop(); >> push addend->vtable->add(addend, adder); >> } >> >> it would be up to the addend->vta

Opcodes (was Re: The external interface for the parser piece)

2000-11-30 Thread Dan Sugalski
(Moved over to -internals, since it's not really a parser API thing) At 11:06 AM 11/30/00 -0600, Jarkko Hietaniemi wrote: >Presumably. But why are you then still talking about "the IV slot in >a scalar"...? I'm slow today. Show me how > > $a = 1.2; $b = 3; $c = $a + $b; > >is going to

Re: Opcodes (was Re: The external interface for the parser piece)

2000-11-30 Thread Nicholas Clark
On Thu, Nov 30, 2000 at 12:46:26PM -0500, Dan Sugalski wrote: > (Moved over to -internals, since it's not really a parser API thing) > > At 11:06 AM 11/30/00 -0600, Jarkko Hietaniemi wrote: > >Presumably. But why are you then still talking about "the IV slot in > >a scalar"...? I'm slow today.

Re: Opcodes (was Re: The external interface for the parser piece)

2000-11-30 Thread David Mitchell
Nicholas Clark <[EMAIL PROTECTED]> wrote: > It looks to me like add needs to be polymorphic and work out the best > compromise for the type of scalar to create based on the integer/num/ > complex/oddball types of its two operands. > > [Oh. but I'm blinkered in this because I'm attempting to make

Re: Opcodes (was Re: The external interface for the parser piece)

2000-11-30 Thread Buddha Buck
At 05:59 PM 11-30-2000 +, Nicholas Clark wrote: >On Thu, Nov 30, 2000 at 12:46:26PM -0500, Dan Sugalski wrote: (Note, Dan was writing about "$a=1.2; $b=3; $c = $a + $b") >$a=1; $b =3; $c = $a + $b > > > > If they don't exist already, then something like: > > > > newscalar a, n

Re: The external interface for the parser piece

2000-11-30 Thread Tim Bunce
On Thu, Nov 30, 2000 at 04:15:24PM +, Nick Ing-Simmons wrote: > Nicholas Clark <[EMAIL PROTECTED]> writes: > > > >We're trying to make this an easy embedding API. > > Yes, and we are in danger of "premature optimization" of the _interface_. Amen. Tim.

Re: The external interface for the parser piece

2000-11-30 Thread Chaim Frenkel
> "JH" == Jarkko Hietaniemi <[EMAIL PROTECTED]> writes: JH> On a related note: a wrapper not completely unlike JH> union sv_any_aligned_s { JH> IV iv; JH> NV iv; JH> PV pv; JH> void *vp; JH> int (*dummy)(void) *fp; JH> /* any others? */ JH> }; JH> should be used aroun

Perl apprenticing (was Re: Backtracking through the source)

2000-11-30 Thread Dan Sugalski
At 01:23 PM 11/30/00 -0500, Buddha Buck wrote: >At 11:47 AM 11-30-2000 -0500, Bryan C. Warnock wrote: >>I forget who proposed it originally, but I thought it an excellent >>analogy, and >>an excellent model for Perl development. Like any tradecraft, there are >>masters, apprentices, and the comm

Re: Backtracking through the source

2000-11-30 Thread David Grove
Simon Cozens <[EMAIL PROTECTED]> wrote: > On Thu, Nov 30, 2000 at 11:54:31AM +, Simon Cozens wrote: > > I categorically do *NOT* want perl6-internals to turn into a basic > course in > > compiler design, purely for the benefit of those who know nothing at all > about > > what they're t

Re: Backtracking through the source

2000-11-30 Thread David Grove
"Bryan C. Warnock" <[EMAIL PROTECTED]> wrote: > On Thu, 30 Nov 2000, Simon Cozens wrote: > > On Thu, Nov 30, 2000 at 11:54:31AM +, Simon Cozens wrote: > > > I categorically do *NOT* want perl6-internals to turn into a basic > course in > > > compiler design, purely for the benefit of tho

Re: Backtracking through the source

2000-11-30 Thread Dan Sugalski
At 10:07 AM 11/30/00 -0500, Andy Dougherty wrote: >On Thu, 30 Nov 2000, Bryan C. Warnock wrote: > > > You don't want the compiler design to be a 'hands-on experiment' for us > > inexperienced folk? That's not elitist, that's pragmatic. > > > > You don't want this to be a learning experience - (co

Re: Perl apprenticing (was Re: Backtracking through the source)

2000-11-30 Thread Bryan C. Warnock
On Thu, 30 Nov 2000, Dan Sugalski wrote: > At 01:23 PM 11/30/00 -0500, Buddha Buck wrote: > >Here here! Is there a place where PAWB's can sign up? > > Not at the moment, at least not formally. Want to set something up? (And > yes, I'm serious. A good master/apprentice thing would help a lot of

Re: Perl apprenticing (was Re: Backtracking through the source)

2000-11-30 Thread Casey R. Tweten
Today around 2:12pm, Dan Sugalski hammered out this masterpiece: : At 01:23 PM 11/30/00 -0500, Buddha Buck wrote: : > : >Here here! Is there a place where PAWB's can sign up? : : Not at the moment, at least not formally. Want to set something up? (And : yes, I'm serious. A good master/apprenti

Re: Backtracking through the source

2000-11-30 Thread Bryan C. Warnock
On Thu, 30 Nov 2000, Dan Sugalski wrote: > What we're doing is *designing* the building. A more appropriate analogy is > one where you walk into the architect's conference room and start > commenting on and fiddling with the design of the building. While the sign > says "Open Meeting", the expe

Re: Backtracking through the source

2000-11-30 Thread Buddha Buck
At 11:47 AM 11-30-2000 -0500, Bryan C. Warnock wrote: >I forget who proposed it originally, but I thought it an excellent >analogy, and >an excellent model for Perl development. Like any tradecraft, there are >masters, apprentices, and the common consumer. The apprentice shouldn't >master, just

Want to help.

2000-11-30 Thread Filipe Brandenburger
Hello. I'm a CS student in Brazil, I'm almost done with my CS course, I like Perl very much and I would like to help in the Perl 6 effort, specifically with Perl/C/C++ programming, and if there's some OS specific thing for me to do, in Linux. If possible, I would like to work closely to data