Re: How awk will do that
- From: gazelle@xxxxxxxxxxxxxxxxxxx (Kenny McCormack)
- Date: Sat, 23 Jul 2005 21:21:10 GMT
In article <3kfcgoFtc7l6U1@xxxxxxxxxxxxx>,
Patrick TJ McPhee <ptjm@xxxxxxxxxxxx> wrote:
....
>To put my oar into this discussion, it's worthwhile knowing how to write
>portable code, simply because sometimes you need to write things that
>will run on machines over which you have no control. Part of that is
>knowing which functions and which behaviour are part of standard awk,
>and which are part of the extended version you're running on your own
>machines, and you don't complain about other people using extensions in
>perfectly standard code.
There's a lot more to it than that, but I don't feel the need to explain it
all here. If you don't see it, you probably never will.
Suffice to say that there are very good practical reasons why it is better,
in the real world, to pick a tool that has what you need, rather than let
everybody re-invent the wheel(s) in new and creative ways.
And, to quote Casino, that's that.
.
- Follow-Ups:
- Re: How awk will do that
- From: Jan Weber
- Re: How awk will do that
- References:
- How awk will do that
- From: nasir
- Re: How awk will do that
- From: Ed Morton
- Re: How awk will do that
- From: Janis Papanagnou
- Re: How awk will do that
- From: Patrick TJ McPhee
- How awk will do that
- Prev by Date: Re: XML parsing with awk - getXML.awk
- Next by Date: Re: XML parsing with awk - getXML.awk
- Previous by thread: Re: How awk will do that
- Next by thread: Re: How awk will do that
- Index(es):
Relevant Pages
|
|
