On 6/30/05, Michael G Schwern <[EMAIL PROTECTED]> wrote:
> On Thu, Jun 30, 2005 at 08:03:32AM +0200, demerphq wrote:
> > Yitzchak pointed me to this thread. I thought I'd add that
> > Data::Dump::Streamer v1.14 has the capability to Dump closures
> > properly, that is including bound lexical state.
On 6/30/05, demerphq <[EMAIL PROTECTED]> wrote:
> Incidentally this is a pretty common mistake when handling REF's.
> Data::Dumper does it as does YAML and pretty much all the other
> storage tools that i have looked at, although Storable gets it right.
> Also, i should say that while this circular
As I understand it SMD is now not much more than a mechanism to
place a constraint on the MMD, saying that there can only be one
method or subroutine with the same short name.
Why is this the default?
MMD has a huge value for amending software (especially not your own
software) - specialized case
On Thu, 30 Jun 2005 05:17:56 +0300, Yuval Kogman
<[EMAIL PROTECTED]> wrote:
[...]
> I gave Perl 6 to Mr. Clean, and he said that if type inferrence was
> formalized, and used always, except that it's usually used for
> performance, and with a lexical pragma can be used to enforce types.
> I like
I'm just wondering if a documentation trait on subs would be usefull.
If we are going to have something like p6explain the doc trait could
be used as the source for the infomation for it. p6explain would
simply have to walk the AST reading the doc traits and pasting the
text together.
--
Please
On Thu, Jun 30, 2005 at 06:17:14AM -, David Formosa (aka ? the Platypus)
wrote:
> On Thu, 30 Jun 2005 05:17:56 +0300, Yuval Kogman
> <[EMAIL PROTECTED]> wrote:
> [...]
>
> > I gave Perl 6 to Mr. Clean, and he said that if type inferrence was
> > formalized, and used always, except that it's
Brian Wheeler wrote:
Its been a while since I tinkered with parrot so I thought I'd start
playing again...but I've hit a segfault.
Should of course not happen... But it seems that the codegen is mixing
old and new calling conventions.
The trace:
8233 set I0, 1- I0=1,
8236 set I
During testing of the upcoming changes to the context handling [1] I
realized that some PGE tests [2] are only failing with this patch installed.
I traced the created code on two different machines (the other w/o the
patch) and diffed the trace log. After a few rounds through the match
loop, one
On Thu, Jun 30, 2005 at 04:44:04PM +0200, Leopold Toetsch wrote:
> During testing of the upcoming changes to the context handling [1] I
> realized that some PGE tests [2] are only failing with this patch installed.
> I traced the created code on two different machines (the other w/o the
> patch)
# New Ticket Created by Will Coleda
# Please include the string: [perl #36437]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/rt3/Ticket/Display.html?id=36437 >
Attempting to come up with a simplistic math grammar that has one possible
operand (A)
On Thu, 2005-06-30 at 19:36 +0200, Leopold Toetsch wrote:
> Brian Wheeler wrote:
> > Its been a while since I tinkered with parrot so I thought I'd start
> > playing again...but I've hit a segfault.
>
> Should of course not happen... But it seems that the codegen is mixing
> old and new calling c
On Wed, 29 Jun 2005, Leopold Toetsch wrote:
> Chip Salzenberg wrote:
> > { This is a partial reply; what with YAPC I didn't finish, but a new
> > version of the patch from Leo will give me time to catch up }
> >
> > I've reviewed the patch. I appreciate what you're doing with it, but
> > there
Nice summary with examples:
ftp://ftp.inf.puc-rio.br/pub/docs/techreports/04_15_moura.pdf
and we still have to define semantics of parrot couroutines, e.g. WRT
argument passing. See also Dan's blogs about couroutines,
leo
Leo~
On 6/30/05, Leopold Toetsch <[EMAIL PROTECTED]> wrote:
> Nice summary with examples:
>
> ftp://ftp.inf.puc-rio.br/pub/docs/techreports/04_15_moura.pdf
>
> and we still have to define semantics of parrot couroutines, e.g. WRT
> argument passing. See also Dan's blogs about couroutines,
I pre
On Jun 30, 2005, at 21:55, Matt Fowles wrote:
Leo~
On 6/30/05, Leopold Toetsch <[EMAIL PROTECTED]> wrote:
Nice summary with examples:
ftp://ftp.inf.puc-rio.br/pub/docs/techreports/04_15_moura.pdf
and we still have to define semantics of parrot couroutines, e.g. WRT
argument passing. See al
# New Ticket Created by Will Coleda
# Please include the string: [perl #36438]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/rt3/Ticket/Display.html?id=36438 >
Leo would like it if the tcl todo tests were silent instead of verbose.
Someone pleas
Yves has some controversial ideas about what is and is not data structure
equivalence. I'd like comments on it.
- Forwarded message from demerphq <[EMAIL PROTECTED]> -
From: demerphq <[EMAIL PROTECTED]>
Date: Thu, 30 Jun 2005 23:17:19 +0200
To: Michael G Schwern <[EMAIL PROTECTED]>
Subj
Yves wrote:
> Ok, ive started work on this, however there is a minor problem: The
> test in circular_refs regarding rt.cpan.org 11623. (I added names to
> make it easier to work with.)
>
> {
> # rt.cpan.org 11623
> # Make sure the circular ref checks don't get confused by a reference
>
On Thu, Jun 30, 2005 at 09:44:06AM +0200, demerphq wrote:
> > Out of curiousity, if Data::Dumper::Streamer can handle
> > closures why not fix B::Deparse?
>
> I'm not really sure what you mean by "fix" B::Deparse. B::Deparse does
> exactly what it says it does: it deparses code. We can't consider
Yuval Kogman wrote:
As I understand it SMD is now not much more than a mechanism to
place a constraint on the MMD, saying that there can only be one
method or subroutine with the same short name.
Why is this the default?
Otherwise you lose this quite useful warning if the signatures didn't
matc
On Thu, Jun 30, 2005 at 05:09:39PM -0700, Michael G Schwern wrote:
>
> So, I conclude that is_deeply()'s behavior is ok and something like
> Test::Deep should be enhanced with an option to deal with this
> problem.
So, am I correct in understanding that is_deeply will only notice
value difference
Thanks to Matt Diephouse, partcl (parrot on tcl) is now able to run
part of tcl's cvs-latest test suite. We don't run enough of tcl at
the moment to run the tests natively, but by pulling the tests out of
the tcltest framework and converting them (sanely, we hope), we are
now passing > 10%
On Jun 25, 2005, at 20:38, Patrick R. Michaud wrote:
I've just checked in changes to PGE that enable it to support
grammars, as well as some more built-in rules...
These are totally awesome. On the plane today, I converted the Punie
parser over to use the shiny new grammars. My one frustratio
On Fri, Jul 01, 2005 at 13:42:34 +1200, Sam Vilain wrote:
> Yuval Kogman wrote:
> >As I understand it SMD is now not much more than a mechanism to
> >place a constraint on the MMD, saying that there can only be one
> >method or subroutine with the same short name.
> >Why is this the default?
>
> O
On Thu, 2005-06-30 at 04:33 +, David Formosa (aka ? the Platypus)
wrote:
> I'm just wondering if a documentation trait on subs would be usefull.
> If we are going to have something like p6explain the doc trait could
> be used as the source for the infomation for it. p6explain would
> simply h
On 7/1/05, Michael G Schwern <[EMAIL PROTECTED]> wrote:
> After talking with Ovid some in the kitchen I'm of the opinion that
> is_deeply() is currently doing the right thing and that these tests cannot
> go. Largely it comes down to the Principle of Least Surprise.
I cant agree with this analysi
On 7/1/05, demerphq <[EMAIL PROTECTED]> wrote:
> The question you have to ask yourself is why should a reference be
> treated different from any other value? It is a VALUE.
> IE: why should
In the following part i meant to make it more clear:
by changing this line
>
> $x=1;$y=2;$z=3;
to
$
On 7/1/05, Michael G Schwern <[EMAIL PROTECTED]> wrote:
> On Thu, Jun 30, 2005 at 09:44:06AM +0200, demerphq wrote:
> > > Out of curiousity, if Data::Dumper::Streamer can handle
> > > closures why not fix B::Deparse?
> >
> > I'm not really sure what you mean by "fix" B::Deparse. B::Deparse does
> >
28 matches
Mail list logo
