Oh, I'm sure you're right, but the idea of a simple <put serialize
(tArray) into ...> that fits all occasions is attractive.
If I think of something I'll be sure to let you (and everyone) know :)
Best,
Mark
On 7 Jan 2009, at 20:41, Jim Ault wrote:
There are a few gotchas with the 'accommodate anything'. Apart
from issues
like unicode, there are those of intended use.
In the world of PHP, there are functions such as
htmlEntities() serialize()
addSlashes() --for storing in SQL databases
-- this adds escaping "\"
gzip()
base64() -- url-safe base64 string
line endings (unix, wn32, mac) CR CRLF LF
Looking at the PHP.NET web site should give you a better picture of
some of
the variations that cause most programmers to build their own
library for
serialization of arrays. It usually boils down to special uses and
needs as
opposed to crafting a general solution.
Let me know if you find a good system :-)
Jim Ault
Las Vegas
_______________________________________________
use-revolution mailing list
[email protected]
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution
