> I don't see a reason why a feature shouldSome possible reasons:
>not have more than one name.
- minimalism: one way to do one thing is better than 56
(readability, concise documentation)
- inheritance: use of synonyms requires a descendant
redefining synonyms to know more about the parent
than otherwise (plus hard to find bugs if you redefine
only one side).
- portability: implementers can introduce portability
issues (eg two slightly different versions under
the two names that behave differently when something
else is redefined)
Franck Arnaud ~ email: franck@...