On Jan 28, 2011, at 10:40 AM, villas wrote: > >> The downside is that we lose the capability to have trailing args that are >> empty strings. > > Hi Jonathan, > My point is that it's only a *downside* for those that want 'trailing > args that are empty strings'. > Who is it that wants them??
We don't know. The problem with args is that they can be used for pretty much anything, and it's entirely application-dependent. So if they're being used for something where elements can be empty, you'll get empty trailing args. Just because *my* application has no use for them doesn't mean that someone else's might not. > If we explicitly want to indicate empty args we can insert something > explicit (of our own choice) to create them, eg /url////~ > Otherwise strip them in the interests of cleaner, shorter args. > 2 cts :) I don't think that they'll be any cleaner or shorter either way. The only way you'll get trailing slashes (if we end up supporting them) is by asking for a URL with empty trailing args. If you don't want trailing slashes, then don't add empty args. That is, args=['arg1'] will generate a URL of .../arg1 regardless of which choice we make here.
