Daniel Grunblatt wrote:
+# endif
+# if EXEC_OS == DARWIN
+# define EXEC_MACH_O
+# endif
+# if (EXEC_OS == FREENBSD) || (EXEC_OS == LINUX)
# define EXEC_ELF
# endif
Umm, I think you mean FREEBSD there ;-)
-garrett
This patch fixes some warnings in global_setup.c and embed.c. All it
does is add some necessary includes to pick up function declarations and
constify a variable to avoid warnings about casting from const to
non-const, so it should be pretty safe to apply.
-garrett
Index: src/embed.c
=
There are two todo tests in given.t that have # in their desc string,
which is confusing 'make test'. Here's a diff to remove the #s, so they
no longer show up as failing.
-garrett
Index: t/base/given.t
===
--- t/base/given.t
I'm having some trouble using the &?SUB variable in a subroutine
declared with the -> operator. The following code results in an error
about &?SUB being undefined:
my $s = -> $count {
if $count < 10 {
say $count;
&?SUB($count + 1);
}
};
$s(1);
If I change to either a named sub (sub
Luke Palmer wrote:
That's because a pointy sub is not a sub. Perhaps we should call it a
pointy block.
That might be clearer ;-)
Not all code objects are Subs. If you call "return", then you return
from the innermost enclosing "sub", which is marked by that word.
Likewise does $?SUB. I don't bel
There are two unexpected successes in given.t (it must be my night for
finding things with that file...), but unfortunately they're not because
pugs is magically doing the right thing, they're because it's doing the
wrong thing in a way that exactly matches what the test is looking for,
if you
Since the first thing I actually tried to do with Pugs was to use the
%hash.kv method (see S04.pod) to iterate over the keys and values in a
hash, and it of course didn't work since it hasn't been implemented yet,
I figured I should at least send in a test for it.
Here's a diff to t/op/hash.t a
It seems that the loop statement currently doesn't let you declare
variables inside it, so the following code:
loop (my $i = 0; $i < 10; $i++) { }
doesn't work. Here's a test for the problem.
-garrett
Index: t/base/loop.t
===
--- t/
Patrick R. Michaud wrote:
On Sat, Mar 05, 2005 at 11:22:23AM -0500, Garrett Rooney wrote:
It looks like the current pugs array interpolation doesn't quite match
the description in S02.
[...]
So what's right, the spec or the implementation?
I should've also mentioned in my previo
We don't have any tests for the $?LINE and $?FILE variables, although
they do work just fine as far as I can tell.
Here's a diff adding some in a new t/magical/vars.t file, since Autrijus
thought they should go in t/magical, but there doesn't appear to be a
good home for them there yet.
-garre
It looks like the current pugs array interpolation doesn't quite match
the description in S02.
S02 says that container references automatically dereference to the
appropriate (white space separated) string values, which is fine, pugs
does that now, but it also says that to interpolate an entire
Garrett Rooney wrote:
Assuming the spec is correct, here's a patch to add some more tests to
t/op/string_interpolation.t.
Of course, those should have been todo_is tests... Here's the right patch.
-garrett
Index: t/op/string_inter
Luke Palmer wrote:
Garrett Rooney writes:
We don't have any tests for the $?LINE and $?FILE variables, although
they do work just fine as far as I can tell.
Here's a diff adding some in a new t/magical/vars.t file, since Autrijus
thought they should go in t/magical, but there doesn&#
Autrijus Tang wrote:
On Sat, Mar 05, 2005 at 02:39:06PM -0700, Luke Palmer wrote:
Garrett Rooney writes:
Garrett Rooney wrote:
Assuming the spec is correct, here's a patch to add some more tests to
t/op/string_interpolation.t.
Of course, those should have been todo_is tests... Here's
I might have this wrong, but isn't the 'is export' trait on a subroutine
supposed to indicate that it's exported into the namespace of the code
that uses or requires the module? That doesn't seem to be happening
right now. Well, it is happening, but it's also happening for
subroutines without
Chia-liang Kao wrote:
Hi,
I've just setup a Subversion mirror of the parrot cvs repository with
svk. Will try to keep it in sync until Robert have time to do similar
setup on perl.org.
So you could now use the Subversion repository (readonly) at:
svn://svn.clkao.org/parrot/cvs/trunk
web interfac
Brent 'Dax' Royal-Gordon wrote:
Matt Fowles wrote:
I thought that subversion was tried for use with Parrot and found
unexceptable for some reason a while back. I am not trying to
discourage you guys... I personally prefer svn to cvs, but I think it
would be wise to determine of those problems sti
Robert Schwebel wrote:
On which platforms shall perl run _today_ which is not able to run sh?
VMS. Just because you don't use it doesn't mean that nobody uses it.
-garrett
On Feb 24, 2004, at 9:38 AM, Leopold Toetsch wrote:
cvsuser 04/02/24 06:38:07
Modified:include/parrot packfile.h
pf pf_items.c
src packfile.c
Log:
try to fix Tru64 native PBC issues
The PARROT_BIGENDIAN case has a typo in pf_items.c, here's a
On Fri, Feb 20, 2009 at 11:23 AM, perl6 via RT
wrote:
> I'm getting a crash on OS X when trying to build rakudo. This is with
> parrot r36907 and the current version of rakudo
> (f23eda2c5251db5a90f5fdd3b587d4c234ee70e4) from github.
Note that rolling back to parrot r36866 fixes the crash. I h
On Fri, Feb 27, 2009 at 9:56 PM, Patrick R. Michaud wrote:
> On Fri, Feb 20, 2009 at 10:56:02PM -0500, Garrett Rooney wrote:
>> On Fri, Feb 20, 2009 at 11:23 AM, perl6 via RT
>> wrote:
>>
>> > I'm getting a crash on OS X when trying to build rakudo. This
21 matches
Mail list logo
