Actually, foo-bar works perfectly fine with :invert so everything is backward compatible. Parenscript doesn't know anything about readtables, just when a symbol name is mixed-case.
The one case where this is ambiguous is something like Foo-bar, which right now gets translated as fooBar.
Vladimir
On Wed, Feb 15, 2012 at 3:07 AM, Miron Brezuleanu mbrezu@gmail.com wrote:
On Wed, Feb 15, 2012 at 12:27 AM, Vladimir Sedach vsedach@gmail.com wrote:
Yes, it really should, but I want to encourage people to change their readtables to invert.
Well, someone who knows about Parenscript symbol name rendering to JavaScript and READTABLE-CASE will know what this is about. Someone new to either Parenscript or Common Lisp will have some trouble figuring things out or will report a bug. If you don't want to change the example to work with :UPCASE, maybe putting a note about READTABLE-CASE in the 'new' section would be useful? (converting the whole manual to one style or another and mentioning the assumed READTABLE-CASE in the 'Symbol Conversion' section is better, but also a great deal of work).
For me personally, changing READTABLE-CASE to :INVERT is not a good choice. I like 'shoe-size' better than 'shoeSize' - it looks more readable to me. On the other hand, there's some pain when writing things like 'JSON.stringify' :-)
Maybe Parenscript should include a (not automatically installed) reader macro that temporarily switches READTABLE-CASE to :INVERT for the next symbol? (again, for me personally, that would be best: having both 'shoe-size' and an easy way to enter 'JSON.stringify').
-- Miron Brezuleanu
parenscript-devel mailing list parenscript-devel@common-lisp.net http://lists.common-lisp.net/cgi-bin/mailman/listinfo/parenscript-devel