Alan Gauld wrote:
Syntactic sugar *IS* a practical benefit. After all, every language above
assember is syntactic sugar, and by your definition of no practical use.
Ah, but by that standard even assembler is syntactic sugar, now
where are those hex codes and my keypunch? :-)
By practical
I'm working on a program to do some processing on a directory tree. If I had
been doing it in a shell script, the core of the processing would have been in
a find $ROOT -type f -name FOO -print command
On the web, I found a snippet of code that demonstrated the os.walk module and
I created a
I'm a semi-competent python user who has discovered that all the
toolkits I really have use of are bound up in java classes. I can cope
with this, because there is Python, but I was wondering if anyone who
has spent more time around it than I have could spare any advice that
will make the
I'm in the planning stages of writing a program to manage user accounts
on some unix boxes that cannot be directly hooked into our central
account management system at work. Obviously, the heavy lifting can be
done with shell calls to the underlying commands or via direct edits of
the relevant
Alan Gauld wrote:
I said awk was easier to learn but less capable than Perl.
Perl is capable of things that awk can only dream of!
Surely you jest, Alan. :-)
Both perl and awk are turing complete, hence anything perl can do, awk
can do as well. Now, as to which one would be easier to work with
Alan Gauld wrote:
My data set the below is taken from is over 2.4 gb so speed and
memory
considerations come into play.
To be honest, if this were my problem, I'd proably dump all the data
into a database and use SQL to extract what I needed. Thats a much
more effective tool for this kind of
