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.

use Perl

All the Perl that's Practical to Extract and Report

[Perl 6 Microgrant] C++ Cleanup Adjustments More | Login | Reply

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.

Without JavaScript enabled, you might want to use the classic discussion system instead. If you login, you can remember this preference.

Refactoring time... (Score:1)

by speters (1787)

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)
  
  by chromatic (983)
  
  I stay up late to apply your patches. It's worth it.
Macros and perl (Score:2)

by drhyde (1683)

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!
- Re: (Score:1)
  
  by speters (1787)
  
  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

Get More Comments

Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.