Piers Cawley <[EMAIL PROTECTED]> wrote:
> Leopold Toetsch <[EMAIL PROTECTED]> writes:
>> ... While S registers hold pointers, they have
>> value semantics.
> Is that guaranteed? Because it probably needs to be.
It's the current implementation and tested.
>> This would restore the register co
Sam Ruby <[EMAIL PROTECTED]> wrote:
> Leopold Toetsch wrote:
> So *all* lookups (complete with the asterisks) does not mean *all* lookups.
> How about ?
Let's first concentrate on simpler stuff like infix operators.
>> Citing S06: "Operators are just subroutines with special names."
> That sta
Hi,
I ran the codestriker (http://codestriker.sourceforge.net/) test set
using Devel::Cover. The test cases ran over a day and a half
and generated a cover_db directory that is 127 megs. Attempting to run
the cover command keeps using up all of the available memory causing
cover to be killed by th
On Dec 7, 2004, at 9:25 PM, Andrew Savige wrote:
/* Horrible hacky thread-unsafe version but no XX */
...
static const char* g_file;
static unsigned long g_line;
i forgot to mention, the way around the non-thread-safety here is to
use thread-local storage.
c.f. pthread_key_create() and p
Clayton, Nik wrote:
>> You might want to throw it in as an option. I'm going to change
>> Test::More so it no longer mucks with the exit code by default, you'll
>> have to turn this feature on.
>
> OK. I'll track changes to Test::Harness, and libtap'll stop
> doing it when T::H stops.
Or, more
First, there was some dicussion not too long ago:
Subject: Numeric semantics for base pmcs [1]
Subject: Last bits of the basic math semantics
The current Integer PMC doesn't yet follow the results of these threads.
Basic behavior of that type is Perl6 or Python semantics, which is: it's
basicall
Ah! Now we are getting somewhere!
Leopold Toetsch wrote:
Sam Ruby <[EMAIL PROTECTED]> wrote:
Leopold Toetsch wrote:
So *all* lookups (complete with the asterisks) does not mean *all* lookups.
How about ?
Let's first concentrate on simpler stuff like infix operators.
OK, but the point is that the
Dan Sugalski <[EMAIL PROTECTED]> wrote:
> pushmark 12
> popmark 12
> pushaction Psub
I've now implemented these bits. I hope it's correct, specifically, if a
return continuation in only captured, the action handler is not run.
See t/pmc/exceptions.t
Still missing is the throw opco
Sam Ruby <[EMAIL PROTECTED]> wrote:
> Ah! Now we are getting somewhere!
Yeah. That's the goal.
> So, why have I proceeded in this manner? Two reasons.
Fair enough, both.
>> So given that we have a set of language-neutral PMCs in core that do the
>> right thing, Python or Perl PMCs can inherit
Leopold Toetsch wrote:
Good. Now Evil Leo (who can't program in Python ;) writes some piece of
code like this:
$ cat m.py
class M(type):
def __new__(meta, name, base, vars):
cls = type.__new__(meta, name, base, vars)
cls.__add__ = myadd
return cls
def myadd(self, r):
On Tue, Dec 07, 2004 at 10:36:53PM -0800, Larry Wall wrote:
: But somehow I expect that when someone writes () they probably
: usually meant («foo»).
If we're going to stick with the notion that captures and something
else doesn't, I'm beginning to think that the other thing isn't «foo» for
a cou
Larry Wall wrote:
Another problem we've run into is naming if there are multiple assertions
of the same name. If the capture name is just the alpha part of the
assertion, then we could allow an optional number, and still recognize
it as a "ws":
Except I can well imagine people wanting number
On Wed, Dec 08, 2004 at 08:19:17AM -0800, Larry Wall wrote:
> And people would have to get used to seeing ? as non-capturing assertions:
>
>
>
>
>
> This has a rather Ruby-esque "I am a boolean" feeling to it. I think
> I like it. It's pretty easy to type, at least on my
On Tue, Dec 07, 2004 at 07:21:09PM -0800, Jason Remillard wrote:
> I ran the codestriker (http://codestriker.sourceforge.net/) test set
> using Devel::Cover. The test cases ran over a day and a half
> and generated a cover_db directory that is 127 megs. Attempting to run
> the cover command keeps u
Larry Wall writes:
> If we're going to stick with the notion that captures and
> something else doesn't, I'm beginning to think that the other thing
> isn't Âfoo for a couple of reasons.
I just sat down to say the exact same thing. I'm glad you beat me to
it.
> And people would have to get use
On Wed, 8 Dec 2004 08:19:17 -0800, Larry Wall <[EMAIL PROTECTED]> wrote:
> / $ := [ () = (\N+) ]* /
You know, to be honest I don't know that I want rules in one-liners to
capture by default. I certainly want them to capture in rules, though.
> And people would have to get used to seeing ? as
Leopold Toetsch <[EMAIL PROTECTED]> writes:
> Piers Cawley <[EMAIL PROTECTED]> wrote:
>> Leopold Toetsch <[EMAIL PROTECTED]> writes:
>
>>> ... While S registers hold pointers, they have
>>> value semantics.
>
>> Is that guaranteed? Because it probably needs to be.
>
> It's the current implementa
Sam Ruby <[EMAIL PROTECTED]> wrote:
> Leopold Toetsch wrote:
> Here's the part that you snipped that addresses that question:
>> And there is a piece that I haven't written yet that will do the
>> reverse: if MMD_ADD is called on a PyObject that has not provided
>> such behavior, then
Piers Cawley <[EMAIL PROTECTED]> wrote:
> Leopold Toetsch <[EMAIL PROTECTED]> writes:
>> The problem I have is: do we know where registers may be reset? For
>> example:
>>
>> $I0 = 10
>> loop:
>> $P0 = shift array
>> dec $I0
>> if $I0 goto loop
>>
>> What happens if the array PMC
Attached is a patch that changes the split opcode to use an Array
instead of a PerlArray.
It also updates the documentation to note this.
All the tests still pass, and a grep in the languages/ directory shows
that no language implementations are effected.
- James
Will Coleda (via RT) wrote:
# N
Leopold Toetsch wrote:
Sam Ruby <[EMAIL PROTECTED]> wrote:
Leopold Toetsch wrote:
Here's the part that you snipped that addresses that question:
> And there is a piece that I haven't written yet that will do the
> reverse: if MMD_ADD is called on a PyObject that has not provided
> such beha
Leo~
On Wed, 8 Dec 2004 20:29:00 +0100, Leopold Toetsch <[EMAIL PROTECTED]> wrote:
> So my conclusion that (in combination with restoring registers to the
> values of continuation creation) I,S,N registers are almost unusable is
> correct?
I would disagree. Let me take the above example and wor
Sam Ruby <[EMAIL PROTECTED]> wrote:
[ snipped - all ok }
> If I define an __add__ method with 16 arguments, Python will not throw
> an exception.
I didn't write that. I've said: *if* you call it via "a + b", Python
throws an exception - that one I've shown. Anyway...
> If this is done at runtim
Leopold Toetsch wrote:
Sam Ruby <[EMAIL PROTECTED]> wrote:
[ snipped - all ok }
If I define an __add__ method with 16 arguments, Python will not throw
an exception.
I didn't write that. I've said: *if* you call it via "a + b", Python
throws an exception - that one I've shown. Anyway...
What you wro
Ashley Winters writes:
> I'm thinking capturing rules should be default in rules, where they're
> downright useful. Your hour/minute/second comment brings up parsing
> ISO time:
>
> grammar ISO8601::DateTime {
> rule year { \d<4> }
> rule month { \d<2> }
> rule day { \d<2> }
> rule
I've set up anonymous read-only access to my Subversion repo, so
anyone that wants to play with libtap easily can now:
svn checkout svn://jc.ngo.org.uk/nik/libtap/trunk/
Share and enjoy.
N
Warning: excessive nitpicking ahead.
Ashley Winters skribis 2004-12-08 10:51 (-0800):
> rule year { \d<4> }
\d**{4}
Or, well, \d**{2,4}
> rule month { \d<2> }
\d**{2}
> rule date { -? -? }
rule week { \d**{2} }
rule yday { \d**{3} }
rule date {
On Tue, Dec 07, 2004 at 12:32:50PM -0500, Abhijit Mahabal wrote:
: According to S12, it is possible to supply the object layout to bless(),
: like so:
:
: $object = $class.bless(:CREATE[:repr] :k1($v1) :k2($v2))
:
: But in the section "Introspection", "layout" is a class trait. Does this
: mean
On Wed, Dec 08, 2004 at 11:09:30AM -0700, Patrick R. Michaud wrote:
: On Wed, Dec 08, 2004 at 08:19:17AM -0800, Larry Wall wrote:
: > And people would have to get used to seeing ? as non-capturing assertions:
: >
: >
: >
: >
: >
: > This has a rather Ruby-esque "I am a bool
On Wed, Dec 08, 2004 at 11:50:51AM -0700, Luke Palmer wrote:
: > Now suppose that we extend that "I am a boolean" feeling to
: >
: >
: >
: > which might take the place of the confusing <(...)>, and make consistent
: > the notion that we always use {...} to invoke "real" code.
:
: Hmm... I'
On Tue, Dec 07, 2004 at 11:33:54AM -0800, Kevin Scaldeferri wrote:
> I'm wondering if I'm the only one who would love to see
> Devel::Cover::Regex? Many (most?) perl programs are pretty regex
> heavy, and if we are honest with ourselves, we have to admit that each
> regex is actually a program
Is there a plan at any point to move to an svn repository from cvs?
I'd like to work on a patch to move all the perl* pmcs into dynclasses, which would involve quite a bit of file moving, and I'll happily wait for svn if we're going that way, since it'll be smoother.
Thanks, applied!
James deBoer wrote:
Attached is a patch that changes the split opcode to use an Array
instead of a PerlArray.
It also updates the documentation to note this.
All the tests still pass, and a grep in the languages/ directory shows
that no language implementations are effected.
-
> On Mon, Dec 06, 2004 at 10:28:45PM -0600, Andy Lester wrote:
> I think even better than
>
> ok( $expr, "name" );
>
> or
>
> ok( $expr, "comment" );
>
> is
>
> ok( $expr, "label" );
>
> RJBS points out that "comment" implies "not really worth doing", and I
> still don't like "name" be
Will~
On Wed, 08 Dec 2004 19:19:07 -0500, William Coleda <[EMAIL PROTECTED]> wrote:
> Is there a plan at any point to move to an svn repository from cvs?
>
> I'd like to work on a patch to move all the perl* pmcs into dynclasses, which
> would involve quite a bit of file moving, and I'll happil
On Wed, 8 Dec 2004 16:07:43 -0700, Luke Palmer <[EMAIL PROTECTED]> wrote:
> Ashley Winters writes:
> > For a grammar, that works perfectly!
>
> Yep.
>
> > In a one-liner, I'd rather just use:
> >
> > $datetime ~~ /$year := (\d+) -? $month := (\d+) -? ./
>
> Then go ahead and use that. If yo
> While I personally like the idea, I think it is unlikely given how
> much slower svn is on sizable repositories. Of course I have not
> tried it recently, so maybe that has changed...
> All that being said, I am in absolutely no position of authority about this...
This is, and always has been,
On Wed, 8 Dec 2004 16:07:43 -0700, Luke Palmer <[EMAIL PROTECTED]> wrote:
Ashley Winters writes:
In a one-liner, I'd rather just use:
$datetime ~~ /$year := (\d+) -? $month := (\d+) -? ./
I'm starting to think that this '$year := ' syntax is an obfuscator. We
couldn't refer to that capture wi
On Wed, Dec 08, 2004 at 10:16:21PM -0500, Matt Fowles wrote:
> While I personally like the idea, I think it is unlikely given how
> much slower svn is on sizable repositories. Of course I have not
> tried it recently, so maybe that has changed...
If you wish to try out a recent Subversion on some
--- "Clayton, Nik" wrote:
> Any "Writing thread safe libraries for dummies" texts you could point
> me at?
I recommend "Programming with POSIX Threads" by David Butenhof.
Re the varargs ok() business, I assume you'll be using some sort of
config.h with your libtap library. Any plans on using aut
40 matches
Mail list logo
