Jeff G:
# Now I'll be the first to admit that I'm probably not the most coherent
# in the world at (looks at the clock) 1:19 A.M. but I'm sitting here
# trying to get something like a PerlInt_Array ready for compilation and
# noticing some problems. It's also entirely possible that I'm
# looking a
Now I'll be the first to admit that I'm probably not the most coherent
in the world at (looks at the clock) 1:19 A.M. but I'm sitting here
trying to get something like a PerlInt_Array ready for compilation and
noticing some problems. It's also entirely possible that I'm looking at
this in the wron
With a little bit of substitution magic, a serious abuse of dynamic
linking, a count or two of using static data improperly, mod_parrot
can now have scripts which output to the users' web browser.
I think they're coming to take me away... put me in a little blue
room for a while...
If you want
classes/ now has a real Makefile.in
Configure.pl now dynamically builds classes/Makefile, and no longer
passes in -I./include as an expanded parameter.
Makefile.in has the classes/perl*.o targets removed, replaced with a 'cd
classes; make' target.
This is done in anticipation of being able to dec
On Saturday 01 December 2001 09:24 pm, Bryan C. Warnock wrote:
{snip}
Er, obviously, s/is/should be/g in my response.
--
Bryan C. Warnock
[EMAIL PROTECTED]
On Saturday 01 December 2001 01:50 pm, Jeff 'japhy' Pinyan wrote:
> $x = "_" x 100_000;
> $a = $x; $b = $x; $c = $x;
>
> $x is now copy-on-write, with three dependents.
>
> $x = "foo";
>
> According to you model, we've just copied 300,000 bytes. Personally, I
> find that unacceptable. Be
On Sat, 1 Dec 2001, Simon Cozens wrote:
> On Fri, Nov 30, 2001 at 03:45:44PM -0800, Hong Zhang wrote:
> > It may be a good idea to have our own version of vsnprintf().
>
> No, I *want* us to have our own version of vsnprintf. Please steal
> one from Perl!
Chip's the original author of that. I'
I couldn't get parrot to make on Irix / MIPSPro, as the perlnum.c
files had errors, I know these are generated, but I like being naughty
and got a compiled something by doing the thing below.
Also, if people change Makefile.in, can they make sure they call perl
$(PERL) rather than perl as sometim
On Sat, 1 Dec 2001, Dan Sugalski wrote:
> At 01:20 PM 12/1/2001 -0500, Jeff G wrote:
> >I'll probably pull out perl5's snprintf function and
> >add it to the vtables.
>
> Unfortunately I'll say the dreaded "L" word here...
>
> Licensing.
Wow, are we still running this project without a license?
At 09:30 AM 12/1/2001 -0800, Brent Dax wrote:
>First of all, you sent us this already. :^)
>
>Jeff 'japhy' Pinyan:
># I'm writing a simple language to embody the concept of
># copy-on-write, and
># so that I can learn how to implement it. The language is
># called COW and
># it's at
>#
># http
At 01:20 PM 12/1/2001 -0500, Jeff G wrote:
>I'll probably pull out perl5's snprintf function and
>add it to the vtables.
Unfortunately I'll say the dreaded "L" word here...
Licensing.
I don't think we can do this. If you do it as an interim thing, and I think
it's a bad idea (though I'll leave
> "J'P" == Jeff 'japhy' Pinyan <[EMAIL PROTECTED]> writes:
J'P> $x = "_" x 100_000;
J'P> $a = $x; $b = $x; $c = $x;
J'P> $x is now copy-on-write, with three dependents.
J'P> $x = 'foo';
J'P> We copy the 100,000 byte string to $a, $a gets $b and $c as dependents,
J'P> an
On Dec 1, Brent Dax said:
>First of all, you sent us this already. :^)
Well, I sent it before I subscribed (and from a different account
entirely) and it hadn't showed up in the archives 12 hours after posting,
so I figured it was dixed.
># So what's copy-on-write? Basically, it's the use of
Applied Andy's patch just to keep the tree sane while the actual issue
gets worked out. I'll probably pull out perl5's snprintf function and
add it to the vtables. One other issue I can see in the vtable stuff is
that there's no easy way to add a library of vtable operations (such as,
in this case
First of all, you sent us this already. :^)
Jeff 'japhy' Pinyan:
# I'm writing a simple language to embody the concept of
# copy-on-write, and
# so that I can learn how to implement it. The language is
# called COW and
# it's at
#
# http://japhy.perlmonk.org/COW/
#
# Ben Tilly suggested I con
I'm writing a simple language to embody the concept of copy-on-write, and
so that I can learn how to implement it. The language is called COW and
it's at
http://japhy.perlmonk.org/COW/
Ben Tilly suggested I contact the Perl6 Internals folk and let you know
that this is an important feature th
16 matches
Mail list logo
