[WebDNA] [regex]

This WebDNA talk-list message is from

2015


It keeps the original formatting.
numero = 111950
interpreted = N
texte = > I think the best way to go forward with our version of [grep] > is to start a wiki (or interactive docs) where users can create > the grep docs over time. I disagree completely. Personally I think the best way to go forward with "our version of [grep]" is to abandon it. YES, ABANDON IT !!! I'm not suggesting that it be removed from the engine (backward compatibility is still important here) ... only that no more effort be made by ANYONE to fix it, or document it, or change it in any way. Instead, WSC might better focus its limited resources on a new [regex] context that implements standard *nix grep. Then we will finally have a version all programmers worldwide can easily and correctly understand and use without issue. Just think about it for a minute: Standard *nix grep is prolifically documented on the web, which means "we don't need no frickin' wiki" if only we had a standard *nix version of grep in the language. So please, WSC, do us all a huge favor by adopting the common standard *nix grep as [regex] ... and then let "our version of grep" die a slow but welcome death. Regards, Kenneth Grome WebDNA Solutions http://www.webdnasolutions.com Web Database Systems and Linux Server Management On 01/16/2015 11:05 AM, Donovan Brooke wrote: > I think the only reason it is there is because there was a > universal open source C port (library) that someone did, and > it gave PC servers the power of grep. As of now, it is a *nix > based language and we do have access to the system grep (on > the OS) via [SHELL]. I think the best way to go forward with > our version of [grep] (which is quite useful) is to start a > wiki (or interactive docs) where users can create the grep docs > over time. It is really not that far off from the ideas of > GNU grep, and I personally know a lot of the quirks / > workarounds.. and I’m sure many of you do to. Over some time, > we could not only create community docs for it, but we could > improve it. Associated Messages, from the most recent to the oldest:

    
  1. Re: [WebDNA] [regex] (Kenneth Grome 2015)
  2. Re: [WebDNA] [regex] (christophe.billiottet@webdna.us 2015)
  3. [WebDNA] [regex] (Kenneth Grome 2015)
> I think the best way to go forward with our version of [grep] > is to start a wiki (or interactive docs) where users can create > the grep docs over time. I disagree completely. Personally I think the best way to go forward with "our version of [grep]" is to abandon it. YES, ABANDON IT !!! I'm not suggesting that it be removed from the engine (backward compatibility is still important here) ... only that no more effort be made by ANYONE to fix it, or document it, or change it in any way. Instead, WSC might better focus its limited resources on a new [regex] context that implements standard *nix grep. Then we will finally have a version all programmers worldwide can easily and correctly understand and use without issue. Just think about it for a minute: Standard *nix grep is prolifically documented on the web, which means "we don't need no frickin' wiki" if only we had a standard *nix version of grep in the language. So please, WSC, do us all a huge favor by adopting the common standard *nix grep as [regex] ... and then let "our version of grep" die a slow but welcome death. Regards, Kenneth Grome WebDNA Solutions http://www.webdnasolutions.com Web Database Systems and Linux Server Management On 01/16/2015 11:05 AM, Donovan Brooke wrote: > I think the only reason it is there is because there was a > universal open source C port (library) that someone did, and > it gave PC servers the power of grep. As of now, it is a *nix > based language and we do have access to the system grep (on > the OS) via [shell]. I think the best way to go forward with > our version of [grep] (which is quite useful) is to start a > wiki (or interactive docs) where users can create the grep docs > over time. It is really not that far off from the ideas of > GNU grep, and I personally know a lot of the quirks / > workarounds.. and I’m sure many of you do to. Over some time, > we could not only create community docs for it, but we could > improve it. Kenneth Grome

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:

Another question (1997) Database not found in Include (2002) [ShowNext] feature in 2.0 (1997) Error: Can't open order file. (2005) Database Path (1998) WebSite and *NO* Authentication Dialog Box!!? (1998) Using WebCat for product info requests (1997) Javascripts (1998) [WebDNA] Friday's.. WIP thread (2009) WebCat2 - Getting to the browser's username/password data (1997) Protect (1997) First postarg not taking in $Commands (1997) & in Lookups (1997) Need some assistance. (1999) Renaming textA (1998) Database of Tax Rates? (1997) Re:2nd WebCatalog2 Feature Request (1996) RE: includes and cart numbers (1997) unable to launch acgi in WebCat (1997) Question... (2002)