| Deutsch English Français Italiano |
|
<vhl0m3$5mu9$1@dont-email.me> View for Bookmarking (what is this?) Look up another Usenet article |
Path: ...!weretis.net!feeder9.news.weretis.net!news.quux.org!eternal-september.org!feeder2.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail From: Janis Papanagnou <janis_papanagnou+ng@hotmail.com> Newsgroups: comp.unix.shell,comp.unix.programmer,comp.lang.misc Subject: Re: Command Languages Versus Programming Languages Date: Wed, 20 Nov 2024 16:53:38 +0100 Organization: A noiseless patient Spider Lines: 42 Message-ID: <vhl0m3$5mu9$1@dont-email.me> References: <uu54la$3su5b$6@dont-email.me> <87edbtz43p.fsf@tudado.org> <0d2cnVzOmbD6f4z7nZ2dnZfqnPudnZ2d@brightview.co.uk> <uusur7$2hm6p$1@dont-email.me> <vdf096$2c9hb$8@dont-email.me> <87a5fdj7f2.fsf@doppelsaurus.mobileactivedefense.com> <ve83q2$33dfe$1@dont-email.me> <vgsbrv$sko5$1@dont-email.me> <vgtslt$16754$1@dont-email.me> <86frnmmxp7.fsf@red.stonehenge.com> <vhk65t$o5i$1@dont-email.me> <vhki79$2pho$1@dont-email.me> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Injection-Date: Wed, 20 Nov 2024 16:53:40 +0100 (CET) Injection-Info: dont-email.me; posting-host="989e2dc1ebe8052ec6f7beceade503c1"; logging-data="187337"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX18OiBEg5Wjx+/Qc598MdGUg" User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0 Cancel-Lock: sha1:QEGDWPnuL1M6q+rkt6qWgXeH5OM= In-Reply-To: <vhki79$2pho$1@dont-email.me> X-Enigmail-Draft-Status: N1110 Bytes: 3139 On 20.11.2024 12:46, Ed Morton wrote: > > Definitely. The most relevant statement about regexps is this: > >> Some people, when confronted with a problem, think "I know, I'll use >> regular expressions." Now they have two problems. (Worth a scribbling on a WC wall.) > > Obviously regexps are very useful and commonplace but if you find you > have to use some online site or other tools to help you write/understand > one or just generally need more than a couple of minutes to > write/understand it then it's time to back off and figure out a better > way to write your code for the sake of whoever has to read it 6 months > later (and usually for robustness too as it's hard to be sure all rainy > day cases are handled correctly in a lengthy and/or complicated regexp). Regexps are nothing for newbies. The inherent fine thing with Regexps is that you can incrementally compose them[*].[**] It seems you haven't found a sensible way to work with them? (And I'm really astonished about that since I know you worked with Regexps for years if not decades.) In those cases where Regexps *are* the tool for a specific task - I don't expect you to use them where they are inappropriate?! - what would be the better solution[***] then? Janis [*] Like the corresponding FSMs. [**] And you can also decompose them if they are merged in a huge expression, too large for you to grasp it. (BTW, I'm doing such decompositions also with other expressions in program code that are too bulky.) [***] Can you answer the question that another poster failed to do?