Per Einar Ellefsen wrote:
> Well, this one is exported by Apache::Constants, so if you don't want to do
> $FORBIDDEN = FORBIDDEN;
> somewhere at the top of your code, you're bound to continue using
> constants, right?
That's still safer. I used the constants pragma on a big project and I
saw people get bitten by $hash{CONSTANT} and "string interp CONSTANT" as
well as the aforementioned CONSTANT => value problem. It's just asking
for trouble, in my opinion.
Can anyone tell us if the Apache::Constants all just standard HTTP
response codes, or are some of them actually Apache-specific?
- Perrin
