OK. It turned out to be like this: App::import('Core', 'Behavior') does
in fact import classes ModelBehavior and BehaviorCollection. But on
subsequent calls App::import() still checks if the 'Behavior' class is
defined.
So I suppose what really should be made is: rename behavior.php to
model_behavior.php; change App::import('Core', 'Behavior') to
App::import('Core', 'ModelBehavior') in model.php and configure.php line
1037.
It works for me and I think I've got noticeable performance gain; but
I'm not sure that a consequence won't rise somewhere in the core code.
AD7six wrote:
>> What kind of pass-the-buck cop out logic is that...
If I got your slang right and you're really complaining about me not
reporting the ticket myself, I must tell that I'm not sure which tickets
must be supplemented with tests and which ones just can't be tested. If
I write a test that ensures that App::import('Core', 'Behavior') imports
classes ModelBehavior and BehaviorCollection, will that not be a break
of test isolation? The same with model.php, I can't be sure that another
test doesn't already included model.php.
I'll report the ticket, the rest is out of my reach for now.
--
kAtremer
[EMAIL PROTECTED]
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"CakePHP" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/cake-php?hl=en
-~----------~----~----~----~------~----~------~--~---
