folks,
Attached is a patch to Devel::Size which computes CV / coderef sizes.
It includes some bad/place-holder pod.
Feedback (off this list) is welcome.
tia
Jim Cromie
patch.dsize.60_06.bz2
Description: BZip2 compressed data
Dan Sugalski wrote:
Hey folks.
It's that time of year again, when the patch pumpkin passes paws. Hands,
rather. Steve Fink now joins the ranks of Parrot Pumpkings Emeritus,
having shepherded a number of releases out the door. We wish him a happy
retirement and hope the nervous twitches stop soon.
following corrects 1 remaining use of bare 'perl' to match all the other
uses of $(PERL)
--- root.in~Sun Aug 10 15:54:44 2003
+++ root.inSun Aug 10 17:58:02 2003
@@ -480,7 +480,7 @@
cpu_dep$(O) : $(GENERAL_H_FILES)
nci.c : call_list.txt build_nativecall.pl
-perl build_nativecall.pl ca
Jerome Quelin wrote:
Steve Fink wrote:
I'm assuming this will be 0.0.10
codename?
I could be persuaded to call it 0.1.0
codename?
Jerome
while trolling for things parrot, I came upon this;
http://www.kingsnicknames.co.uk/
Towards the bottom of this paragraph is the HIT, from
Nicholas Clark wrote:
Admittedly my program may not be portable Ook! as it does assume that
cells wrap round from 255 to 0
The original brainfuck version worked fine on Leon's interpreter.
(I find Ook! too hard - I'm just another brainfuck monkey)
Nicholas Clark
.
I hesitate to suggest (se
Dan Sugalski wrote:
At 7:35 AM -0500 12/31/02, Jim Cromie wrote:
pardon the lack of clue I reveal here, but..
on 32 bit box, a void* has 3 values which are illegal/unaligned;
void* ptr;
if (ptr & 0x00) {
/* ok */
} else {
/* some exceptional situation */
}
is there any conciev
pardon the lack of clue I reveal here, but..
on 32 bit box, a void* has 3 values which are illegal/unaligned;
void* ptr;
if (ptr & 0x00) {
/* ok */
} else {
/* some exceptional situation */
}
is there any concievable use of this which doesnt interfere with
legitimate bus-errors (ie exi
Nicholas Clark wrote:
>
>An IRC channel is good for discussions. But it doesn't archive them,
>index them, collate them and provide them as reference for any new
>would be recruits. I'm not saying that anyone has to write the docs, or
>even the skeleton of the docs for their code - everyone and a
