On Jan 15, 2008, at 8:14 AM, Chris AtLee wrote:
I just had a chance to look at the Routes 2 spec, and this was my
first thought as well. Having route names as attributes on the
RouteMap object will be very confusing since the methods used to
manipulate the RouteMap will be indistinguishable
Hi,
I just want to add some sugar to the discussion:
Instead of
m.connect(foobar, vars) it was proposed: m.foobar(vars...)
One option could be:
m.routes.foobar(vars...)
= adding a central var under which all named routes are accessible as
attributes
Alternativly:
m[foobar] =