yup. You missed the whole point of my request(Which you seem to do alot). Why have bvars function the way was /set|/var does? If you changed the format of them, it would mess up backwards compatiblity, breaking a lot of scripts.
The -u switch is a good idea, if it was to be used with the suggested -p switch. The -l switch is unless, if what I suggested is implemented.
You listed 3 commands... what about the other 20 or so commands/identifiers that use binvars? They all going to need a -p switch too?
the switch would only be suitable for functions that create bvars, of which there are a limited number (in addition to what he mentioned i can only recall /sockread off the top of my head, and of course $hget()/$fread() which aren't commands though switches could still be implemented).
i'm afraid i can't rally behind this suggestion since, as argv mentioned, persistent bvars can already quite comfortably be coded with the use of a hash table. and if it were to be considered, we would also have to add a $var() counterpart for bvars to keep track of those that have been set as persistent, otherwise it's very possible to lose track of them all, some of which could be hogging large amounts of memory. should we choose to use a hash table to house our persistent bvars, this method of keeping track is already offered with $hget().
