Re: [racket] Question about string conversion

2013-07-18 Thread m0nastic
From: Greg Hendershott Sent: Thursday, July 18, 2013 10:01 AM To: m0nas...@tengulabs.com Cc: users@racket-lang.org Subject: Re: [racket] Question about string conversion To add to what Carl and Robby said: On Thu, Jul 18, 2013 at 2:29 AM,   wrote: > (although truth

Re: [racket] Question about string conversion

2013-07-18 Thread Nick Shelley
I recently came across a site that made coming up with regular expressions much, much easier for me: http://www.debuggex.com/ Hopefully that will help with your "regex hell" problem. On Thursday, July 18, 2013, Greg Hendershott wrote: > To add to what Carl and Robby said: > > On Thu, Jul 18, 201

Re: [racket] Question about string conversion

2013-07-18 Thread Greg Hendershott
To add to what Carl and Robby said: On Thu, Jul 18, 2013 at 2:29 AM, wrote: > (although truth be told, mail headers are surprisingly nonstandard even > within a single message) That's where net/head could definitely help. (Especially for SMTP headers, which tend to be more "interesting" than ty

Re: [racket] Question about string conversion

2013-07-18 Thread Robby Findler
Also, check out the net/head library: http://docs.racket-lang.org/net/head.html?q=header%20parse&q=header Robby On Thu, Jul 18, 2013 at 2:25 AM, Carl Eastlund wrote: > Chris, > > The regexp-match* function has a rather complex input/output > specification, because it is doing a lot of things

Re: [racket] Question about string conversion

2013-07-18 Thread Carl Eastlund
Chris, The regexp-match* function has a rather complex input/output specification, because it is doing a lot of things at once. If you only want the first match of a regular expression, you might want to consider regexp-match instead (no *); its specification is slightly simpler, though still a l

[racket] Question about string conversion

2013-07-17 Thread m0nastic
Hi, I'm super new to Racket, but had what I hope isn't too embarrassingly easy of a question. I'm writing a program that parses SMTP headers in order to automate some business-y workflow. I managed to put together a series of "regexp-match*"s to parse out the specific identifiers I was looking for