Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

use Perl Log In

Log In

[ Create a new account ]

speters (1787)

speters
  (email not shown publicly)
http://www.fisharerojo.org/
AOL IM: fisharerojo (Add Buddy, Send Message)

mmm...Perl

Journal of speters (1787)

Friday April 27, 2007
07:56 AM

[Perl 6 Microgrant] C++ Cleanup Adjustments

[ #33122 ]

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
More | Login | Reply
Loading... please wait.
  • 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.

  • The perl5 source is a twisty impenetrable maze of macros. I know that macros can be jolly useful when used wisely, but do please be careful not to fall into the same trap!
    • 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 returns void * pointers. That's fine, but it causes severe problems in comprehension when people have a function which happens to call malloc() return the void * without casting it to something else. My thoughts are on performing this cleanup by use of macros to avoid the parenthesis hell that usual