From: Steve Klabnik <steve@steveklabnik.com>
To: Rack Development <rack-devel@googlegroups.com>
Subject: Regexp warning with Cucumber
Date: Sun, 22 Aug 2010 13:33:27 -0700 (PDT) [thread overview]
Message-ID: <06f9371e-4a92-46c9-ba7a-9a284577190a@v8g2000yqe.googlegroups.com> (raw)
Hey everyone-
I tried to look around to see if this was posted anywhere, but I
couldn't find anything. I'm not 100% sure if this is a bug in Rack, or
the product of a few things working together...
Anyway, I'm starting a new project, Ruby 1.9.2, Rails 3, the whole
works. (oh, and Rack 1.2.1) So I get my standard Cucumber stuff on,
and I get a bunch of these:
/Users/steveklabnik/.rvm/gems/ruby-1.9.2-p0/gems/rack-1.2.1/lib/rack/
utils.rb:16: warning: regexp match /.../n against to UTF-8 string
This makes sense, as that's the proper warning... but is this a
problem with Rack, or a problem with something else up higher in the
stack? I'd imagine that it's higher up, as /n explicitly means that
you don't support multibye, right?
Thanks in advance for any guidance.
reply other threads:[~2010-08-22 22:28 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-list from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://groups.google.com/group/rack-devel
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=06f9371e-4a92-46c9-ba7a-9a284577190a@v8g2000yqe.googlegroups.com \
--to=rack-devel@googlegroups.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).