Quoting Jan Schneider <
jan@...>:
>>> I agree about framework not really making sense, but if the
>>> package is Core, shouldn't the classes be named Horde_Core_*?
>>
>> IMHO, no. As for Horde:: - we have app-specific "master" utility
>> libraries called IMP::, Turba::, etc. that naming it Horde_Core::
>> doesn't make sense. And I think at this point moving from
>> something like Registry:: -> Horde_Core_Registry:: is too much
>> overkill.
>>
>> The package that contains the core files needs to be named
>> *something* - I don't think we have to incorporate that name in the
>> class names robotically.
>
> Despite of what I wrote earlier, I think I agree with Michael here.
I don't have strong feelings on this issue, so if someone wants to do
something with the naming, there is no objection here.
michael
--
___________________________________
Michael Slusarz [
slusarz@...]
--
Horde developers mailing list - Join the hunt:
http://horde.org/bounties/Frequently Asked Questions:
http://horde.org/faq/To unsubscribe, mail:
dev-unsubscribe@...
