> I guess the real question is whether ==> my $x is really assigning a
> list or binding an iterator to a Lazy slot somewhere. It feels like
> the latter is more useful. Which means that ==> @x can return as soon
> as it binds the iterator to @x.specs. It doesn't have to wait for all
> the valu
On 5/6/05 1:50 PM, in article
[EMAIL PROTECTED], "Steve Peters"
<[EMAIL PROTECTED]> wrote:
> On Fri, May 06, 2005 at 11:43:53AM -0400, Robert wrote:
>> "Andy Lester" <[EMAIL PROTECTED]> wrote in message
>> news:[EMAIL PROTECTED]
>>> On Thu, May 05, 2005 at 10:12:14AM -0400, Robert ([EMAIL PROTECTE
[EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> Modified:
>trunk/build_tools/build_nativecall.pl
> Log:
> Added a seen hash so that we don't get redefinition errors when things
> are listed twice (as they probably ought to be if they're for specific
> libraries).
> +next if $seen{"$ret$;
Dino Morelli <[EMAIL PROTECTED]> wrote:
> On Sat, 7 May 2005, Dino Morelli wrote:
>>On Sat, 7 May 2005, Leopold Toetsch wrote:
>$ ./parrot -o foo.pbc foo.imc
>$ ./parrot foo.pbc
>>The part I'm unsure of is the exit codes.
>>I could change it to watch for a bad code during the for loop wi
http://www.parrotcode.org/resources.html still has CVS and CVS
instructions mentioned. Please replace it with equivalent SVN hints.
Thanks,
leo
Leopold Toetsch wrote:
http://www.parrotcode.org/resources.html still has CVS and CVS
instructions mentioned. Please replace it with equivalent SVN hints.
... which are at http://www.parrotcode.org/source.html
Thanks,
leo
Please no more svn commits.
Thanks,
leo
On Sun, May 08, 2005 at 02:39:03PM +1000, Andrew Savige wrote:
: A crude hack sometimes used by gung ho p5 testers is to redefine
: perl built-in functions. For example:
:
: BEGIN {
: *CORE::GLOBAL::read = sub (*\$$;$) { return undef };
: }
:
: to test read failures (and so boost your Devel::
On Sun, May 08, 2005 at 07:20:04AM -0700, Larry Wall wrote:
> Absolutely everything is overridable in Perl 6, except the fact that
> the program is parsed as Standard Perl up till the first declaration
> (which might, of course, occur before the program file in a switch.)
On that note, http://perl
There have been a lot of substantial updates to the Parrot Grammar
Engine, so I figure it's a good time for a summary report. The latest
version (in the Parrot cvs trunk) now incorporates:
- subrules
- capture aliases (named and numbered)
- the :w modifier and subrules
- word boundaries
I hope all is working and may the checkins continue,
leo
Parrot 0.2.0 "NLnet" Released!
On behalf of the Parrot team I'm proud to announce the release of
Parrot 0.2.0 and I'd like to thank all involved pepole as well as
our sponsors for supporting us.
It's a pleasure and honor for me to be able to advertise (after 0.1.0) the
next leap release 0.2.0 with
[Correcting typographic errors noticed after sending original. Sorry
for the errors and duplicate posts. Also, in many of the double
quoted strings below the backslashes should probably be escaped
(i.e., "\\s" instead of "\s") but I'm leaving them alone for
readability. --Pm]
* Rules are Parro
Hi,
C is now implemented. The second part (find_(not_)cclass) will
follow tomorrow.
jens
PS: The "get_byte past the end of the buffer (1 of 1)" error is hopefully
fixed, too. Don't know if it is the cleanest way, but it at least works :-)
On Tuesday 12 April 2005, Steve Peters via RT wrote:
> This ticket is a duplicate of ticket #34549. ÂI'll have a patch for this
> issue later this week.
It is not fixed yet, can you please give a status update?
Are you still working on it?
jens
The following patch makes Parrot_get_name report a different error
message if Parrot_MMD_search_default_func finds nothing, to distinguish
this from the case where nothing is found. I am finding this helpful in
debugging.
But this seems like a band-aid, for two reasons:
1. find_name ca
Greetings. Attached is a patch that I'm currently using in Pugs's
bundled PGE.pbc, in order to make PGE output properly escaped strings,
in a format ready to be used form Haskell FFI.
I'd appreciate comments, and if it's okay to commit it back to the
PGE directory.
Thanks,
/Autrijus/
Patch
> Leopold Toetsch wrote:
> > http://www.parrotcode.org/resources.html still has CVS and CVS
> > instructions mentioned. Please replace it with equivalent SVN hints.
>
> ... which are at http://www.parrotcode.org/source.html
Updated.
As always, patches for this kind of thing are welcome.
(You
18 matches
Mail list logo
