I said (about my own error): > > And we have a new kind of error: If you use "!" indents, and later > > split a line, this won't work: > > ! hello( ... > > ! .... > > ! ....) > > Because the "!" on the middle and last line are *NOT* indent chars. > > > > I'm really striving to make the notation as resistant to accidents as I > > can, but there are already so many constraints that they will creep in. > > Hopefully not too many.
Alan Manuel Gloria: > IMO we should really remove ! in this case - it loses the consistency > of the indentation to have some lines break the rule. > > Will think how best to handle this... need to pass in even more stufff > to basic readers!!!!!! Hmm. I certainly want to AVOID complexity in implementation or in their interface, where we can. Passing in even more stuff to basic readers sounds like a way to create just *DIFFERENT* ways to make mistakes, and might cause more problems than it solves. A reader may not know if it's at the beginning of a line or not, but when using the sweet-reader it more or less has to be anyway. So if we wanted to do anything at all, one approach might be to say that, if a neoteric-read or curly-read see an end of line, they would just consume that and any sweet-reader indentation as well. Since we're implementing this as a stack, we even could say that only occurs if they're called by a sweet-reader. I have to admit, it's not at all clear to me that this would be a good idea. All notations have some gotchas; sometimes the best thing to do is to just teach people what they are, so that they are prepared for them. Since we're the first users of this notations, it's unsurprising if we have *some* problem. I really like having a non-whitespace indent; it's unusual, but in this application, it seems to be helpful. Having to NOT insert it there doesn't bother me, it hints to the reader that something unusual is going on. --- David A. Wheeler ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Readable-discuss mailing list Readable-discuss@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/readable-discuss
