On Sat, 21 Feb 2004, Simon Glover wrote:
>
> OK, here's a rewritten version of PDD 0, which reflects my view of
> the role that the PDDs currently play in Parrot development.
> Comments welcome.
Let's try that again, with the the PDD actually attached this time...
Simon
--
OK, here's a rewritten version of PDD 0, which reflects my view of
the role that the PDDs currently play in Parrot development.
Comments welcome.
Simon
On Thu, 19 Feb 2004 08:35:28 +, Nick Ing-Simmons wrote:
>
> How about layering it on ssh then?
> That has done all authentication stuff already.
I agree. With empty passphrases and/or ssh-agent it is very
easy to set up automated commands. Add forced commands (an
under
I checked in some changes that allow up to 3 levels of hierarchy in the
languages/perl6 tests (t/harness, Makefile, and run_tests() in 'perl6').
I also added a few new test files that use the new levels of hierarchy.
This is the first step in moving toward the new test hierarchy:
http://p6storie
> -Original Message-
> From: Jonathan Worthington [mailto:[EMAIL PROTECTED]
> Sent: Friday, February 20, 2004 4:47 PM
> To: [EMAIL PROTECTED]
> Subject: Re: [PATCH] Re: [perl #25239] Platform-specific files not
> granular enough
>
>
[snip]
>
> Creating an empty signal.h works fine, but t
- Original Message -
From: "Leopold Toetsch" <[EMAIL PROTECTED]>
To: "Jonathan Worthington" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Thursday, February 19, 2004 7:06 PM
Subject: Re: [PATCH] Re: [perl #25239] Platform-specific files not granular
enough
> Jonathan Worthington <[EM
Joe Gottman asked:
How do you decide whether a key-extractor block returns number? Do you
look at the signature, or do you simply evaluate the result of the
key-extractor for each element in the unsorted list? For example, what is
the result of the following code?
sort {$_.key} (1=> 'a
On Fri, 2004-02-20 at 15:00, Jonathan Worthington wrote:
> If someone will tell me how to make the changes, without having to
> spend hours messing with installing a content management system
> locally, I'll happily get on with it.
I have Combust working here. Grab the html files from:
Using both PIO and stdio in Parrot_warn causes output to get mixed up when io
is being buffered. This patch changes print_pbc_location to use PIO, and adds
a new print_pbc_location_stdio function for use by exceptions.c (which uses
stdio). With it I no longer get test failures on t/pmc/perlarray.t
# New Ticket Created by Adam Thomason
# Please include the string: [perl #26966]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org:80/rt3/Ticket/Display.html?id=26966 >
[First mail seems to have been lost in RT, apologies to the moderator if this shows
Smylers wrote:
sort {$_.key} (1=> 'a', 10 => 'b', 2 =>'c');
There is nothing in the signature of the key-extractor to suggest that
all the keys are numbers, but as it turns out they all are.
Are they? I'd been presuming that pair keys would always be strings
Nope.
> and that the C<< => >>
Luke wrote:
I think you're forgetting what language you're talking about. Those are
numbers. After this statement:
$x = '345';
C<$x> is a number.
I don't think so. C<$x> is, of course, a variable. And what it contains after
that statement will depend on whether the variable is explicitly
Smylers wrote:
Oh. I'd been assuming that quote marks indicated strings, and that,
while a string containing only digits could obviously be treated as a
number (as in Perl 5), it wouldn't be one without being provoked.
Correct.
What about:
$x = '0345';
Is that a number?
Nope. A string (un
> I brought this up several months ago and was told that a new webpage was
> in the works. Where in the works is it? Does it have an expected time
> to leave the works? I agree with Mitchell that it is important to
> maintain a public face (lest we send the wrong impression).
>
I offerred to hel
Uri wondered:
DC> No. C<< &infix:<=> >> is the name of the binary C<< <=> >> operator.
so how is that allowed there without a block?
A Code object in a scalar context yields a Code reference.
Damian
Smylers writes:
> Luke Palmer writes:
>
> > After this statement:
> >
> > $x = '345';
> >
> > C<$x> is a number.
>
> Oh. I'd been assuming that quote marks indicated strings, and that,
> while a string containing only digits could obviously be treated as a
> number (as in Perl 5), it would
At 2:49 PM -0700 2/20/04, Luke Palmer wrote:
After this statement:
$x = '345';
C<$x> is a number.
No, it isn't. It's a string. Or, rather, it's a PerlScalar.
I should hope it would be treated as one during
multimethod dispatch.
I should certainly hope *not*. If so, it's a bug. We ought to go
Luke Palmer writes:
> After this statement:
>
> $x = '345';
>
> C<$x> is a number.
Oh. I'd been assuming that quote marks indicated strings, and that,
while a string containing only digits could obviously be treated as a
number (as in Perl 5), it wouldn't be one without being provoked.
>
Smylers writes:
> Joe Gottman writes:
>
> > sort {$_.key} (1=> 'a', 10 => 'b', 2 =>'c');
> >
> > There is nothing in the signature of the key-extractor to suggest that
> > all the keys are numbers, but as it turns out they all are.
>
> Are they? I'd been presuming that pair keys would alw
Joe Gottman writes:
> sort {$_.key} (1=> 'a', 10 => 'b', 2 =>'c');
>
> There is nothing in the signature of the key-extractor to suggest that
> all the keys are numbers, but as it turns out they all are.
Are they? I'd been presuming that pair keys would always be strings (as
for hashes in
Smylers writes:
> Luke Palmer writes:
>
> > Uri Guttman writes:
> >
> > > > "DC" == Damian Conway <[EMAIL PROTECTED]> writes:
> >
> > > DC> @sorted = sort {-M}=>{$^b cmp $^a} @unsorted;
> > >
> > > but there is no comma before @unsorted. is that correct?
> >
> > Yes. Commas may be
Luke Palmer writes:
> Uri Guttman writes:
>
> > > "DC" == Damian Conway <[EMAIL PROTECTED]> writes:
>
> > DC> @sorted = sort {-M}=>{$^b cmp $^a} @unsorted;
> >
> > but there is no comma before @unsorted. is that correct?
>
> Yes. Commas may be ommitted on either side of a block whe
Here's a first draft of PDD 11. It's based on a combination of the
existing extend.pod and the comments in extend.c, with additional text
by yours truly. It should provide a minimal level of documentation for
all of the functions currently implemented in extend.c, but it doesn't
discuss futur
Leopold Toetsch <[EMAIL PROTECTED]> writes:
> Dan Sugalski <[EMAIL PROTECTED]> wrote:
>
>> Nah. Modern filesystems understand that A and a are the same letter.
>> It's those old antique filesystems that don't understand that... :-P
>
> yeP dAn, yOu ArE rIghT.
Still the same letters. Just a strang
On Fri, 20 Feb 2004, Dan Sugalski wrote:
> At 2:37 PM -0500 2/20/04, Simon Glover wrote:
> > I'm currently trying to put together a first draft of PDD 11 (extensions)
> > based on extend.pod plus the comments in extend.c and I've got a few
> > questions:
> >
> >[NB. I've dropped the Parrot_PMC
All~
I brought this up several months ago and was told that a new webpage was
in the works. Where in the works is it? Does it have an expected time
to leave the works? I agree with Mitchell that it is important to
maintain a public face (lest we send the wrong impression).
Parrot is current
At 2:37 PM -0500 2/20/04, Simon Glover wrote:
I'm currently trying to put together a first draft of PDD 11 (extensions)
based on extend.pod plus the comments in extend.c and I've got a few
questions:
[NB. I've dropped the Parrot_PMC prefixes below to save typing]
i) We have _get_string, _get_p
I'm currently trying to put together a first draft of PDD 11 (extensions)
based on extend.pod plus the comments in extend.c and I've got a few
questions:
[NB. I've dropped the Parrot_PMC prefixes below to save typing]
i) We have _get_string, _get_pointer, _get_intval, _get_numval,
_get_c
It's open for proposals and such. Quoth the organizer:
the workshop is now officially announced and the Call for Papers has
started
http://www.sebastian-bergmann.de/InterpretedLanguages2004/
Look 'em up and put in a paper. Should be fun.
--
Dan
It's open for proposals and such. Quoth the organizer:
the workshop is now officially announced and the Call for Papers has
started
http://www.sebastian-bergmann.de/InterpretedLanguages2004/
Look 'em up and put in a paper. Should be fun.
--
Dan
At 6:48 PM +0100 2/20/04, Leopold Toetsch wrote:
Dan Sugalski wrote:
At 9:42 AM +0100 2/20/04, Leopold Toetsch wrote:
Started that now:
The syntax (proposed and current) is for PASM:
.pcc_sub @MAIN _main:
and for PIR:
.sub _main prototyped, @MAIN, @IMMEDIATE, @LOAD, @POSTCOMP
Let's skip
At 1:00 PM -0500 2/20/04, Mitchell N Charity wrote:
A new release draws new attention, this release perhaps more than most.
The public face of parrot is that of a project which died a year ago. ;)
Yeesh, good point. We need to get that cleaned up.
Perhaps cleaning up the web site should be added t
Parrot's homepage http://www.parrotcode.org/ is out of date.
"the current release is version 0.0.10", "Where are we", etc.
The site has several automation failures.
ERROR RETRIEVING DATA messages in http://www.parrotcode.org/todo
and http://www.parrotcode.org/openpatches
The script which generates
Dan Sugalski wrote:
At 9:42 AM +0100 2/20/04, Leopold Toetsch wrote:
Started that now:
The syntax (proposed and current) is for PASM:
.pcc_sub @MAIN _main:
and for PIR:
.sub _main prototyped, @MAIN, @IMMEDIATE, @LOAD, @POSTCOMP
Let's skip the commas, mandate the properties come later, l
> One thing that would help is if people ran
>
> perl tools/docs/write_docs.pl -d -s
>
> on various platforms and told me if it works - or what they
runs fine on Windows 2000, with only the warning mentioned by chromatic.
On Fri, 20 Feb 2004, Tim Bunce wrote:
> Did you forget to add "Volunteers wanted for each of these" ?
>
Well, I'm going to try to tackle some of it, but since I have minimal
CFT at the moment, any volunteers would be very welcome.
Simon
Dan Sugalski <[EMAIL PROTECTED]> wrote:
> Nah. Modern filesystems understand that A and a are the same letter.
> It's those old antique filesystems that don't understand that... :-P
yeP dAn, yOu ArE rIghT.
leO, sCnr
At 9:42 AM +0100 2/20/04, Leopold Toetsch wrote:
Started that now:
The syntax (proposed and current) is for PASM:
.pcc_sub @MAIN _main:
and for PIR:
.sub _main prototyped, @MAIN, @IMMEDIATE, @LOAD, @POSTCOMP
Let's skip the commas, mandate the properties come later, lower-case
'em, and toss
At 6:19 PM -0800 2/19/04, Goplat wrote:
IMO this should just be replaced with plain old "filename = argv[1];" which
is what this patch does..
Applied, thanks.
--
Dan
--"it's like this"---
Dan Sugalski
Dan Sugalski <[EMAIL PROTECTED]> wrote:
> MAIN subs, of which there should be only one, is the sub that parrot
> executes when it's handed a bytecode file to run. If I do:
Done.
> IMMEDIATE subs are executed, with no parameters, as soon as they're
> done compiling. They're definitely compile-tim
At 4:56 PM -0800 2/19/04, chromatic wrote:
On Thu, 2004-02-19 at 16:34, Michael Scott wrote:
One thing that would help is if people ran
perl tools/docs/write_docs.pl -d -s
on various platforms and told me if it works - or what they did to make
it work - because I only have access to Mac OS X
Dan Sugalski <[EMAIL PROTECTED]> wrote:
> We've got the need to have subs that get executed when a code segment
> is loaded,
That part is working now for loaded assembly and byte code.
.pcc_sub @LOAD _the_init_code: # PASM
.sub _the_init_code @LOAD, prototyped # PIR
s. t/pmc/sub.t for
Did you forget to add "Volunteers wanted for each of these" ?
Tim.
On Thu, Feb 19, 2004 at 08:17:50PM -0500, Simon Glover wrote:
>
> PDD 0 (intro. to PDDs):
>
>Very, very out of date; I think it actually pre-dates Parrot
>
> PDD 1 (overview of Parrot):
>
>Not obviously out-of-date,
Dan Sugalski <[EMAIL PROTECTED]> wrote:
> Okay, since folks are diving into IMCC (assuming we can keep a fight
> from breaking out) it's time to address bytecode loading.
> We've got the need to have subs that get executed when a code segment
> is loaded, a need to have a 'main' sub that gets exec
Chromatic <[EMAIL PROTECTED]> wrote:
> Oops, I meant util/ncidef2pasm.pl.
This util just spits out PASM that generate NCI stubs and stores them as
globals. Not much change necessary: just put 2 statements around
.pcc_sub _sdl_init_nci_globals LOAD
[ code ]
invoke P1
This makes a subroutin
Jens Rieks <[EMAIL PROTECTED]> wrote:
> Hi,
> Am Donnerstag, 19. Februar 2004 23:39 schrieb Leopold Toetsch:
>>
>> I'll have a look at that _init call tomorrow - albeit _init (it was that
>> name IIRC) could be a too commonly used label. _library_init or such
>> could be better.
> That sounds reas
Thanks, applied.
On 20 Feb 2004, at 01:56, chromatic wrote:
On Thu, 2004-02-19 at 16:34, Michael Scott wrote:
One thing that would help is if people ran
perl tools/docs/write_docs.pl -d -s
on various platforms and told me if it works - or what they did to
make
it work - because I only have a
47 matches
Mail list logo
