Re: [svn:parrot] r18971 - trunk/config/gen/makefiles

On Jun 13, 2007, at 11:11 AM, [EMAIL PROTECTED] wrote: Log: Make 'headerizer' depend on 'fingerprint.c', so that it can run right after 'make realclean; perl Configure.pl' Thanks for doing this, Bernhard. I'm glad to have someone else workin'

Re: Parrot at YAPC::NA::2007 in Houston

27;ve marked it too. -- Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance

Parrot_get_runtime_prefix has a bad interface

plit into Parrot_get_runtime_prefix_string and Parrot_get_runtime_prefix_cstring. Anything I'm missing? Dissent? xoxo, Andy -- Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance

Re: [svn:parrot] r19088 - trunk/src/pmc

On Jun 18, 2007, at 3:38 PM, chromatic wrote: Does this compile for you? I don't think the PMC to C translator picks up the "const" here. Sorry, my bad. I modified an autogenerated header file. :-( -- Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance

memcpy

when we're passing around structs. Clearly this won't work everywhere. -- Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance

Re: [perl #43241] [PATCH] [CAGE] include/parrot/string.h typedefs STRING and String are redundant

On Jun 18, 2007, at 11:28 AM, Mark Glines (via RT) wrote: Here's a patch to consolidate that, and standardize on STRING (based on the fact that it's used *much* more often than String is). And also isn't String a standard C++ class? I've applied your patch. Tha

Re: 0.4.13 Release Code Slush

ructs that should be modified for safety and portability. Thanks, xoxo, Andy -- Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance

Re: [perl #43241] [PATCH] [CAGE] include/parrot/string.h typedefs STRING and String are redundant

On Jun 19, 2007, at 2:33 AM, Paul Cochrane via RT wrote: Does this close this ticket, or are there still outstanding instances? No, that closes it. Thanks for taking care of it. -- Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance

bignum.c seems to be unused

bignum.c seems to be entirely unused. Everything builds just fine without it. There are many lint errors in it, such as int functions returning with "return;" and no value. Can we throw it away? Move it somewhere out of the way? -- Andy Lester => [EMAIL PROTECTED] =>

Re: [svn:parrot] r19168 - trunk/src

scares me, because on the BSD box I was using it was in something that wasn't math.h, which surprised me. So I did what I did. -- Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance

Re: memcpy

e the need to document a standard C behavior with a macro. We don't have #define inc(x) (x)++ do we? xoxo, Andy -- Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance

Re: memcpy

problem, and one that I'm happy to have some runtime support in locating. My point is that *d = *s; is no more a weird cryptic construct than n++; or while (*s) *d++ = *s++; for that matter. -- Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance

Re: r19207 - in trunk: compilers/imcc config/gen/makefiles tools/build

ven asking. I updated your fix so that it's "INLINE" macroing to "inline". Otherwise, I might not be including parrot.h and it'll work for me, but still fail for you. This way, INLINE will fail unless we're using parrot.h -- Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance

Re: memcpy

On Jun 21, 2007, at 1:39 AM, Allison Randal wrote: Andy Lester wrote: I guess I don't see the need to document a standard C behavior with a macro. If you had read all the way through the message, you would see that the biggest benefit is the ability to hang debugging hooks of

Struct copying

We now have STRUCT_COPY(dest,src) and STRUCT_COPY_N(dest,src,n) for all your struct-copying needs. xoxo, Andy -- Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance

Summary of today's digging into t/compiler/pge/06-grammar.t

es. ==1002== ==1002== LEAK SUMMARY: ==1002==definitely lost: 10,981 bytes in 641 blocks. ==1002== possibly lost: 576 bytes in 2 blocks. ==1002==still reachable: 4,269,562 bytes in 2,489 blocks. ==1002== suppressed: 0 bytes in 0 blocks. ==1002== Use --leak-check=full to see deta

What should I work on at the hackathon tomorrow and Friday?

I'm taking requests: http://use.perl.org/~petdance/journal/33615 xoxo, Andy -- Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance

t/codingstd/perlcritic.t needs to be optional

The Perl::Critic testing in t/codingstd/perlcritic.t needs to be optional. The existence of Perl::Critic on a machine doesn't mean that it's appropriate to run Perl::Critic on the Parrot code. xoa -- Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance

Re: t/codingstd/perlcritic.t needs to be optional

On Jun 27, 2007, at 3:22 PM, Andy Lester wrote: The Perl::Critic testing in t/codingstd/perlcritic.t needs to be optional. The existence of Perl::Critic on a machine doesn't mean that it's appropriate to run Perl::Critic on the Parrot code. Following up, it takes almost 11 un

Re: t/codingstd/perlcritic.t needs to be optional

On Jun 27, 2007, at 11:50 PM, chromatic wrote: I'd like to see an option to run it only on *modified* files. Modified since when? -- Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance

Re: t/codingstd/perlcritic.t needs to be optional

on a given VCS. I know Parrot's hosted in Subversion, but what about the Git folks? It smells funny to me. -- Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance

Re: t/codingstd/perlcritic.t needs to be optional

On Jun 28, 2007, at 12:52 AM, chromatic wrote: Heck, you didn't even *compile* before one of your checkins yesterday. Yeah, I did. I just had modified something else on a wild tear, forgot to revert it, and did a commit hours later. Sorry about that. -- Andy Lester => [EMAIL P

Re: t/codingstd/perlcritic.t needs to be optional

sults, too. That's what we do at work, and it's annoying, but it's there and it's pretty in-your-face. xoxo, Andy -- Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance

Re: [svn:parrot] r19381 - trunk/src/dynpmc

-- Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance

Re: [svn:parrot] r19381 - trunk/src/dynpmc

;n'replace. My only fear was that INTERP meant something different. -- Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance

Parrot and Perl 6 wikis moved to perlfoundation.org

lfoundation.org/hackathon-chicago/ -- The 2006 hackathon in Chicago * http://www.perlfoundation.org/hackathon-toronto/ -- The 2007 hackathon in Toronto Thanks to Socialtext for the hosting. -- Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance

Macros that assume variables are awful

Of course! We #define interp NULL! G xoxo, Andy -- Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance

Re: Building with icc

portability problem) CCWARN="-Wall" perl Configure.pl \ --cc="$CC" \ --cxx="$CX" \ --link="$CX" \ --ld="$CX" \ --ccflags="$CCFLAGS" \ --ccwarn="$CCWARN" \ -- Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance

About the headerizer

http://www.perlfoundation.org/parrot/index.cgi?headerizer I've started this page as my brain dump of ideas until I get it into a proper .pod file. Please add to it, or ask questions on the page, as you see fit. xoxo, Andy -- Andy Lester => [EMAIL PROTECTED] => www.p

Re: [svn:parrot] r19533 - trunk/docs

id is fine. In English text, it's not. -- Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance

Re: [perl #43481] t/examples/shootout.t (shootout_16.pir) fails on gentoo/x86

work. That I can't tell. All I'm looking at is the underlying C code, where it seems to me that passing in a rep of NULL should not be allowed. -- Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance

Re: Parrot and Perl 6 wikis moved to perlfoundation.org

Thank you so much for hosting these wikis up to now! (Also, thanks Socialtext for the ongoing hosting) Thanks for sayin'. That's the problem with JFDI, is you get stuck with what you D. xoxo, Andy -- Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance

Sun Studio on Solaris

I've set up a box at home running Solaris 10 with Sun Studio 12. If anyone wants an account on it so that they can work on the platform, let me know, preferably in IRC. xoxo, Andy -- Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance

Nulls for Parrot_make_COW_reference

not NULL. If I don't hear anything, I'll go ahead and do this tonight or tomorrow. xoxo, Andy -- Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance

Re: Building with icc

="$CC" \ --link="$CC" \ --ld="$CC" \ --ccflags="$CCFLAGS" \ --ccwarn="$CCWARN" \ I'm working on linker hints right now. -- Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance

ICC building

n. I think GCC just aggravates it. -- Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance

Unused variables

ous tools at our disposal when I get it working. xoxo, Andy -- Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance

Re: Splint runs!

On Jul 9, 2007, at 7:16 PM, James E Keenan wrote: Can you give us splint noobs a rundown on how to interpret this data? Thanks. Give us another couple of days to shake out the noise, 'kay? -- Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance

Re: [svn:parrot] r19794 - in trunk: compilers/imcc src

ve their own str_dup do. -- Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance

Checking for unused results

you have to add it manually. xoxo, Andy -- Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance

Splint upgrade released

ng time ago... --- Dave Andy Lester wrote: What would it take to get the CVS version of Splint released as 3.1.2? It fixes a number of bugs that I've run into as we use it on the Parrot project (http://parrotcode.org/). I'm using the CVS version from my own build, but I'd like

Who works on which platform?

Can y'all please go update this page and talk about what platforms you're using? I can never keep track of who's doing what. http://www.perlfoundation.org/parrot/index.cgi?platforms -- Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance

Documenting the PARROT_XXX macros

se macros are good, and consting is good, and all the seat belts I'm trying to put in place. I'm thinking a new doc is in order. Thoughts? -- Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance

Re: Parrot hackathon at OSCON

ils. Alas, I'll be leaving on Friday but will be around on Sunday before OSCON. Will anyone else be available for pre-OSCON hacking? -- Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance

Re: Parrot Scan login

ey might be pretty far out in my mind to remember. The Perl 5 codebase is RADICALLY different from the Parrot one, thank goodness. -- Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance

Re: Parrot Scan login

Subversion? If not, that's fine. It's just that I know I'm going to be waiting on pins & needles to see what new stuff Scan finds for us. Thanks, Andy -- Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance

Pre-OSCON hackathon

There's a p5 reposithon going on at Schwern's before OSCON. I'd like to hook up with Jonathan and whoever else is around pre-OSCON there, and have our own little Parrot hackathon on the corner. I'm sure Schwern will be fine with that. -- Andy Lester

Re: Pre-OSCON hackathon

ost of all I wanted to be able to make it to both hackathons. Then again, if it's just me & Jonathan, how much of a hackathon is that? -- Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance

Coverity scan results

Name Uninspected Bug False Ignore Pending Resolved Total parrot-0.4.13 722 0 0 0 7 81 Those 7 are all from me, I believe. The bugs are in RT. The rest I'm not sure about yet. I'm plodding through as I have time.

Re: [svn:parrot] r20058 - in trunk: . src

Log: [Coverity] USE_AFTER_FREE, set pointer to NULL after free so it could be returned safely. Excellent! Are you marking it in the Coverity system as RESOLVED? Thanks, xoxo, Andy -- Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance

Re: [svn:parrot] r20098 - in trunk: . compilers/imcc

On Jul 22, 2007, at 9:01 AM, [EMAIL PROTECTED] wrote: [Coverity] CID:67 USE_AFTER_FREE - reordered statements to correct problem I can't tell you how happy it makes me to see these. xoxo, Andy -- Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance

Re: [svn:parrot] r20101 - in trunk: . tools/build

On Jul 23, 2007, at 7:21 PM, chromatic wrote: I'm okay with that, but we should also decorate PANIC with PARROT_DOES_NOT_RETURN, which I believe *should* help compilers. I'm all over it, long ago. PANIC just wraps do_panic which is so decorated. -- Andy Lester => [EM

Re: [svn:parrot] r20101 - in trunk: . tools/build

On Jul 23, 2007, at 5:57 PM, Kevin Tew wrote: My thinking was that, should someone, someday change PANIC into a recoverable error, this will prevent leakage. Ok its a stretch. :) if it's unreachable, we need to get rid of it. PANIC is a dead-end. xoa -- Andy Lester => [EMAIL P

What I broke

5 1280 160 155 1-37 39-70 72 74-90 92- 96 98-160 t/pmc/exporter.t 6 1536126 1-6 t/pmc/objects.t1 25678 77 1-6 8-78 -- Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance

Re: What I broke

On Jul 24, 2007, at 8:43 AM, Andy Lester wrote: Here's what I know is broken because of changes I've made yesterday: t/compilers/imcc/syn/file.t 255 6528013 16 1-13 This is still broken, as is shootout (of course). t/library/test_builder_tester.t0 612

Re: [svn:parrot] r20172 - trunk/src/ops

as much as possible. -- Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance

Re: [svn:parrot] r20172 - trunk/src/ops

an be (PMC)NULL or it can be PMCNULL, a special non- null variable. See how it's defined in the header. -- Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance

Re: [svn:parrot] r20172 - trunk/src/ops

Because PMCNULL can be (PMC)NULL or it can be PMCNULL, a special non- null variable. See how it's defined in the header. I thought we fixed it. Let's fix it. I don't know what the broken is. We don't want a special PMCNULL value? What is the backstory on PMCNU

Re: [svn:parrot] r20172 - trunk/src/ops

PMCNULL is a singleton Null PMC. It's good. We like it. Hooray for PMCNULL. Except that PMCNULL is not a real NULL and therefore splint and lint and whatnot can't keep track of it getting somewhere it shouldn't be. -- Andy Lester => [EMAIL PROTECTED] =

Re: [svn:parrot] r20196 - in trunk: include/parrot src

On Jul 25, 2007, at 11:06 PM, chromatic wrote: or remote, I can go either way) or to mark failing tests as TODO before checkin if you know they're going to fail? Duh, duh, duh. I forgot about TODOs. Yeah, I'll do that. xoxo, Andy -- Andy Lester => [EMAIL PROTECTED] =>

Make a compile-to-bytecode option

Andy also needs we need a pbc disassembler where it dumps .pbc to pasm, if we don't have one. -- Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance

Thank you so much Josh Hoblitt for the backtracing

ke you failed 6 tests of 12. t/pmc/exporterdubious Test returned status 6 (wstat 1536, 0x600) -- Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance

headerizer phase 1 is complete

the pointers that it says are unprotected. xoxo, Andy -- Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance

Re: [PATCH] [PDD] PDD07: header guard example should use #ifndef

On Jul 30, 2007, at 9:56 PM, Mark Glines wrote: Also note that PDD07 actually has two header guard examples; grep for PARROT__H_GUARD and grep for PARROT_FOO_H_GUARD. I think these should be consolidated as well, but this patch does not address that. Done and committed. Thanks. -- Andy

Re: Floating point comparisons

0; The REAL question, I believe, is for comparisons to zero. Last ptc and I talked about this, there were no places where the comparison in question isn't against 0.0. Should simplify things a lot. xoxo, Andy -- Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance

Re: [perl #44291] [PATCH] Fix for suncc

. You can have the Sun compiler on other platforms, because Sun Studio, from version 10 onward, is freely available on non- Solaris platforms. xoxo, Andy -- Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance

My autodetect stuff

I just committed a patch that autodetects the HASATTRIBUTE_xxx attributes for GCC. It's kinda funky under Solaris, but still passes. Please let me know what happens on other platforms. I'm off to bed. xoxo, Andy -- Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance

Re: [svn:parrot] r20446 - trunk/config/auto

e the autosniffing I've done on the HASATTRIBUTE flags. xoxo, Andy -- Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance

Re: [perl #44379] config/auto/attributes.pm ought to use its own test_c.in

t; > my %eval = eval cc_run(); > return if !%eval; Have you looked at the string it returns? It looks like this: ( GCC_VERSION => 3, GCC_MINOR => 4 ); Or something similar. It perplexed me as well. -- Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance

Re: [Win32] There's a new compiler in town (sort of)

things out similarly on x86_64. ~jerry Does MS provide any cheapie installs of their compiler? I now have WinXP running on my Mac laptop and it would be swell if I could do builds on MSVC, too. xoxo, Andy -- Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance

Re: [Win32] There's a new compiler in town (sort of)

On Aug 7, 2007, at 10:25 AM, Andy Armstrong wrote: This any use? http://msdn.microsoft.com/vstudio/express/ Beautiful. Sure looks like it. xoxo, Andy -- Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance

Re: [svn ci] added support for decorators to pmc methods

? For the decorators to really make sense, we need both halves of the equation. -- Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance

Re: [svn ci] added support for decorators to pmc methods

des the default ones that already exists? That's what I'm thinking of. xoxo, Andy -- Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance

Re: [svn:parrot] r20562 - trunk/src/pmc

On Aug 8, 2007, at 10:58 AM, [EMAIL PROTECTED] wrote: -static PMC* undef(Interp* interp) +static PMC *undef(Interp *interp) And this should get changed to static PMC *undef(PARROT_INTERP) xoxo, Andy -- Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance

Re: [svn:parrot] r20562 - trunk/src/pmc

oxo, Andy -- Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance

Re: Need help in writing PCRE

ist to help you on this (assuming you're doing this in PHP). xoa -- Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance

Re: What is best location for position papers?

its permanent home. -- Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance

Re: `warn_unused_result' warnings

On Aug 11, 2007, at 10:11 AM, Bob Rogers wrote: All tests pass, so this is purely at the annoyance level. I'm running gcc 3.3.1; is it because that is too old? No, the autodetection doesn't do all we want yet. -- Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance

Fixing warn_unused_result

I don't have a gcc 3.3 anywhere. Any of you got one I can get to? -- Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance

Re: `warn_unused_result' warnings

he attribute must not work. xoa -- Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance

Re: [perl #38982] [CAGE] refactor long test files

getting their own, but why is 3000 lines a bad thing? xoa -- Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance

Statistical view of the history of Parrot

http://perlbuzz.com/2007/08/statistical-views-of-open-source-projects- on-ohloh.html -- Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance

Re: [perl #39088] [CAGE] Add conditional GCC attributes to functions

> You've done a lot of work on this in parrot already and I haven't seen > anything new as far as attributes go for a while. Have you finished > adding gcc attributes? If so, we can close this ticket. On attributes, I think so. Warning flags will be a separate projec

Re: mod_perl6 update

http://perlbuzz.com/project-hum/2007/09/first-mod-perl6-handlers.html -- Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance

please stop converting FUNCDOC headings to POD.

nefit when you consider the amount of boilerplate we'd be re-adding. -- Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance

Re: please stop converting FUNCDOC headings to POD.

7;ve headerized, which is all of them. > Back to DRY again, the biggest objection to using Pod is creating an > exact duplicate of the function signature in the Pod. More than anything, I want boilerplate gone. =item C is boilerplate. At the VERY least, remove the C<&g

Gone for a while

ct. So, I'm backing out of Parrot development for right now. If anyone needs me, you know where to find me. For that matter, if there's anything specifically that I can help with, please let me know. I just can't keep an eye on what's going on any more. xoxo, A

Re: Gone for a while

't have the time to talk about the things that I've been wanting to talk about for a while anyway. -- Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance

Re: [ANN] SF parrot win32

end-users (on Windows) and promote the use of Parrot. Beautiful. Thanks. http://perlbuzz.com/2007/12/parrotwin32-project-provides-prebuilt-windows-exec.html xoxo, Andy -- Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance

What's up with compilers/imcc?

When last I was playing with Parrot, I recall noises that imcc was not useful, and was effectively dead. Is this right, or am I misremembering? Is it worth my time to const & headerize it? If not, I'm pretty much done with headerizing. xoxo, Andy -- Andy Lester => [EMA

Re: [BUG] headerizer can't handle new file src/atomic/gcc_x86.c

tile *ptr, void *expect, void *update)" -- Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance

Re: [BUG] headerizer can't handle new file src/atomic/gcc_x86.c

I can't spare the brain bandwidth to dig into this further at the moment, so posting for others. BTW I have other headerizer stuff to update, like updating all the comments automagically so that the function declaration always matches the POD. -- Andy Lester => [EMAIL P

Memory checking I've been working on lately

es problems with your specific compiler. I'd especially like it if someone non-GCC has compiler options that we can put into PARROT_CANNOT_RETURN_NULL and its brethren so we have more compilers watching our backs. xoxo, Andy -- Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance

The headerizer and comment blocks

ow, I think that what I've got as the prototype above is 90% there, and gets rid of the tons of cut'n'paste that are sprinkled throughout the C code. Let me know your thoughts, so I can do more automation and run it on the rest of the source files. xoxo, Andy -- Andy Le

Consting args for vmethods

es particle: the role could be called 'enumerable' particle: and would have methods like elements(), next() first() etc particle: it's a good idea to take this to the list. discussion will ensue, i promise. -- Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance

Re: Consting args for vmethods

give up on the CONSTed selfs. -- Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance

Re: writing mod_perl6 in perl 6

On Dec 21, 2007, at 10:50 AM, Jeff Horwitz wrote: This just went up in my blog, but I think it's interesting enough to post to the list as well. URL? I'll post it to Mechanix. -- Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance

VTABLE_elements

Should we be allowing negative in the PMC elements() functions? Seems to me they'd be more appropriate as UINTVALs. xoa -- Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance

Re: VTABLE_elements

ing breaks? At this point, it's in a todo list in seatbelts.pod. -- Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance

Re: VTABLE_elements

What about when you want to implement things like, element -1 gets the last element of the array? That's the case in some languages, I believe... Yes, but we're talking about returning the number of elements in a PMC. That should never be negative. -- Andy Lester => [EM

<    1   2   3   4   5   >