# New Ticket Created by Joshua Hoblitt
# Please include the string: [perl #38196]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/rt3/Ticket/Display.html?id=38196 >
This transaction appears to have no contentHi Folks,
I started writing this document
# New Ticket Created by Joshua Hoblitt
# Please include the string: [perl #38195]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/rt3/Ticket/Display.html?id=38195 >
The current svk-bootstrap-dump.bz2 is pretty far out of date now being
only through r
From: Steve Gunnell <[EMAIL PROTECTED]>
Date: Mon, 09 Jan 2006 18:45:24 +0800
On Sun, 2006-01-08 at 11:05 -0500, Bob Rogers wrote:
>From: Steve Gunnell <[EMAIL PROTECTED]>
>Date: Sun, 08 Jan 2006 15:02:37 +0800
>
>. . .
>
>It also seems to me that with
Hello again,
In Pugs, we are currently trying to figure out how classes are
initialized with $repr types other than P6opaque. My interpretation
of S12 is that P6opaque types are initialized as follows (by default):
&new is called with named arguments, it then calls &bless passing in
'P6op
"Jonathan Worthington" <[EMAIL PROTECTED]> wrote:
Note that dynamic op libs do not *work* on Win32 yet
They do now - I'm using them with my .NET to PIR translator and they work
nicely.
I would really like some feedback from MinGW and cygwin folks on how
dynoplibs build and work for them, as I
On Tue, Jan 10, 2006 at 01:06:29AM +, Nick Glencross wrote:
> Joshua Hoblitt (via RT) wrote:
>
> >Parrot should support pkgconfig by installing a pc data file. It should
> >probably be named parrot.pc.
> >
> Ok, I can do this. I've had an initial stab at it, and one thing that
> I've had to
Joshua Hoblitt (via RT) wrote:
Parrot should support pkgconfig by installing a pc data file. It should
probably be named parrot.pc.
Ok, I can do this. I've had an initial stab at it, and one thing that
I've had to do is provide a quoting mechanism into the configuration
file substitution bec
Hello all,
I have been reading the recently updated Synopsis 12, and a few
things jumped out at me. In the "Classes" section, classes are
described like this:
Classes are primarily for instance management, not code reuse.
Later in the same section the following is stated:
Every cl
On 1/9/06, Gaal Yahas <[EMAIL PROTECTED]> wrote:
>sub use_ok($module) {
>eval "package {caller.package}; require etc.";
>}
I'd like to see a nice interface to scopes in general. That is, we
would have a "scope object" which would provide access to all the
lexical scopes and the pa
On Dec 14, 2005, at 12:52, Joshua Isom (via RT) wrote:
[ substr related PANIC ]
I've now a rather simple test case: a string reverse_inplace that shows
some parts of the problem.
(You might ulimit -v yourself to a few 100 Megs before running the
program)
.sub main :main
.local string
> We need to clean up the docs and pmcs for compilation, dynamic
> compiler modules, and the associated pmcs (eval, compiler, and so on).
The muddle has been somewhat cleaned up. For example the PMCs returned by
compreg and from the compilers can now simply be invoked.
Are further actions neede
What we need to do is find a way to do this at compile time.
One way is to make use_ok a macro.
The whole thing with linkage in Perl 6 is that it's supposed to
happen at compile time so that things are overall saner, but that it
can happen at runtime if we really really mean it.
use_ok as a func
Consider use_ok from the test system. Essentially, it should be
require $module; $module.import; pass "load $module";
in its caller's context. But now that exportation is lexical, how can
use_ok be implemented? It must divert the symbols installed by &import
and have them installed in the call
On Jan 9, 2006, at 2:18 AM, Adrian Howard wrote:
Y'want Test::Builder's failure_output(), e.g.:
use Test::More tests => 1;
binmode Test::More->builder->failure_output, ':utf8';
diag "\x{201c}";
ok 1;
Ah, right, error_output, too.
Thanks!
David
Thanks for the responses. I have indeed started to look at Test::Class.
A major point raised here about Test::Unit is that it doesn't
integrate with Test::Builder, which I hadn't considered.
Another issue is that because TU so closely matches jUnit it is "less
Perlish", and I think that is
On Sun, 2006-01-08 at 11:05 -0500, Bob Rogers wrote:
>From: Steve Gunnell <[EMAIL PROTECTED]>
>Date: Sun, 08 Jan 2006 15:02:37 +0800
>
>Hi,
>
>I'm sitting here thinking about cross language calls and what I
don't
>see anywhere is a prohibition that stops a context from popping
On 9 Jan 2006, at 05:03, David Wheeler wrote:
[snip]
Is there any way to get Test::Builder to set an I/O layer on its
file handles?
[snip]
Y'want Test::Builder's failure_output(), e.g.:
use Test::More tests => 1;
binmode Test::More->builder->failure_output, ':utf8';
diag "\x{201c}";
ok 1;
C
On Mon, Jan 09, 2006 at 07:06:08PM +1100, Kirrily Robert wrote:
> Does anyone else find that SKIP: { } blocks bugger up the debugger?
> I'll be happily bouncing on the "n" key to get to round about the
> vicinity of the failing test, and then blam, it sees a skipped test
> and just fast-forw
Does anyone else find that SKIP: { } blocks bugger up the debugger?
I'll be happily bouncing on the "n" key to get to round about the
vicinity of the failing test, and then blam, it sees a skipped test
and just fast-forwards to the end.
K.
--
Kirrily Robert
[EMAIL PROTECTED]
http://infotr
> On Sun, 8 Jan 2006 13:34:43 -1000, Joshua Hoblitt <[EMAIL PROTECTED]>
> said:
> Are you happy with META.yml I proposed or are there other issue
> that need to be addressed?
Yes, it looks good.
--
andreas
20 matches
Mail list logo
