Doesn't do much beyond strength reduction and constant folding, but it's
there. Also, if you look at the parsing routines I've created a fairly
simple data structure to hold lines of a post-macro-processed assembler
program. The output routine preserves comments and whitespace within
reason.
--
J
Bryan C. Warnock:
# Can we start a config/ directory for config snippets?
Fine by me.
--Brent Dax
[EMAIL PROTECTED]
Configure pumpking for Perl 6
"Nothing important happened today."
--George III of England's diary entry for 4-Jul-1776
At 04:16 PM 12/13/2001 -0600, Garrett Goebel wrote:
>Okay... let me try again.
>
>This fixes:
>o parrot/classes/Makefile.in to use double quotes
>instead of single quotes with perl -e
>o parrot/languages/Makefile.in to use && instead of $(MAKE) -C
Applied, thanks.
Brent,
Can we start a config/ directory for config snippets?
--
Bryan C. Warnock
[EMAIL PROTECTED]
> This fixes:
> o parrot/classes/Makefile.in to use double quotes
>instead of single quotes with perl -e
Note that if you have to get even slightly more complicated than this,
then you're better off wrapping everything up in a (possibly very small)
file and just calling that. Don't forget,
"Brent Dax" <[EMAIL PROTECTED]> writes:
> Piers Cawley:
> # In the following code fragment, what context is foo() in?
> #
> # @ary[0] = foo()
>
> The short answer is scalar context. The long answer is below. Note
> that the long answer is only the way I think of it. You may think
> differe
I'm not sure we'll ultimately go this way, but I've added the following ops
to the core:
setline
setpackage
setfile
getline
getpackage
getfile
so compiler output can note the file, package, and line that code is in.
Definitely optional, but there for debugging purposes.
Title: RE: Better temporary Makefile patch
Okay... let me try again.
This fixes:
o parrot/classes/Makefile.in to use double quotes
instead of single quotes with perl -e
o parrot/languages/Makefile.in to use && instead of $(MAKE) -C
After which I can:
perl ./Configure.pl && nmake &
From: Garrett Goebel [mailto:[EMAIL PROTECTED]]
>
> That gets me further on Win32... now we hit Win32 perl -e and quoting
> issues...
>
> c:\perl\bin\perl.exe -ne 'next unless /Parrot_default/;
> s/{/;/;s/^/extern /;print' default.c > default.h
> Can't find string terminator "'" anywhere
> > @ary[0] =()= foo(); # " " " " " "" "
>
> Hm, thats a change from perl5. In perl5 that would assign the number of
> elements returned from foo(). Is there a good reason for this change ?
Firstly, Larry may have to rule on which behaviour actually *is*
From: Andy Dougherty [mailto:[EMAIL PROTECTED]]
>
> This patch fixes up Makefile.in to handle subdirectories
> along the lines
> I suggested yesterday. (The make -C trick is GNU-specific
> and hence not
> portable, and the cd dir; $(MAKE) trick is Unix-specific and hence not
> portable.) This
On Fri, Dec 14, 2001 at 06:39:02AM +1100, Damian Conway wrote:
>
>> In the following code fragment, what context is foo() in?
>>
>> @ary[0] = foo()
>
> Scalar context. @ary[0] is a single element of @ary.
>
> To call foo() in list context use any of the following:
>
> (@
On Thu, 13 Dec 2001 12:17:44 -0500, Mark J. Reed wrote:
> @i = (0);
> @ary[@i] = foo();
>
>How could one get that behavior without the intermediate array?
Parens, likely.
(@ary[0]) = foo();
--
Bart.
On Wed, 12 Dec 2001, Andy Dougherty wrote:
> One idiom which might work is
>
> cd foo && $(MAKE)
D'oh, that's
cd foo && $(MAKE) && cd ..
(remembering the actual initial problem . . . :-)
--
Andy Dougherty [EMAIL PROTECTED]
Dept. of Physics
Lafayette Colle
At 09:42 AM 12/13/2001 -0500, Andy Dougherty wrote:
>This patch fixes up Makefile.in to handle subdirectories along the lines
>I suggested yesterday.
Applied. Thanks.
Dan
--"it's like this"---
Dan Sugal
> In the following code fragment, what context is foo() in?
>
> @ary[0] = foo()
Scalar context. @ary[0] is a single element of @ary.
To call foo() in list context use any of the following:
(@ary[0]) = foo(); # Assign @ary[0] the first element returned
@(@ary[
This patch fixes up Makefile.in to handle subdirectories along the lines
I suggested yesterday. (The make -C trick is GNU-specific and hence not
portable, and the cd dir; $(MAKE) trick is Unix-specific and hence not
portable.) This is a "temporary" patch because a perl-based build system
will re
Do we wish to abstract shared mem behind a Parrot IO object as well, so all
the
file methods work?
Melvin Smith
Centers for IBM e-business Innovation :: ATLANTA
At 05:44 PM 12/13/2001 +, Dave Mitchell wrote:
>I wrote:
>
> > (If you were to give me a PDD number, I might even get round to finishing
> > the doc off ;-)
>
>Okay, I lied
Oh, right, you already had it done and were using the thread of
unfinishedness to get a PDD number! Clever... ;-P
I wrote:
> (If you were to give me a PDD number, I might even get round to finishing
> the doc off ;-)
Okay, I lied
:-)
At 05:38 PM 12/13/2001 +, Dave Mitchell wrote:
>Dan Sugalski <[EMAIL PROTECTED]> wrote:
> > D'oh! First I find the codings standard doc, then I get it an official PDD
> > number if it doesn't have one already. (Then I smack myself with it...)
>
>print "Dan, can I have a PDD number for my codin
Dan Sugalski <[EMAIL PROTECTED]> wrote:
> D'oh! First I find the codings standard doc, then I get it an official PDD
> number if it doesn't have one already. (Then I smack myself with it...)
print "Dan, can I have a PDD number for my coding stds doc?\n" for 1..Inf;
(If you were to give me a PDD
Thats all the answer I was looking for. :)
Melvin Smith
Centers for IBM e-business Innovation :: ATLANTA
(Embedded
image moved to Dan Sugalski <[EMAIL PROTECTED]>
Piers Cawley:
# In the following code fragment, what context is foo() in?
#
# @ary[0] = foo()
The short answer is scalar context. The long answer is below. Note
that the long answer is only the way I think of it. You may think
differently.
I like to think of it as 'one context'. 'Scalar'
At 12:21 PM 12/13/2001 -0500, Melvin Smith wrote:
>Well I had hoped after repeated questions and submitting some code I would
>generate some discussion on the IO layer that was supposed to be on the
>TODO list. I'm no closer a week later so I'll assume ignored patches and
>request for comments me
Well I had hoped after repeated questions and submitting some code I would
generate some discussion on the IO layer that was supposed to be on the
TODO list.
I'm no closer a week later so I'll assume ignored patches and request for
comments
means someone else wants to work on it "when" they get to
On Thu, Dec 13, 2001 at 12:12:14PM -0500, Ted Ashton wrote:
> Thus it was written in the epistle of Piers Cawley,
> > In the following code fragment, what context is foo() in?
> >
> > @ary[0] = foo()
>
> Scalar, I would think.
I assume that the following would make the assignment a slice
an
Thus it was written in the epistle of Piers Cawley,
> In the following code fragment, what context is foo() in?
>
> @ary[0] = foo()
Scalar, I would think.
Just my guess,
Ted
--
Ted Ashton ([EMAIL PROTECTED]) | From the Tom Swifty collection:
Southern Adventist University| "Multiplicati
In the following code fragment, what context is foo() in?
@ary[0] = foo()
the following code
@ary= foo()
obviously evaluates @foo in a list context, but in the first I'm no
longer sure.
--
Piers
"It is a truth universally acknowledged that a language in
possession of a ri
At 11:15 AM 12/13/2001 -0500, Bryan C. Warnock wrote:
>On Thursday 13 December 2001 11:10 am, Dan Sugalski wrote:
> > At 11:33 PM 12/12/2001 -0500, Josh Wilmes wrote:
> > >Here are a few of the more clear-cut fixes I noticed from -Wall's
> > > whinings.
> >
> > Applied, with some hand-patching. (Y
At 11:22 AM 12/13/2001 -0500, Josh Wilmes wrote:
>Oops. Sorry, i'll attach it next time.
Inline's just fine. (Eudora has this nasty habit, when transferring mail
from IMAP-hosted mailboxes to local folders of *not* copying the
attachments, instead referencing the attachment in the IMAP box. Wh
Oops. Sorry, i'll attach it next time.
--Josh
At 11:10 on 12/13/2001 EST, Dan Sugalski <[EMAIL PROTECTED]> wrote:
> At 11:33 PM 12/12/2001 -0500, Josh Wilmes wrote:
> >Here are a few of the more clear-cut fixes I noticed from -Wall's whinings.
>
> Applied, with some hand-patching. (Your maile
On Thursday 13 December 2001 11:10 am, Dan Sugalski wrote:
> At 11:33 PM 12/12/2001 -0500, Josh Wilmes wrote:
> >Here are a few of the more clear-cut fixes I noticed from -Wall's
> > whinings.
>
> Applied, with some hand-patching. (Your mailer threw in hard returns for
> lines over 80 characters)
At 11:18 PM 12/12/2001 -0500, Josh Wilmes wrote:
>Here's a minor patch which should make purify happy. (passing in 0 for
>the length was causing an "ABR" error).
Applied, thanks.
Dan
--"it's like this"-
At 11:33 PM 12/12/2001 -0500, Josh Wilmes wrote:
>Here are a few of the more clear-cut fixes I noticed from -Wall's whinings.
Applied, with some hand-patching. (Your mailer threw in hard returns for
lines over 80 characters)
Dan
-
35 matches
Mail list logo
