Damn, I followed your advice and starting adding global's, instead of
modifying var to ::var.
However, after deleting all changes I made yesterday (silly me :@) and
adding several global's, I figured out that does not work.
The idea of the tip apparently is that the global and variable commands
will disappear. Global will not have any effect anymore. Where a
variable is stored can be seen completely from the variable name.
> but I'd like to suggest something.. instead of doing $::varname I think it
> would be best to use global varname; $varname ...and especially for namespace
> vars.. the reason
> imagine you have a namespace MSN { $::MSN::protocol_version } and now we add
> multi protocol and we want namespace ::protocols::MSN {
> $::protocols::MSN::protocol_version } ... well, if we have hundreds of vars
> everywhere, we'd
> need to replace each one.. with 'variable' we won't need to...
We should use relative names as much as possible. That way your above
remark is still valid. But as for the initialize_amsn, it really must
become ::initialize_amsn, there's no other way.
When using relative names, we can add "variable varname" so that it
works right now as well, and I can already commit those.
JeeBe.
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Amsn-devel mailing list
Amsn-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/amsn-devel
