binarycloud-dev

[binarycloud-dev] Varnames / Zend 2.0

[Andreas A. <a.a...@th...>]

Hi Alex,

> on monday I'll be changing some important variable names,
[..]

Cool. Very good.

> Class Vars:
> varname
> I have not defined public/private class vars as php doesn't support them -
> is anyone in favor of making an artificial distinctoin similar to the
> private class names?

> like:
> Private Class Vars:
> _varname

Hmm, for the moment I don't see a reason. But with ZendEngine 2.0 it may be
supportet but then they would be specially marked i guess (private
$varname).
So a special naming convention isn't really neccessary.
But there should be an convention that classvars should only be accessed by
getVarname(), setVarname() methods. So this implies all that all varnames
without an accessor are private ones.

I had a talk with some guys from Zend at the german LinuxTag. ZE2.0 can be
implemented in a timeframe of several months as soon as all specs are final.

Other feautures planed with engine 2 are (* not yet final):

- multiple Inheritances*
- private member vars*
- static member vars
- exception handling (throw, try, catch)
- destructors
- new objects model (similar to java, variables contina object handles
instead of the objects)
- improved OO Apis (java objects, com)
- internationalization (multilingual error messages, unicode, non western
charsets)

Andi

Re: [binarycloud-dev] Varnames / Zend 2.0

[alex b. <en...@tu...>]

> Hmm, for the moment I don't see a reason. But with ZendEngine 2.0 it may
be
> supportet but then they would be specially marked i guess (private
> $varname).

well, looks like private vars will be supported, so a naming standard is
relevant.

> So a special naming convention isn't really neccessary.
> But there should be an convention that classvars should only be accessed
by
> getVarname(), setVarname() methods. So this implies all that all varnames
> without an accessor are private ones.

Hmm, I don't know if I agree with that.
What does it get you? i.e. why not, $ClassName->var ?
is there a reason to create a method name to match each public class var?

> - multiple Inheritances*
> - private member vars*
> - static member vars
> - exception handling (throw, try, catch)

no shit?

> - destructors
> - new objects model (similar to java, variables contina object handles
> instead of the objects)
> - improved OO Apis (java objects, com)
> - internationalization (multilingual error messages, unicode, non western
> charsets)

Yes, this last one is a good step. Everything is pretty ISO-8859-1 heavy, it
will be good to get some more mature charset support.

in any case, doesn't look like varnames are a big controversy :)

_a

RE: [binarycloud-dev] Varnames / Zend 2.0

[Andreas A. <a.a...@th...>]

Hi Alex,

> well, looks like private vars will be supported, so a naming standard is
> relevant.
Well for better readabiliy of course. But since private member vars are only
in the scope of the class they belong to (with engine 2.0) and every attempt
to access them will fail in an fatal error,  the idea is to define as much
variables as possible as private and use accessors to get/set them (maybe to
perform additional checks). So class variables exposed to the public are
reduced to a minium.

>> But there should be an convention that classvars should only be accessed
by
>> getVarname(), setVarname() methods. So this implies all that all varnames
>> without an accessor are private ones.
> Hmm, I don't know if I agree with that.
> What does it get you? i.e. why not, $ClassName->var ?
> is there a reason to create a method name to match each public class var?

Currently, not an objective reason ;-) Personally I feel better to access
variables with get/set routines from outside the class and with
$this->varname from the inside.
But maybe with Engine 2.0 this could be an issue. If you switch some vars to
private and you call them from outside the class with $ClassName->var this
will cause an fatal error.


>> - multiple Inheritances*
>> - private member vars*
>> - static member vars
>> - exception handling (throw, try, catch)

> no shit?
No shit, I have a Zend Engine 2.0 Overview flyer here. And Peter pointet out
the complete doc.


> in any case, doesn't look like varnames are a big controversy :)
No they are not. An they should not be.

It was just a thought on this topic.


Andi