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

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


Hubert Chan writes:
> >>>>> "Justin" == Justin Mason <jm@xxxxxxxxxx> writes:
> 
> [...]
> 
> Adam> Yes I had come to think the same thing ... re "'" or '"' as the
> Adam> two choices, and this is the "perl" thing, plus "\"'" and '"'\'
> 
> Ben> This is icky - whatever format you use should, IMO, be regex
> Ben> friendly, and trivial to parse. This is neither. I'd vote for URL
> Ben> encoding.
> 
> Justin> +1 on this idea -- me too.  URL encoding is much easier to parse
> Justin> than backslashing.
> 
> My personal opinion is that since the stamps are primarily meant for
> computer consumption, to just use a single type of quotes, and
> backslash-escape the quotes, and backslash.  It takes a bit less
> processing, and is still fairly readable if anyone wants to look at the
> stamp.
> 
> I don't see backslashing any harder to parse than URL encoding -- just
> scan through the string from left to right, and every time you see a
> backslash, drop it and take the next character as a literal.
> 
> I also don't see backslashing, or having two types of quotes, as being
> regex unfriendly.

Oh good, you'd be happy to provide a regex that'll do the above
left-to-right scan to cope with

  foo:"bar \\\\\\\\\\\\\\\":baz":blargh

then.  as far as I know it can be done with perl re's, but
I don't know the recipe off-hand ;)

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

iD8DBQFAU58XQTcbUG5Y7woRAkqqAJ9ZsdkNEKoRvq3Wd7iDl7fDQcRH6ACdGVRa
/8sR9EZtdN1z8kUp7N0QfyM=
=+dNp
-----END PGP SIGNATURE-----

Other related posts: