Hi,
This was wanted in the next release, so I applied the bits that weren't
applying with patch manually. Applied your tests as well. All checked in
as r17514.
Thanks!
Jonathan
On Fri Mar 16 05:53:37 2007, coke wrote:
> file in original patch was never added. Added, need feedback from
> win32 developers if this addresses the warning.
No more strdup deprecation warnings.
kjs
Hi,
Just tried to reproduce this (on Win32)...
% ../../parrot -o out.pbc out.pir # takes forever
This gives the following error:
error:imcc:syntax error, unexpected LOCAL
in file 'out.pir' line 1
If I stick a .sub main at the start and a .end at the end, I still get
errors...
error:im
# New Ticket Created by Jerry Gay
# Please include the string: [perl #41870]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=41870 >
i need a config file processing library for use in pir code--something
like perl's Config::
Jim, can you resend with diffs in unified format? (That's "diff -u",
not "diff".) They're much, much easier to read.
-- c
# New Ticket Created by James Keenan
# Please include the string: [perl #41871]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=41871 >
Twice in the past two days I have encountered this failure while
running 'make test':
# New Ticket Created by James Keenan
# Please include the string: [perl #41872]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=41872 >
While running 'make test', t/distro/manifest.t failed with this output:
t/distro/manife
# New Ticket Created by James Keenan
# Please include the string: [perl #41873]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=41873 >
These failures occurred during 'make test' and were confirmed by
running the individua
chromatic wrote:
Jim, can you resend with diffs in unified format? (That's "diff -u",
not "diff".) They're much, much easier to read.
-- c
I screwed up. I attached this to the wrong ticket.
Author: larry
Date: Fri Mar 16 09:31:56 2007
New Revision: 14352
Modified:
doc/trunk/design/syn/S02.pod
doc/trunk/design/syn/S03.pod
Log:
The ratio type is now a noun, not an adjective.
No longer spec that / must pragmatically produce a Rat.
Instead, Int div Int is now guaranteed to return
Author: larry
Date: Fri Mar 16 12:27:14 2007
New Revision: 14353
Modified:
doc/trunk/design/syn/S02.pod
Log:
Fixes suggested by spinclad++.
Modified: doc/trunk/design/syn/S02.pod
==
--- doc/trunk/design/syn/S02.pod
On Thu, Mar 15, 2007 at 05:14:01PM -0400, Zev Benjamin wrote:
: If the idea of having an author attribute is to allow multiple
: implementations of a module, why not add an API version attribute? The
: idea would be to detach the module version number from the module API
: version number.
I was t
P.S. Sorry for not replying to this for so long, but I have been without
a computer for the last week ... and possibly for the next week too ...
right now, I'm on someone else's machine.
--
On Wed, 7 Mar 2007, Smylers wrote:
> On February 27th Darren Duncan writes:
> > One common us
On Fri, Mar 16, 2007 at 05:29:21PM -0700, Larry Wall wrote:
> On Thu, Mar 15, 2007 at 05:14:01PM -0400, Zev Benjamin wrote:
> : If the idea of having an author attribute is to allow multiple
> : implementations of a module, why not add an API version attribute? The
> : idea would be to detach the
On Wed Aug 16 23:06:53 2006, coke wrote:
> Anything referring to TEST_PROG should probably be renamed to
> "parrot" or "executable" based on context.
>
For reference ...
I 'acked' and got the instances of TEST_PROG found in the attachment
TEST_PROG.instances.txt.
kid51
languages/APL/t/harne
On Fri Mar 16 19:42:17 2007, [EMAIL PROTECTED] wrote:
> On Wed Aug 16 23:06:53 2006, coke wrote:
> > Anything referring to TEST_PROG should probably be renamed to
> > "parrot" or "executable" based on context.
> >
>
> For reference ...
>
> I 'acked' and got the instances of TEST_PROG found in the
Emacs users, what's the appropriate equivalent to the relevant part of:
# Local Variables:
# mode: cperl
# cperl-indent-level: 4
# fill-column: 100
# End:
# vim: expandtab shiftwidth=4:
for PIR files? Is this workable?
# Local Variables:
# mode: pir
#
On 3/16/07, James Keenan via RT <[EMAIL PROTECTED]> wrote:
On Fri Mar 16 19:42:17 2007, [EMAIL PROTECTED] wrote:
> On Wed Aug 16 23:06:53 2006, coke wrote:
> > Anything referring to TEST_PROG should probably be renamed to
> > "parrot" or "executable" based on context.
> >
>
> For reference ...
>
Will Coleda wrote:
Having a limit is more than reasonable, agreed: the goal of this patch
was to bring the code into agreement with the docs.
Consider this a poke to the Architect to verify/replace the previous
overturn of the original 32-register limit.
The advantage of allowing unlimited r
Namespaces have an export feature. A bit clunky, but a definite
improvement over the .IMPORT macro. I've replaced all instances of
.IMPORT with the "export_to" method, except
languages/PIR/examples/test.pir, because it seems to just be a generic
syntax example.
20 matches
Mail list logo
