Brent Dax wrote:
Leopold Toetsch:
# - string_set() is gone, highly (WRT malloc) illegal reusage
# of existing
# string headers - and unnecessary IMHO
I specifically asked for and received permission from Dan for this.
It's designed to remove the need to pass in
pointers-to-pointers-to-headers
Andy Dougherty (via RT) wrote:
# New Ticket Created by Andy Dougherty
# Please include the string: [perl #18191]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt2/Ticket/Display.html?id=18191 >
Thanks, applied with Parrot_destroy changes,
leo
I read Allison's topicalization piece:
http://www.perl.com/pub/a/2002/10/30/topic.html
I started with a simple thought:
is given($foo)
seems to jar with
given $foo { ... }
One pulls in the topic from outside and
calls it $foo, the other does the reverse --
it pulls in $foo from th
For all you Mac OS X fans out there:
http://www.earthlingsoft.net/UnicodeChecker/
Regards,
David
--
David Wheeler AIM: dwTheory
[EMAIL PROTECTED] ICQ: 15726394
http://david.wheeler.net/ Yahoo!: dew7e
Leopold Toetsch:
# - string_set() is gone, highly (WRT malloc) illegal reusage
# of existing
# string headers - and unnecessary IMHO
I specifically asked for and received permission from Dan for this.
It's designed to remove the need to pass in
pointers-to-pointers-to-headers in functions with s
Leo --
Here's one of the early fingerprinting patches, 2001-09-14:
http://archive.develooper.com/perl6-internals@;perl.org/msg04063.html
Here's where Simon removed Digest::MD5, 2001-09-18:
http://archive.develooper.com/cvs-parrot@;perl.org/msg00151.html
Here's one of the messages abou
[EMAIL PROTECTED] wrote:
All --
FWIW, this stuff came up early on in Parrot's infancy.
Pointers, hints, information ...
On a related note, I'm working on a toy VM outside of Parrot to
demonstrate the technique I've proposed here in the past,
Pointers, hints, information ...
thanks,
leo
Finally and after more changes I like to ci in one bunch, the parrot
interpreter is (almost) memory leak free.
Summary
Currently broken test:
- t/op/interp_2 with standard allocator and --gc-malloc
Memory leakages:
- PIO (PIO_new doesn't remember ParrotIO structures)
- rx (bitmaps)
- intstack (
All --
FWIW, this stuff came up early on in Parrot's infancy. At one time we had
fingerprinting, then we removed it. At one time it was MD5, then we went
away from MD5. IM(NS)HO, the better approach overall is to remove the need
for fingerprinting altogether. I used to know roughly how to get f
I added a local to $_ in t/src/manifest.t to avoid an undef warning in
5.005_03's File::Find
Nicholas Clark
--
Befunge better than perl? http://www.perl.org/advocacy/spoofathon/
> Mailing-List: contact [EMAIL PROTECTED]; run by ezmlm
> Date: 3 Nov 2002 14:58:52 -
> From: Smylers <[EMAIL PROTECTED]>
> X-Posted-By: 193.237.84.140
>
> Michael Lazzaro wrote:
>
> > Agreed: the value of comparing a boolean with anything else is not
> > particularly sensible in *any* langua
Peter Gibbs wrote:
Clinton A. Pierce wrote:
LOOP: new P1, .PerlHash
branch LOOP
This is simply a long-standing GC bug. Try the attached patch and see if
it helps.
Thanks for clarifying this. Actually, when introducing GC_IS_MALLOC I
was bug compatible too ;-)
Patch included in Parrot_
Michael Lazzaro wrote:
> Agreed: the value of comparing a boolean with anything else is not
> particularly sensible in *any* language.
It isn't particularly unsensible in PHP.
PHP only has one equality operator. If its operands are of different
types then it casts one operand to match the other
Josh Wilmes wrote:
FYI- I just re-indented a bunch of code, using the tools/dev/run_indent.pl
script.
I see really no need for quoting this stuff and plz next time wait, until
real changes are committed - I did announce them.
--Josh
Thanks,
leo
Damian Conway <[EMAIL PROTECTED]> writes:
> Piers Cawley wrote:
>
>> So, on the train this morning, I had a moment of Satori. What's wrong
>> with doing what we think of as bitwise operations using the flexops
>> and adding a 'bitwise' context? So, a bitwise op becomes:
>>bitwise ( $a | $b | $
Clinton A. Pierce wrote:
> LOOP: new P1, .PerlHash
> branch LOOP
> What happens is that memory gets chewed up
> quickly. Do I have the wrong idea of how the Px registers are used to
point
> to things (god, I hope not) or is there some GC that needs to happen that
> isn't (and I can expect it t
On Mon, 2002-10-28 at 14:41, Larry Wall wrote:
> And maybe:
>
> A bitwise operator is just a logic operator scoped to a set of bits.
Hypo-operators. :-)
--
Bryan C. Warnock
bwarnock@(gtemail.net|raba.com)
Matthew Zimmerman wrote in perl.perl6.language :
>
> So let me make my original question a little more general: are Perl 6 source
> files encoded in Latin-1, UTF-8, or will Perl 6 provide some sort of
> translation mechanism, like specifying the charset on the command line?
I expect probably some
Larry wrote:
> $z = 0 but true;
> I'm not even particularly upset by this:
> my bool $x = $z;# $x == 1
Yep, that's all I mean. I just want things like:
my bool $lit = ($light eq "on");
if $lit { ... }
to work such that (1) 'bool' always stores the "truth" of the
e
19 matches
Mail list logo
