On 26 Oct 2009, at 09:38, Simon Thulbourn wrote:
> I'd have to agree with the other posts in this thread, that it's up
> to the developer to to ensure that he or she is entering the correct
> case/name into the build script. This stands for both of your points.
This surprises me. As:
- It leads to inconsistent behaviour between OS X and Linux. For the
model "Records" getModel('Records') and getModel('records') both work
on OS X but only getModel('Records') on Linux. It took me a while to
figure this one out when moving a project.
- The action-create script tests for incorrect spelling, but not for
incorrect capitalisation (on OS X). I have on a number of occasions
mis-spelt a module name when quickly creating an action, and the
script ended with an error and so I could quickly re-run with the
correct spelling. I have also run it using the incorrect
capitalisation, but I only figured this out later at runtime when PHP
failed.
Can I ask why it should be left to the developer? I feel I must be
missing something...
Just to be clear as well: by "incorrect capitalisation" I don't mean
without a starting capital letter. I mean something that is different
to what the existing file/folder/class name specifies. I agree that
forcing a specific capitalisation on the developer is something to
avoid.
Michal.
_______________________________________________
users mailing list
[email protected]
http://lists.agavi.org/mailman/listinfo/users
