Re: Towards 0.1.1 - timetable

2004-10-05 Thread Gregory Keeney
Ultramarine Lorikeet. No reason in particular. I just like saying "ultramarine". Gregory Keeney (Mmm... "ultramarine"... )

Re: This week's summary

2004-09-13 Thread Gregory Keeney
The Perl 6 Summarizer wrote: Namespaces (Am I the only person who wants to repeat Namespaces! with the same intonation used for 'Monorail!' in the Simpsons?) Not any more...

Re: Probing for Configurations

2004-09-09 Thread Gregory Keeney
getting a whole lot out of the target. You could write the results in memory and then dump it, but ... well, it seems simpler to hand supply the config information. Trying to get answers from an embedded target is tricky and sometimes even potentially dangerous. Gregory Keeney Thomas Seiler

Probing for Configurations

2004-09-08 Thread Gregory Keeney
volved) for Parrot â that may be more work than it is worth, however. I dug down in there once. It's kind of scary. I feel like I am missing something here, but I am not sure whatâ Gregory Keeney

Re: Config parameter files

2004-09-08 Thread Gregory Keeney
Dan Sugalski wrote: The only problem I can forsee when doing cross-compilation is in the building of the library files. Parrot itself... no big. We build miniparrot for the platform you're on, then use the config file to rebuild for the target platform. That part works out OK, but the resulting

Re: No Autoconf, dammit!

2004-09-08 Thread Gregory Keeney
Larry Wall wrote: In principle, cross-compile configuration is drop-dead easy. All you need is a database of what the probe program *would* have answered had you been able to run it on the other machine. (Getting someone to write that database entry for you is the tricky part.) You also have to

Re: No Autoconf, dammit!

2004-09-08 Thread Gregory Keeney
Herbert Snorrason wrote: I suggest we institute a "Rule One" for Dan. (And number two, too, while we're at it.) It'd be easier that way. Ooh, ooh, I know, I know! Rule Number One: â No one wants the â [interrobang if your email client or font doesn't like utf-8] Rule Number Two:" â Dan ge

Re: No Autoconf, dammit!

2004-09-08 Thread Gregory Keeney
uiet nasty. Frameworked properly, however, such a script could work both for unknown and known targets. (Robert is likely screaming: "Your re-inventing autoconf!!!") Gregory Keeney

Re: Current state?

2004-09-08 Thread Gregory Keeney
Patrick R. Michaud wrote: We're in the beginning stages of building a basic perl 6 grammar engine (i.e., probably without p6 closures) that compiles to parrot and handles basic optimizations. Concurrent with that I'm working on a Perl 6 grammar. Where can one get a look at these wonderful thin

Re: Bundles

2004-09-07 Thread Gregory Keeney
ch sense (writing device drivers messes with your head).) Gregory Keeney

Re: Bundles

2004-09-07 Thread Gregory Keeney
l be willing to look it over before I post it; he is good with this kind of stuff.) Gregory Keeney

Re: Bundles

2004-09-07 Thread Gregory Keeney
not always desirable (especially if you want to be able to alter the resource files on the fly). and as you say all this really isn't about perl 6 the language. Nicholas Clark Thus, I reply to perl6-compiler. Gregory Keeney

Re: Bundles

2004-09-07 Thread Gregory Keeney
despite its utility â I cannot (quite) justify the cost. Application distribution is a pain. Let's make Perl application distribution easier. Gregory Keeney