Comments on: Use a convention to structure your code http://cakebaker.42dh.com/2007/09/24/use-a-convention-to-structure-your-code/ baking cakes with CakePHP Tue, 31 Jan 2012 15:12:14 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: cakebaker http://cakebaker.42dh.com/2007/09/24/use-a-convention-to-structure-your-code/comment-page-1/#comment-15319 cakebaker Tue, 25 Sep 2007 16:57:15 +0000 http://cakebaker.42dh.com/2007/09/24/use-a-convention-to-structure-your-code/#comment-15319 @all: Thanks for your comments! @Brandon: I think one reason why many people stay with PHP 4 is that nobody wants to pay to migrate old stuff. @Mladen: Yeah, I am aware of this button, but unfortunately it mixes the variables and methods. And that's something I don't like ;-) @Henrik: Currently I use PDT 1.0 (http://www.eclipse.org/pdt) together with the Subclipse plug-in. @all: Thanks for your comments!

@Brandon: I think one reason why many people stay with PHP 4 is that nobody wants to pay to migrate old stuff.

@Mladen: Yeah, I am aware of this button, but unfortunately it mixes the variables and methods. And that’s something I don’t like ;-)

@Henrik: Currently I use PDT 1.0 (http://www.eclipse.org/pdt) together with the Subclipse plug-in.

]]> By: Henrik http://cakebaker.42dh.com/2007/09/24/use-a-convention-to-structure-your-code/comment-page-1/#comment-15229 Henrik Tue, 25 Sep 2007 07:23:42 +0000 http://cakebaker.42dh.com/2007/09/24/use-a-convention-to-structure-your-code/#comment-15229 What kind of eclipse setup do u use?? What kind of eclipse setup do u use??

]]> By: Mladen Mihajlovic http://cakebaker.42dh.com/2007/09/24/use-a-convention-to-structure-your-code/comment-page-1/#comment-15215 Mladen Mihajlovic Tue, 25 Sep 2007 05:46:32 +0000 http://cakebaker.42dh.com/2007/09/24/use-a-convention-to-structure-your-code/#comment-15215 You don't actually need to write the methods in alphabetical order for them to appear in that order in the outline view - there is a button there to sort them. You don’t actually need to write the methods in alphabetical order for them to appear in that order in the outline view – there is a button there to sort them.

]]> By: brandon http://cakebaker.42dh.com/2007/09/24/use-a-convention-to-structure-your-code/comment-page-1/#comment-15163 brandon Mon, 24 Sep 2007 23:45:40 +0000 http://cakebaker.42dh.com/2007/09/24/use-a-convention-to-structure-your-code/#comment-15163 IMO, I think variables and methods should always be sorted alphabetically. I think this based on how one "reads" source code. Grouping semantically equivalently methods make the source easier to read and especially easier to find. The access of those methods (public, private, protected, etc) is ancillary when reading source code and only matters when you are instantiating/extending the object. I think we could all benefit from some more defined standards when it comes to naming variables and methods. For instance, "_" and "__" should no longer be used outside PHP4, get/set methods, or even type hinting on variables names. On another note, why do you think so many people are still stuck on PHP4? In mid July the PHP Team announced they will no longer release new versions of 4.x at the end of this year and will stop ALL work on by Aug 2008. IMO, I think variables and methods should always be sorted alphabetically. I think this based on how one “reads” source code. Grouping semantically equivalently methods make the source easier to read and especially easier to find.

The access of those methods (public, private, protected, etc) is ancillary when reading source code and only matters when you are instantiating/extending the object.

I think we could all benefit from some more defined standards when it comes to naming variables and methods. For instance, “_” and “__” should no longer be used outside PHP4, get/set methods, or even type hinting on variables names.

On another note, why do you think so many people are still stuck on PHP4? In mid July the PHP Team announced they will no longer release new versions of 4.x at the end of this year and will stop ALL work on by Aug 2008.

]]> By: bkuhns http://cakebaker.42dh.com/2007/09/24/use-a-convention-to-structure-your-code/comment-page-1/#comment-15081 bkuhns Mon, 24 Sep 2007 15:49:05 +0000 http://cakebaker.42dh.com/2007/09/24/use-a-convention-to-structure-your-code/#comment-15081 This is pretty good advice, though I've been doing something similar for a while. With cakePHP, I write my controllers with all the public actions first (if there are "admin_" actions, they go after the normal ones), followed by public functions that may be called through requestAction. Finally, any private functions come at the very end. This really helps when jumping around controllers so you know where in the file to look for certain things. This is pretty good advice, though I’ve been doing something similar for a while. With cakePHP, I write my controllers with all the public actions first (if there are “admin_” actions, they go after the normal ones), followed by public functions that may be called through requestAction. Finally, any private functions come at the very end. This really helps when jumping around controllers so you know where in the file to look for certain things.

]]>