1
edit
Update:Archive/2.0/Developers/Best Practices: Difference between revisions
Jump to navigation
Jump to search
Update:Archive/2.0/Developers/Best Practices (view source)
Revision as of 22:13, 16 April 2005
, 16 April 2005why not umo_?
(→Do) |
(why not umo_?) |
||
| Line 54: | Line 54: | ||
:Personally, if you want to avoid namespace conflicts, then you should be writing things as classes; so <tt>mozupd_addRating()</tt> becomes <tt>$rating = new Rating(); $rating->addRating();</tt>. I would tend to agree on "internal" methods being called <tt>_methodName</tt> but I think prefixing everything with mozupd_ etc. is going to get extremely annoying very quickly. --[[User:Csogilvie|Csogilvie]] 10:55, 22 Jan 2005 (PST) | :Personally, if you want to avoid namespace conflicts, then you should be writing things as classes; so <tt>mozupd_addRating()</tt> becomes <tt>$rating = new Rating(); $rating->addRating();</tt>. I would tend to agree on "internal" methods being called <tt>_methodName</tt> but I think prefixing everything with mozupd_ etc. is going to get extremely annoying very quickly. --[[User:Csogilvie|Csogilvie]] 10:55, 22 Jan 2005 (PST) | ||
Why not use "umo_" instead? It's much more intuitive to use. | |||
--[[User:Topal|Topal]] 15:13, 16 Apr 2005 (PDT) | |||