The best way to store arrays as text file?

[Stephen Barncard]

And then there is the NULL character - Ascii 0.

also if you know the data is text - URLEncoding and Decoding will 
make almost any,  especially non printable, char usable as a 
delimiter when used outside the encoded text.



  keyword    {TAB}    %3Cp%3E%3Cfont+size%[-URLENCODED 
TEXT-]3D%2219%22+color% {TAB}

{} =  invisible char

of course only useable if it's in and out within rev. REPEAT FOR EACH 
can make this data into an array in a flash.

One can always URLdecode all text as it renders plain text as plain 
text. Web browsers do this.



>David said:
>>>
>In general no delimiter is completely safe - safest would be XML is my guess
>- all though I was wandering about JSON as it is simpler.
><<
>
>I'm with Richard on this. The ASCII character set provides the 
>following delimiters:
>
>(communication controls)
>SOH = start of heading
>STX = start of text
>ETX = end of text
>
>and
>
>(informational separators)
>FS = file separator
>GS = group separator
>RS = record separator
>US = unit separator
>
>See the RFC for ASCII (from 1969):
>http://rfc.net/rfc20.html
>
>In fact, one could argue that these character codes are safer than 
>the ">" and "<" of XML, as the former carry no textual meaning at 
>all.
>
>When I had to provide structured data before, I used combinations of 
>these rather than use XML (I was dynamically updating keyword lists 
>in a web page, so I wanted to keep the transmitted data as small as 
>possible).
>
>Bernard

-- 


stephen barncard
s a n  f r a n c i s c o
- - -  - - - - - - - - -