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

"use constant" versus ReadOnly 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.

Constant versus ReadOnly (Score:1)

by Alias (5735)

I guess the big question is, why make it a constant? The big reason, so far as I can tell, is compile-time optimisation.

If you can define constants such that they will be compiled out, and in doing so make your code smaller, faster or simpler, then constants are a good thing.

use constant UNIX = ...;

eval UNIX ? 'END_UNIX' : 'END_OTHER';

etc
etc

And so now you have smaller faster unix-specific code paths...
- Re:Constant versus ReadOnly (Score:1)
  
  by Alias (5735) on 2005.08.31 10:30 (#42989) Homepage Journal
  
  Yuck, it killed my << chars :(
  
  Reply to This
  
  Parent
  - Re:Constant versus ReadOnly (Score:1)
    
    by Aristotle (5147)
    
    Use the ecode tags, Luke. :-)

Get More Comments

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