On 2012-07-19, David A. Wheeler wrote: > > I'm rather curious what Alan Manuel Gloria thinks about my "\\" symbol idea, > > which I believe eliminates the problems from slashification.
Alan Manuel Gloria replied: > I still prefer \, but I won't object to \\. > I also won't object to ~ or !. > > So if I were to rank preferences: > \ > \\ > ~ or ! > Other symbols, NO. We may have a winner! I *strongly* object to a bare "\" as the split symbol, because it screws up on any system with slashification (all Common Lisps, some Scheme implementations, and probably many others). Other than that, though, I don't care much. I think almkglor's discussion of the visual advantages of various symbols a really interesting analysis, and it suggests that something using backslashes has advantages. So, since almkglor can live with \\, and I *strongly* object to \, I think the best between the two of is \\ for SPLIT, presuming that we implement SPLIT. Based on previous discussions, I think we should implement SPLIT at least. I'm not convinced of the advantages of ENLIST, and almglor was willing to live without it. So here's how I see the discussion shaking up: * SPLIT semantics, using \\ as the SPLIT symbol. It's like GROUP when the first symbol of the line, it represents a null-length function name at that indentation level. Otherwise, it splits datums; the next datum restarts at the current indentation level. * "." lives on as indentation, but only when followed by space or tab. --- 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
