On Thu, Oct 9, 2008 at 2:03 PM, Paul Barry <[EMAIL PROTECTED]> wrote: > > What about having #"pattern" work like is does now, and then having #/ > pattern/ work similarly to Ruby, Python, Perl, etc. regular expression > in that they not require double escaping of characters like '\'? So > in other words:
I would vote against any new syntax that doesn't allow for a user-chosen delimiter. If we introduce something new, it should solve the problem more completely than that. > The advantage to this is that it is backwards compatible. That's true and good, and if Rich is open to it, I think #r/foo/ or #~/foo/ or something would be a great choice, allowing for / or " or perhaps even () for delimiting the regex. > I don't think the arbitrary delimiter is as necessary as not having to include > extra escaping characters because it is a string. I actually prefer " over / as the only allowed delimiter. Matching file paths with / as the delimiter is not uncommon, and rather painful: #/\/usr\/lib\/*.so/ The contexts where " have to be quoted often don't seem quite as bad: #"<img src=\"file://foo/bar\">" --Chouser --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/clojure?hl=en -~----------~----~----~----~------~----~------~--~---
