All the Perl that's Practical to Extract and Report
use Perl Log In
speters (1787)
speters
(email not shown publicly)
http://www.fisharerojo.org/
AOL IM: fisharerojo (Add Buddy, Send Message)
mmm...Perl
(email not shown publicly)
http://www.fisharerojo.org/
AOL IM: fisharerojo (Add Buddy, Send Message)
mmm...Perl
Friday April 27, 2007
08:56 AM
[Perl 6 Microgrant] C++ Cleanup Adjustments
The other night, I sent in a large patch to cleanup some additional implicit void pointer casts that C++ simply cannot live with. particle gave me a great idea on IRC, however, for cleaning up some of the redundancy of one set of cleanups with a macro. So, its time to re-patch with some additional cleanups for good measure. More on this patch later today.
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
Full
Abbreviated
Hidden
Loading... please wait.
--Larry Wall in <10226@jpl-devvax.JPL.NASA.GOV>
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.
Refactoring time... (Score:1)
It looks like someone applied that patch. My next step was going to be to refactor and cleanup after the fact, so, I'll just add this to the list as well.
Re: (Score:1)
I stay up late to apply your patches. It's worth it.
Macros and perl (Score:2)
Re: (Score:1)
Oh certainly, I don't plan on making Parrot more obfuscated than it already is ;-).
The macros come in with trying to make Parrots guts easier to understand.
malloc()is a typical sore spot. By definition, it returnsvoid *pointers. That's fine, but it causes severe problems in comprehension when people have a function which happens to callmalloc()return thevoid *without casting it to something else. My thoughts are on performing this cleanup by use of macros to avoid the parenthesis hell that usual