In article <
barmar-6CA80E....@reader.eternal-september.org>,
Barry Margolin <
bar...@alum.mit.edu> wrote:
>In article <
ef6e824b-2545-4c5b...@googlegroups.com>,
> Paul D <
spectre....@gmail.com> wrote:
>
>> Both perfect ! - thanks so much :)
>
>Which part of the non-cryptic solution was "tricky"? It's just a direct
>translation from English to awk. Use %-16s for the 6-character field,
>and %-6s for the 6-character fields? Maybe you didn't know how to loop
>over the remaining fields?
>
>The only way this could be tricky is if you just don't know some common
>awk idioms.
That seems to be precisely the case. I can't speak for any of the other
languages mentioned in the original thread title, but awk is a language
that exists at many different levels:
1) As not really a language at all; just a "shell helper", like cut,
join, etc.
2) As a simple language with some very basic constructs, but nothing
fancy. At this level, I put it as at about the same level as sed
(which actually does have a programming language embedded in it,
though no sane person would ever use it).
3) As a full blown programming language with various operating system
hooks, including the abiltiy to write your own code in extension
libraries and such.
Most people (*) do not get past #1 in the above list. The ability to do
printf() style formatting (including the %-16s thing) is at level 2.
(*) Including, I would assume, OP.
--
The randomly chosen signature file that would have appeared here is more than 4
lines long. As such, it violates one or more Usenet RFCs. In order to remain
in compliance with said RFCs, the actual sig can be found at the following URL:
http://user.xmission.com/~gazelle/Sigs/God