Update:Archive/2.0/Developers/Best Practices: Difference between revisions

Update:Archive/2.0/Developers/Best Practices (view source)

No change in size , 22 January 2005

m

109

edits

Revision as of 21:29, 22 January 2005 (view source) Victory (talk \| contribs) m (→‎Proposals: typo) ← Older edit		Revision as of 21:31, 22 January 2005 (view source) Victory (talk \| contribs) m (→‎Proposals: typo) Newer edit →
Line 52:		Line 52:
	* We prefix all the functions in a module (include) that are not meant to be called from an including file (private utility functions) with '''_mozupd_'''? example '''_mozupd_dbTest()'''		* We prefix all the functions in a module (include) that are not meant to be called from an including file (private utility functions) with '''_mozupd_'''? example '''_mozupd_dbTest()'''

	:Personally, if you want to avoid ~~namesoace~~ 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)