Sebastian Riedel wrote:
> Tony Bowden:
>>The problem is that moniker is giving the wrong
>>answer because Loader is setting up the class name wrongly.
>
> If Loader's so wrong, how else should it handle non word characters in
> table names?
>
> Btw. i would really hate classes with underscores, like "Data::Foo_Bar"
> for a table named "foo_bar"...
I think this is the crux of one issue with Loader/moniker. Perl style
says that names generally should have underscores as opposed to
capitalization (cf prog. perl p605) but goes on to say that modules
'sometimes' are an exception and should use capitalization and
'probably' omit underscores. The whole issue is pretty religious anyway
for many people and this ambiguous guidance doesn't help.
My personal view is that I don't care about naming conventions in code
but I would prefer that the Maypole and Class::DBI communities in
particular could decide on a particular convention then document it and
implement it consistently.
I believe at the moment the status quo implementation is capitalized
with no underscores but that isn't explicitly recorded and more
importantly it bleeds through from class names into other things.
Maypole is worst here because it conflates names generated for use in
code with strings generated for display to users (which is the other
Loader/moniker issue).
Chers, Dave
-- No virus found in this outgoing message. Checked by AVG Anti-Virus. Version: 7.0.298 / Virus Database: 265.6.5 - Release Date: 26/12/04_______________________________________________ maypole mailing list maypole at lists.netthink.co.uk http://lists.netthink.co.uk/listinfo/maypole
This archive was generated by hypermail 2.1.3 : Thu Feb 24 2005 - 22:25:57 GMT