Re: Re: Private Classes - Same or Separate Files?

[demerphq]

I agree with demerphq. Enforce restrictions through code, not organization.

Actually my point was that afaict in Perl enforcing such restrictions can only be done through code. But it was not that I think such a thing is a good idea.

Generally speaking I prefer that code doesnt restrict me in any ways that arent absolutely necessary. Just because someone cant think of a good reason why I would want to do X with their module doestn mean that I can think of one, and if I do im gunna be mighty unimpressed that they went out of their way to stop me, especially if there isnt a damn good reason why.

Yves / DeMerphq
--
When to use Prototypes?
Advanced Sorting - GRT - Guttman Rosler Transform