On Dec 22, 2010, at 14:19, Larry E. Masters wrote: > Why do you think this is wrong in 2.0?
In CakePHP 1.3.x the __() function echoes the message out by default. If you want it to return the output instead of echoing, you pass true as the second parameter. This struck me as a strange way for the function to behave; it is not how the standard PHP and C _() function behaves. In the CakePHP 2.0 branch, __() has been changed so that it now always returns the output, just as the standard _() function does. It no longer has the built-in capability to echo anything out. This means you always have to do something with the result, such as echo it yourself if that's what you want. And it is, in the line in question. Further, in the CakePHP 2.0 branch, the second parameter of __() has been repurposed; __() now has a built-in sprintf feature, so any additional parameters you pass to __() get replaced into the placeholders in the message string. There are no placeholders in the string given is this line (at least, there won't be, after the template has been processed by bake), so there should not be a second parameter to the __() invocation. On Dec 22, 2010, at 14:23, Larry E. Masters wrote: > And 2.0 is not released... I am of course aware that 2.0 is not released. But when it is released, I would like it to be released with as few bugs as possible, which is why I am trying to report what I believe is a bug so that it can be resolved before release. If I am incorrect about my interpretation and this is not a bug, please let me know. Check out the new CakePHP Questions site http://cakeqs.org and help others with their CakePHP related questions. 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
