Greg McCarroll <[EMAIL PROTECTED]> writes:
> * Stephen Adkins ([EMAIL PROTECTED]) wrote:
>> Hi,
>>
>> I have grabbed the Slash style guide, removed/modified
>> the offending sections (exit/die, DESTROY, shift), and
>> created a proposed P5EE style guide.
>>
>> All comments are welcome. This is to make code consistency
>> possible, not to make our lives difficult.
>>
>
> I'm just going to play devils advocate here and I apologise for coming
> in a little late in this thread, however ...
[...]
> Now I agree that there needs to be a common style used in
> documentation and perhaps examples, so that the person learning how
> to write P5EE applications isn't confused by different styles while
> they learn, but they most likely will not go poking around in the
> middle of modules.
The 'internal' style of the module is probably not that important. But
it is important that we have consistency of things like method naming
for all the modules in whatever becomes P5EE since one of the points
of the whole exercise is to provide a single point of entry. Requiring
the end user to remember that the Foo package uses methodsLikeThis and
the that the Bar package uses methods_like_that seems a little counter
productive.
--
Piers
"It is a truth universally acknowledged that a language in
possession of a rich syntax must be in need of a rewrite."
-- Jane Austen?
