Dan Sugalski wrote:
>
> 'Kay, here's the preliminary assembly-level docs for keys, which is how
> we're going to be accessing entries in aggregates.
>
> --Snip here---
> =head2 Key operations
>
> Keys are used to get access to individual elements of an aggregate
> variab
On Tue, Dec 04, 2001 at 10:45:53PM -0500, Adam Turoff wrote:
> 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 FAQab
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
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 probably duplicates, and some
inappropriate for a Parrot FAQ, but:
Q:
On Tue, Dec 04, 2001 at 04:27:22PM -0500, Adam Turoff wrote:
> Besides, Schwern is having no end of problems with the Perl QA
> wiki. I'd much rather put the docs in CVS later this week.
Actually, I make a lot more noise than I'm actually having trouble.
With the exception of that one big glitch
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 thing as Perl6?
4
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
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 made a wiki so that others can play too?
-Scott
--
Jonathan Scott Duff
[EMAIL P
At 04:07 PM 12/4/2001 -0500, Nguon Hao Ching wrote:
>Here's one more:
>
>Q: How does Dan know so much?
>A: Quiet, You.
Now, now, that's not nice. :) Besides, it's:
Q: How come you know all these answers?
A: I wrote the questions. It's easy that way.
Seriously, there are real answers to a
Here's one more:
Q: How does Dan know so much?
A: Quiet, You.
-Hao
At 03:26 PM 12/4/2001 -0500, Adam Turoff wrote:
>The beginnings of a Parrot FAQ can be found here:
Here's some more:
Q: What language is Parrot written in?
A: C
Q: For the love of god, man, why?!?!?!?
A: Because it's the best we've got.
Q: That's sad
A: So true. Regardless, C's available prett
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
Folks,
We're nailing down the license finally for Parrot, and should have things
set. Until then...
DO NOT SUBMIT CODE THAT ISN'T YOURS!
This *includes* from perl 5. (Like, say, the code in utf8.[ch]) If you
didn't write it, or did but don't want to abide by the bits about licensing
in the R
On Tuesday 04 December 2001 01:32 pm, Andy Dougherty wrote:
> On Tue, 4 Dec 2001, Dan Sugalski wrote:
> > Okay, here's the decree.
> >
> > FP constants in the bytecode file constants section will be 64-bit IEEE
> > floats.
>
> You mean something like this?
> -prompt("And your floats?", 'nv');
> +
At 01:32 PM 12/4/2001 -0500, Andy Dougherty wrote:
>On Tue, 4 Dec 2001, Dan Sugalski wrote:
>
> > Okay, here's the decree.
> >
> > FP constants in the bytecode file constants section will be 64-bit IEEE
> floats.
>
>You mean something like this?
Nope. :)
The floating-point tyoe can be larger th
On Tue, 4 Dec 2001, Dan Sugalski wrote:
> Okay, here's the decree.
>
> FP constants in the bytecode file constants section will be 64-bit IEEE floats.
You mean something like this?
--- parrot/Configure.pl Sun Dec 2 00:06:30 2001
+++ parrot-andy/Configure.plTue Dec 4 13:22:31 2001
@@ -60,
Okay, here's the decree.
FP constants in the bytecode file constants section will be 64-bit IEEE floats.
The Q&A as to why. (This'll be a new feature for all the declarations of
arbitrary decisions)
-
Q: Why?
A: Gotta have somethin
[Tue, Dec 04, 2001 at 08:37:36AM -0500: Andy Dougherty]
> My cvs repository contained a file t/op/pmc.t. However, that files isn't
> included in MANIFEST. Is it supposed to be there?
It should be in MANIFEST, and now is. I don't know if that will quiet
the tinderclients though.
Alex
--
On Tue, 4 Dec 2001, Alex Gough wrote:
> The tinderbox is getting warm as a result of my number from string
> commit. I'm not able to reproduce the failures on either FreeBSD4.4
> or Irix or even on the Tru64 machine which is currently claiming to be
> orange. So I suspect that something odd is
[Tue, Dec 04, 2001 at 01:28:40PM +: Simon Cozens]
> On Tue, Dec 04, 2001 at 01:31:34AM -, [EMAIL PROTECTED] wrote:
> > Added length parameter to extract_num and extract_int string vtables,
> > without this it would be impossible to have strings with nulls in while
> > still know
> perl -e ''
> is very essential; though I could see a compatibility mode being
> enabled by
> default with '-e' if necessary.
But perl is not parrot, and parrot doesn't need -e (unless we expect people
to write one-liners in actual bytecode). Perl will be sitting on top of
parrot, so it will
On Tuesday 04 December 2001 12:21 am, David M. Lloyd wrote:
> He was telling me about the way PHP seperates the interpreter from
> the OS-specific stuff via a SAPI layer.
Facinating, but perl is, afterall a scripting language first. perl -e ''
is very essential; though I could see a compati
Automated smoke report for patch Dec 3 20:00:03 2001 UTC
v0.02 on hpux - 11.00 using cc version B.11.11.02
O = OK
F = Failure(s), extended report at the bottom
? = still running or test results not (yet) available
Build failures during: - = unknown
c = Configure, m = m
23 matches
Mail list logo
