Alan Manuel Gloria: > I considered proposing this before, but one of sweet's goals is to make it > easy to use classic s-expression code while using a sweet reader. > > Having the rule "everything added by sweet indentation processing is > disabled within ()" helps that tremendously. > > Not to say that this idea has been explicitly rejected already, though; it > hasn't been discussed. It really depends on a tradeoff: you lose some > amount of back-compatibility to gain expressibility.
I'd thought of this as well. Alan Manuel Gloria is exactly right - the problem is that you give up backwards compatibility if you do that. I think backwards compatibility is really important, so I've intentionally *not* done that. So I did do that intentionally, though I probably didn't document it so well. I want people to be able to quietly replace their readers... and have nothing break. That's not always possible, but it's pretty close. It can read *EVERY* guile 1.8 file without any problems, and in a Common Lisp sample code nearly all worked without problem. The ":" symbol would be especially problematic, because several Lisps (including typed Racket) use that as a type declaration operator. --- David A. Wheeler ------------------------------------------------------------------------------ Precog is a next-generation analytics platform capable of advanced analytics on semi-structured data. The platform includes APIs for building apps and a phenomenal toolset for data science. Developers can use our toolset for easy data analysis & visualization. Get a free account! http://www2.precog.com/precogplatform/slashdotnewsletter _______________________________________________ Readable-discuss mailing list Readable-discuss@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/readable-discuss
