BuffaloFeeds » Comments for Josh the Outspoken » Comment on A syntactic dilemma (and an intro to Gazelle’s ambiguity resolution) by Dennis

Feeds

105363 items (97572 unread) in 19 feeds

• 2 Star (84 unread)
• John Carrino (12 unread)
• Comments for Josh the Outspoken (296 unread)
• Josh (34 unread)
• Planet Matt (595 unread)

• MAKE Magazine (20292 unread)
• Instructables.com (35006 unread)
• Hack A Day (5017 unread)
• Toolmonger (7776 unread)

• Exploration Through Example
• Paul Graham: Unofficial RSS Feed (113 unread)
• Stevey's Blog Rants (34 unread)
• Joel on Software (207 unread)
• Gibson Blog (239 unread)
• Adventures in Bloggery (123 unread)

• Slashdot (25203 unread)
• Economist.com Global Agenda (1412 unread)
• Ruby Inside (922 unread)

• Templar, Arizona (207 unread)

Comments for Josh the Outspoken

• 

  Comment on A syntactic dilemma (and an intro to Gazelle’s ambiguity resolution) by Dennis

  Posted: August 23rd, 2008, 12:54pm MDT by Dennis

  This might be a lame idea, but could you use // for the prioritized choice? I can not think of a reason why you would want to use // when defining a regular expression. Everybody knows that two is better then one.

  Also, | is OR sometimes and || is OR other times, so why not / sometimes and // other times….

TOP Gregarius 0.5.4 Tentatively valid XHTML1.0, CSS2.0 Last update: Sun Apr 15 21:49:26 2012