OK, I'll summarize. First, we have a pool of syntax symbols. Let's not fix meanings to symbols for now:
~ \ . ! $ % ^ Then we have a bunch of concrete proposals: 1. almkglor: Don't use GROUP Don't use SPLICE Use SPLIT Use ENLIST Use 2 symbols from our pool of syntax symbols. Current proposal: \ = SPLIT, ~ = ENLIST 2. dwheeler: Don't use GROUP Don't use SPLICE Use SPLIT Don't use ENLIST Use 1 symbol from our pool of syntax symbols. Various: ! = SPLIT, ~ = SPLIT, \ = SPLIT (in order of preference?) 3. arne_bab: Use GROUP + GROUP-inline=dotted list Use SPLICE - SPLICE-at-beginning rule Don't use SPLIT Don't use ENLIST Use 2 symbols from our pool of syntax symbols. Current proposal: . = GROUP, \ = SPLICE Those positions/ideas look OK to consider? Are there more ideas? Sincerely, AmkG ------------------------------------------------------------------------------ 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
