I used to worry about this sort of thing all the time. Really it would keep me awake at night. Then I ditched Windows, and switched to Unix. Fairly soon I stopped worrying. I'm not trying to start an OS holy war here - hell, I've no idea about what your favourite Desktop OS is (but I'm guessing Windows). But there is definately some sort of culture thing going on which I only became aware of when I switched.
With windows I suppose it can be best summed up as "maintain control" - and is the responsibility of the creator of the code. Whereas with Unix it's more like "best practice" - and is the responsibility of the user of the code.
I'm a fan of "best practice". It seems like it's less work when I'm hacking code. I also like the possibility of stepping outside the envelope if I wish - although I've learned that's usually not a good idea. But the main reason is that I don't need to write decent API documentation... read the code POD if you really want to know.
In reply to Re: OOPerl isn't that bad after all...
by xaphod
in thread OOPerl isn't that bad after all...
by yosefm
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |