You should name it “Gazelle Forever”.
I kid 
Feeds
104649 items (96858 unread) in 19 feeds
Friends
(992 unread)
-
2 Star
(79 unread)
-
John Carrino
(12 unread)
-
Comments for Josh the Outspoken
(273 unread)
-
Josh (34 unread)
-
Planet Matt
(594 unread)
Build
(67517 unread)
-
MAKE Magazine
(20223 unread)
-
Instructables.com
(34656 unread)
-
Hack A Day
(4913 unread)
-
Toolmonger
(7725 unread)
Heads
(712 unread)
-
Exploration Through Example
-
Paul Graham: Unofficial RSS Feed (112 unread)
-
Stevey's Blog Rants
(33 unread)
-
Joel on Software (205 unread)
-
Gibson Blog
(239 unread)
-
Adventures in Bloggery (123 unread)
News
(27430 unread)
-
Slashdot (25098 unread)
-
Economist.com Global Agenda (1412 unread)
-
Ruby Inside
(920 unread)
fun
(207 unread)
-
Templar, Arizona
(207 unread)
Items by Dennis
Comments for Josh the Outspoken
-
Comment on Gazelle/upb status and plans (aka: On Releasing) by Dennis
Posted: December 31st, 2009, 9:03am MST by Dennis
-
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….