On November 29th 2011, Asumu Takikawa wrote:
> On 2011-11-29 15:43:27 -0500, Matthias Felleisen wrote:
> >
> > So, any volunteers?
> >
>
> I added this to the list of intro projects on GitHub, so if anyone
> wants to take this up, please put it up on GitHub/PLaneT and
> update the page:
> https://
Matthias Felleisen wrote at 11/29/2011 03:43 PM:
On Nov 29, 2011, at 3:41 PM, Norman Gray wrote:
What Neil said _and_ what Shivers said!
Implementing Shivers-style SREs would be a much bigger win than any alternate
pregexp syntax with differently funky backslash rules from everything else.
On 2011-11-29 15:43:27 -0500, Matthias Felleisen wrote:
>
> So, any volunteers?
>
I added this to the list of intro projects on GitHub, so if anyone
wants to take this up, please put it up on GitHub/PLaneT and
update the page:
https://github.com/plt/racket/wiki/Intro-Projects
Cheers,
Asumu
__
On Nov 29, 2011, at 3:41 PM, Norman Gray wrote:
>
> What Neil said _and_ what Shivers said!
>
> Implementing Shivers-style SREs would be a much bigger win than any alternate
> pregexp syntax with differently funky backslash rules from everything else.
So, any volunteers?
_
On 2011 Nov 29, at 18:14, Neil Van Dyke wrote:
> 1. Everyone should acknowledge the JWZ quote, "Some people, when
> confronted with a problem, think 'I know, I'll use regular expressions.'
> Now they have two problems." Regular expressions are Perl's hammer that
> makes most problems look lik
1. Everyone should acknowledge the JWZ quote, "Some people, when
confronted with a problem, think 'I know, I'll use regular expressions.'
Now they have two problems." Regular expressions are Perl's hammer that
makes most problems look like a nail.
2. Before someone spends too much time puttin
> I'm curious what others think so I'll try to find the irc
conversation.
http://racket-lang.org/irc-logs/2026.txt
http://racket-lang.org/irc-logs/2027.txt
http://racket-lang.org/irc-logs/2028.txt
Search for "regexp"
> But my first impression is that such a new #px reader syntax
> s
On Mon, Nov 28, 2011 at 12:02:46AM -0800, Pauan wrote:
> JavaScript you can saythis: /\\\d/ But before we can even consider
> such a syntax, we first need to add in theabove mentioned regexp
> syntaxes. Because otherwise #px/\n/ would compile into(pregexp "\\n")
> which would then throw an error,
On Mon, Nov 28, 2011 at 12:02:46AM -0800, Pauan wrote:
> Yes that is exactly it. The rationale is as ozzloy said: right now you
> needto use something like #px"\\d" to match the string "\\5".
> That's a lot ofbackslashes!
> In other languages that support regexps, there's usually a way of
> spe
Sorry for the confusion. Ideally most of the syntax described will
beavailable in both pregexp and regexp mode, but "\\X" and
"\\u{E0}"should probably be restricted to pregexp only.
> To add to my confusion, your original email mentioned #px"n", which>
> currently matches a backslash followed
i'll take a stab at clarifying.
there was some discussion on irc about being able to represent regexpes
using less escaping.
it was suggested that we could have something similar to perl, ruby,
javascript and other languages for specifying a regexp pattern, something
like #rx/pattern/
so for exampl
On Sat, Nov 26, 2011 at 10:35:57PM -0800, Pauan wrote:
> It was brought up that my explanation was confusing, and I agree it is.
> So I'll try again. The following should return #t:
...
> (regexp-match? "\\n" "\n")
I am confused about a number of things in your emails, so for simplicity
I'm
Sorry for the butchered e-mail, I was quite careful to send it in
plain textmode, so I don't know how that happened.
_
For list-related administrative tasks:
http://lists.racket-lang.org/listinfo/dev
It was brought up that my explanation was confusing, and I agree it is.
So I'll try again. The following should return #t:
(regexp-match? #px"\\u{E0}" "\u00E0")(regexp-match? "\\X"
"\u00E0")(regexp-match? "\\u00E0" "\u00E0")(regexp-match? "\\x00"
"\x00")(regexp-match? "\\n" "\n")(regex
Racket pregexp syntax is currently missing the following:
#px"X"-> a single Unicode grapheme
#px"u[a-fA-F0-9]{4}" -> hexidecimal Unicode escapes
#px"u\\{[a-fA-F0-9]{1,4}\\}" -> hexidecimal Unicode escapes
#px"x[a-fA-F0-9]{2}" -> \x escapes
15 matches
Mail list logo
