On Wednesday, April 24, 2002, at 04:04 PM, Robert Spier wrote:
> One of the keys of the system Jeff has implemented is that it's 100%
> real perl code and real perl objects, not a language parsed with
> perl. This means you can do nifty things and write perl code to
> modify things in a natural w
>Without knowing too much about it, I still have to wonder what is
>wrong with cons? I thought it was a fully functional all-perl make
>replacement.
One reason not to use cons is that we will have to port it to
parrot/perl6 in order to become self hosting, another, is that it
may not meet all of
Michael G Schwern wrote in perl.perl6.language :
> On Tue, Apr 23, 2002 at 11:11:28PM -0500, Me wrote:
>> Third, I was thinking that having perl 6 regexen have /s on
>> by default would be easy for perl 5 coders to understand;
>> not too hard to get used to; and have no negative effects
>> for exi
At 4:10 PM -0400 4/24/02, Simon Glover wrote:
> You're quite right - corrected patch below, plus a simple test case.
Applied, thanks.
--
Dan
--"it's like this"---
Dan Sugalski
Folks,
From now on, please every time you want to send a patch send it to
[EMAIL PROTECTED] so that we can keep track of it and it doesn't
get lost in space.
Thanks.
Daniel Grunblatt.
On Wed, 24 Apr 2002, Steve Fink wrote:
> On Wed, Apr 24, 2002 at 03:22:57PM -0400, Simon Glover wrote:
> >
> > --- core.ops.oldWed Apr 24 15:07:05 2002
> > +++ core.opsWed Apr 24 15:22:03 2002
> > @@ -470,7 +470,7 @@
> > Sets register $1 to the current address plus the offset $2
> >
On Wed, Apr 24, 2002 at 03:22:57PM -0400, Simon Glover wrote:
>
> --- core.ops.old Wed Apr 24 15:07:05 2002
> +++ core.ops Wed Apr 24 15:22:03 2002
> @@ -470,7 +470,7 @@
> Sets register $1 to the current address plus the offset $2
>
> inline op set_addr(out INT, in INT) {
> - $1 = cur_o
On Wed, 24 Apr 2002, Dan Sugalski wrote:
> I've added set_addr, which gets the address of a label, like so:
>
> set_addr I3, FOO
>
> and fixed jump and jsr to actually work with absolute addresses.
>
This generates a stack of warnings of the form:
core.ops:473: warning: assignment makes
In message <[EMAIL PROTECTED]>
Nicholas Clark <[EMAIL PROTECTED]> wrote:
> Jarkko mailed this URL to p5p:
>
> http://developer.kde.org/~sewardj/
>
> It describes a free (GPL) memory leak checker for x86 Linux
>
> 1: This may be of use for parrot hackers
Which is why I mentioned
On Wed, Apr 24, 2002 at 03:10:55AM -0400, Jeff wrote:
> In between attempting to get the new assembler up and running (currently
> dealing with XS issues), Robert Spiers and I have come up with a new
> make mechanism.
XS? Is this a different assembler than Simon Cozen's? I assume so,
since I've h
On Wed, Apr 24, 2002 at 12:49:27PM -0400, Dan Sugalski wrote:
> I've added set_addr, which gets the address of a label, like so:
>
>set_addr I3, FOO
Awww, you didn't call it lea? Now how am I supposed to feel superior
to all the people who would have no clue what lea means?
> I think callcc
I've added set_addr, which gets the address of a label, like so:
set_addr I3, FOO
and fixed jump and jsr to actually work with absolute addresses.
I think callcc might be coming soon. Be afraid, be very afraid...
--
Dan
---
At 2:30 AM + 4/20/02, Chip Salzenberg wrote:
>According to [EMAIL PROTECTED] (Dan Sugalski):
>>At the moment, we don't have to support cascading lexical
>>scratchpads--since we know at compile time which variables we're
>>accessing and where they come from, we can install trampoline entries
>>
Methamphetamine/Speed is probably unhealthy for parrots.
On 4/24/02 7:32 AM, "Nicholas Clark" <[EMAIL PROTECTED]> wrote:
> On Wed, Apr 24, 2002 at 12:26:57PM +0100, Nicholas Clark wrote:
>> Jarkko mailed this URL to p5p:
>>
>> http://developer.kde.org/~sewardj/
>
> I'd not twigged, but the
Steve Fink:
> EVENTUAL CURRENT
> set I0, P0[7] get_keyed I0, P0, 7
> set P0[7], I0 set_keyed P0, 7, I0
> set P0[0], P1[1]not possible
> set I0, P0[P1] not possible -- I'm not even sure what this will do
> set P1, P0[7] get_keyed P1, P0, 7 (
I vote for mutable strings.
Anything but immutable strings please!
Java sucks as a string manipulation engine because of their immutable
String class. The best GC and JIT in the world can't save it.
High performance Java parsers generally write their own mutable
string class for this very reaso
On Tue, 2002-04-23 at 19:43, Dan Sugalski wrote:
> At 6:19 PM +0100 4/19/02, Alberto Manuel Brandão Simões wrote:
> >But, this e-mail is not to say this, but to request some kind of help.
> >I'm used to check-out, compile and test parrot, looked at the language
> >(well, a long time ago) and I'm n
Steve Fink <[EMAIL PROTECTED]> writes:
> On Mon, Apr 22, 2002 at 05:40:09PM +0100, Piers Cawley wrote:
>> Does anyone have an idea of when we're going to see these? Or hashes
>> of PMCs, I don't really care which...
>
> Well, we don't have hashes of anything. We already have arrays of
> PMCs. You
18 matches
Mail list logo
