Re: [Scm-discuss] building scm

[Philipp Klaus Krause]

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

Am 23.10.2010 22:57, schrieb Aubrey Jaffer:
>  | Date: Sat, 23 Oct 2010 14:03:46 +0200
>  | From: Philipp Klaus Krause <address@hidden>
>  | 
>  | Am 19.10.2010 02:40, schrieb Aubrey Jaffer:
>  | > We could modify "hobbit.scm" so that all C identifiers have
>  | > numbered names, eg. hv_932252.  This has the disadvantage of
>  | > making the generated C code much harder to read and debug.  A
>  | > compromise would be to use numbered names for only the non-ASCII
>  | > identifiers.
>  | 
>  | How about punycode? It has been designed to allow non-ascii
>  | characters in URLs, while still keeping them easy to read (at least
>  | up to the last ascii character from the beginning of the word).
> 
> Punycode can introduce a hyphen ("-") and can output a string with a
> leading digit (see the Hebrew and Korean examples in
> <http://tools.ietf.org/html/rfc3492>), both of which are not legal in
> C identifiers.  Are these the only pitfalls?

AFAIK, yes. However I only consider the hyphen to be a real pitfall: To
ease the integration of Scheme and C code I would suggest to use a
prefix for all hobbit-generated identifiers to reduce the risk of name
clashes. Thus would the problem of leading digits go away automatically.

Philipp
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkzEBMEACgkQbtUV+xsoLprGqQCgoV/jD2zoT+otxxd92lLK5ZPS
S8IAoJhj9ZkblRlrXDSbdXevtlh2CsuS
=UpxF
-----END PGP SIGNATURE-----