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:
#/<em>(.*?)<\/em>/
instead of:
#"<em>(.*?)<\\/em>"
The advantage to this is that it is backwards compatible. I don't
think the arbitrary delimiter is as necessary as not having to include
extra escaping characters because it is a string.
On Oct 9, 1:14 pm, "Stephen C. Gilardi" <[EMAIL PROTECTED]> wrote:
> On Oct 8, 2008, at 11:03 AM, Chouser wrote:
>
> > Of course if this change is unacceptable, these proposed rules could
> > be applied to a new dispatch macro. One option would be something
> > like #r/foo/ that would allow your choice of delimiters to further
> > reduce the need for back-slash quoting within the regex.
>
> I like both proposed changes: new escape rules for #" , and #r with
> arbitrary delimiters. Thanks for moving the issue along.
>
> Comparing the two, I think the arbitrary delimiter allowed by #r is
> very attractive. The only potential downside I see with that is that
> it requires a smarter "clojure mode" in an editor to know how to find
> the end in source code. (I use emacs, so I trust I'll be all set. I
> suspect "clojure mode" most other editors can be adapted to handle it.)
>
> With #r in place, I would be in favor of leaving #" as it is now, and
> possibly deprecating and removing it over time.
>
> --Steve
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Clojure" group.
To post to this group, send email to [email protected]
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
-~----------~----~----~----~------~----~------~--~---
