|
|
Posted by Gary L. Burnore on 09/04/07 13:14
On Tue, 04 Sep 2007 03:11:38 -0700, Marijn
<marijn.huizendveld@gmail.com> wrote:
>On 4 sep, 10:02, Toby A Inkster <usenet200...@tobyinkster.co.uk>
>wrote:
>> By the way, you shouldn't name your functions with a double-underscore.
>> Functions that start with a double-underscore are reserved for future use
>> as "magic" functions (e.g. __construct, __call, __get, __autoload, etc).
>>
>
>I know it is for reserverd magic functions BUT this way i serarate
>public (no underscore) from (protected one underscore) from (private
>(two underscores)
>
>I really prefer a difference in my code for private and protected
>methods.
>
>Plus everybody with a bit of experience knows that ther is __call,
>__autoload, __desctruct ...etc.
So you think it's ok to mix YOUR functions with reserved functions
just so your functions look different?
how about pu_ pv_ and pr_ (or no for public, pv for private and pr
for protected).
Of course, it's your coding skills that'd be called into question if
someone who knew better looked at it so that's up to you.
--
gburnore at DataBasix dot Com
---------------------------------------------------------------------------
How you look depends on where you go.
---------------------------------------------------------------------------
Gary L. Burnore | ÝÛ³ºÝ³Þ³ºÝ³³Ýۺݳ޳ºÝ³Ý³Þ³ºÝ³ÝÝÛ³
| ÝÛ³ºÝ³Þ³ºÝ³³Ýۺݳ޳ºÝ³Ý³Þ³ºÝ³ÝÝÛ³
Official .sig, Accept no substitutes. | ÝÛ³ºÝ³Þ³ºÝ³³Ýۺݳ޳ºÝ³Ý³Þ³ºÝ³ÝÝÛ³
| ÝÛ 0 1 7 2 3 / Ý³Þ 3 7 4 9 3 0 Û³
Black Helicopter Repair Services, Ltd.| Official Proof of Purchase
===========================================================================
Navigation:
[Reply to this message]
|