[hashcash] Re: new format tweak coming...

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


Ben Laurie writes:
>Adam Back wrote:
>
>> On Sat, Mar 13, 2004 at 11:07:48AM -0500, Eric S. Johansson wrote:
>> 
>>>which means the only thing you really need to quote is the quote 
>>>character itself.  I was thinking that it might be possible to instead 
>>>use something like two types of quotes so that you could have quoted 
>>>strings within using the "other" form but then you could have both 
>>>quotes within a quoted strings if you were truly unlucky.
>> 
>> 
>> Yes I had come to think the same thing ... re "'" or '"' as the two
>> choices, and this is the "perl" thing, plus "\"'" and '"'\'
>> 
>> Cool.  So the usual case should be nice and clean for most
>> applications and there are no restrictions.  I was also thinking the
>> quotes should be optional.  So you only need to quote if you're trying
>> to protect =.
>
>This is icky - whatever format you use should, IMO, be regex friendly, 
>and trivial to parse. This is neither. I'd vote for URL encoding.

+1 on this idea -- me too.   URL encoding is much easier to 
parse than backslashing.

- --j.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
Comment: Exmh CVS

iD8DBQFAU2byQTcbUG5Y7woRArcjAKClDqpmtTT/KnXNVEy9mg12zySlFACdE566
Ujeuu8QcuMBn6t0+2RZIvC4=
=jBUY
-----END PGP SIGNATURE-----

Other related posts: