Re: grep is really pathetic sometimes
This WebDNA talk-list message is from 2003
It keeps the original formatting.
numero = 51318
interpreted = N
texte = Hi John, I tried that same code: >> code: [Text show=T]SKU=TROUTPRINT.JPG[/Text]
[grep search=^([A-Z0-9][0-9A-Z])([0-9A-Z][0-9A-Z][0-9A-Z])&replace=\1/\2/][getchar s start=1&end=5][SKU][/getchars][/grep] >> output: TROUTPRINT.JPG TR/OUT/ Raj ----- Original Message ----- From: "John Peacock"
To: "WebDNA Talk" Sent: Wednesday, June 25, 2003 2:10 AM Subject: RFE: grep is really pathetic sometimes > > I love using regular expressions to process my text (which is why I spend most > of my time using Perl these days). However, one of my other developers came to > me to ask why a particular grep was working the way it was. > > The code is as follows: > > [grep > search=^([A-Z0-9][0-9A-Z])([0-9A-Z][0-9A-Z][0-9A-Z])&replace=\1/\2/][getchar s > start=1&end=5][SKU][/getchars][/grep] > > That *should* match the first two characters (as \1) and the next three (as \2). > It always seemed to work when we were only looking at numbers, but we had to > extend it to work with characters as well as and it suddenly started matching > twice for one item. > > For SKU=TROUTPRINT.JPG, we expected it to return "TR/OUT/", but it would return > "TR/OUT/PR/INT" instead. It turns out that [grep] doesn't understand the > beginning of line (BOL) anchor "^" character. Consequently, the pattern was > matching twice (because this item had a longer SKU than the other items). This > is very annoying and vastly reduces the usabililty of [grep] for me. > > Why couldn't WebCat provide a real regex engine like Perl Compatible Regular > Expressions: > > http://www.pcre.org/ > > instead of whatever hodgepodge of code it currently has? At the very least, > WebCat should have thrown some sort of an error for the "^" which it doesn't > understand. > > > John > > -- > John Peacock > Director of Information Research and Technology > Rowman & Littlefield Publishing Group > 4501 Forbes Boulevard > Suite H > Lanham, MD 20706 > 301-459-3366 x.5010 > fax 301-429-5748 > > > ------------------------------------------------------------- > This message is sent to you because you are subscribed to > the mailing list . > To unsubscribe, E-mail to: > To switch to the DIGEST mode, E-mail to > Web Archive of this list is at: http://webdna.smithmicro.com/ ------------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://webdna.smithmicro.com/
Associated Messages, from the most recent to the oldest:
Hi John, I tried that same code: >> code: [Text show=T]SKU=TROUTPRINT.JPG[/Text]
[grep search=^([A-Z0-9][0-9A-Z])([0-9A-Z][0-9A-Z][0-9A-Z])&replace=\1/\2/][getchar s start=1&end=5][SKU][/getchars][/grep] >> output: TROUTPRINT.JPG TR/OUT/ Raj ----- Original Message ----- From: "John Peacock" To: "WebDNA Talk" Sent: Wednesday, June 25, 2003 2:10 AM Subject: RFE: grep is really pathetic sometimes > > I love using regular expressions to process my text (which is why I spend most > of my time using Perl these days). However, one of my other developers came to > me to ask why a particular grep was working the way it was. > > The code is as follows: > > [grep > search=^([A-Z0-9][0-9A-Z])([0-9A-Z][0-9A-Z][0-9A-Z])&replace=\1/\2/][getchar s > start=1&end=5][SKU][/getchars][/grep] > > That *should* match the first two characters (as \1) and the next three (as \2). > It always seemed to work when we were only looking at numbers, but we had to > extend it to work with characters as well as and it suddenly started matching > twice for one item. > > For SKU=TROUTPRINT.JPG, we expected it to return "TR/OUT/", but it would return > "TR/OUT/PR/INT" instead. It turns out that [grep] doesn't understand the > beginning of line (BOL) anchor "^" character. Consequently, the pattern was > matching twice (because this item had a longer SKU than the other items). This > is very annoying and vastly reduces the usabililty of [grep] for me. > > Why couldn't WebCat provide a real regex engine like Perl Compatible Regular > Expressions: > > http://www.pcre.org/ > > instead of whatever hodgepodge of code it currently has? At the very least, > WebCat should have thrown some sort of an error for the "^" which it doesn't > understand. > > > John > > -- > John Peacock > Director of Information Research and Technology > Rowman & Littlefield Publishing Group > 4501 Forbes Boulevard > Suite H > Lanham, MD 20706 > 301-459-3366 x.5010 > fax 301-429-5748 > > > ------------------------------------------------------------- > This message is sent to you because you are subscribed to > the mailing list . > To unsubscribe, E-mail to: > To switch to the DIGEST mode, E-mail to > Web Archive of this list is at: http://webdna.smithmicro.com/ ------------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://webdna.smithmicro.com/
"Rajeev Kumar"
DOWNLOAD WEBDNA NOW!
Top Articles:
Talk List
The WebDNA community talk-list is the best place to get some help: several hundred extremely proficient programmers with an excellent knowledge of WebDNA and an excellent spirit will deliver all the tips and tricks you can imagine...
Related Readings:
[WebDNA] Upgrade 4.5.1 to 6.0a (2009)
WebCat2 several catalogs? (1997)
[INCLUDE] Limitations (1998)
Lost Installer (2000)
Websited Development (1999)
Associative lookup style? + bit more (1997)
Showing unopened cart (1997)
Re[2]: 2nd WebCatalog2 Feature Request (1996)
$purchase WITHOUT creditcar (1997)
[foundItems] context problem (2000)
show all problem (1997)
Online reference (1997)
listfiles-looking for slick solution (1997)
[lineitems] (2000)
[WebDNA] More YouTube Comments (2010)
Add a field to the error log? (1997)
Thanks ! (1997)
frames & carts (1997)
Forcing a NEWCART (1997)
Re: (1997)