One liners, quick rant... Post: 302977499

Sponsored Content

The Lounge What is on Your Mind? One liners, quick rant... Post 302977499 by Neo on Tuesday 19th of July 2016 07:18:33 AM

07-19-2016

Administrator

Yeah... my view is that if you want (generally) "one liner" for a more complex task or expression, but it in a file and save it; and execute the script.

Of course, to each his own, and I'm not saying others should not be creative; I'm only saying that my experience is that I have so much code to manage, some from 10 years ago, and "elegant" or "fancy" one liners are hard to understand years after writing them, at least for me.

Anyway, I'm always going back and looking a legacy HTML and PHP and other admin scripts for this site and all the backup sites, etc. I try to keep is very clean, easy to understand, because with a site like this; you could be out have wine with friends and need to come back to the desk to fix a problem!

But I still use the unix pipeline for command line tasks, but nothing fancy or that I would keep for sysadmin.

Anyway, maybe I misunderstood the post or the intention here... which is possible since I have been coding like crazy lately!!

LOL

Neo

View Public Profile for Neo

Visit Neo's homepage!

Find all posts by Neo

4 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Where can I rant?

First of all, apologies to the admins for not reading the rules totally and missing the bit about ranting off about other OSs. But that raises a question. Where do you go to have a good rant, to vent your disgust at various corporations and thier hideous behaviour? :confused:

2. Shell Programming and Scripting

awk - one liners

Guys, I have a requirement like this. A file has >5K records always. Separated by "|", it has 30 fields for each line. In some lines, I am getting an odd field. say, the 15th field is supposed to be 2 characters but comes in as >2. In this case, for resolving this I need to copy the value of...

3. What is on Your Mind?

Those simple one liners

I wanted to say LOL and punch my face when I saw post#11 (where Don_Cragun even reduced the string manipulation with a simple regex) in the thread https://www.unix.com/shell-programming-scripting/220553-add-0-start-filename-2.html I mean, when things can be done with just a one liner, sometimes I...

4. What is on Your Mind?

A rant...

Hi guys... (Apologies for any typos etc...) This is basically a rant. I have been doing kids level projects and writing code to suit since around 1982, for the uProfessor, for the Sinclair Spectrum and later for the QL, IBM-XT in MS-DOS and after that for a 386DX40 up to Windows 95, until I...

LEARN ABOUT CENTOS

time

TIME(2) 						     Linux Programmer's Manual							   TIME(2)

NAME

       time - get time in seconds

SYNOPSIS

       #include <time.h>

       time_t time(time_t *t);

DESCRIPTION

       time() returns the time as the number of seconds since the Epoch, 1970-01-01 00:00:00 +0000 (UTC).

       If t is non-NULL, the return value is also stored in the memory pointed to by t.

RETURN VALUE

       On success, the value of time in seconds since the Epoch is returned.  On error, ((time_t) -1) is returned, and errno is set appropriately.

ERRORS

       EFAULT t points outside your accessible address space.

CONFORMING TO

       SVr4, 4.3BSD, C89, C99, POSIX.1-2001.  POSIX does not specify any error conditions.

NOTES

       POSIX.1	defines  seconds  since  the Epoch using a formula that approximates the number of seconds between a specified time and the Epoch.
       This formula takes account of the facts that all years that are evenly divisible by 4 are leap years, but years that are  evenly  divisible
       by  100	are not leap years unless they are also evenly divisible by 400, in which case they are leap years.  This value is not the same as
       the actual number of seconds between the time and the Epoch, because of leap seconds and because system clocks are not required to be  syn-
       chronized  to  a  standard  reference.	The  intention	is  that  the  interpretation of seconds since the Epoch values be consistent; see
       POSIX.1-2008 Rationale A.4.15 for further rationale.

SEE ALSO

       date(1), gettimeofday(2), ctime(3), ftime(3), time(7)

COLOPHON

       This page is part of release 3.53 of the Linux man-pages project.  A description of the project, and information about reporting bugs,  can
       be found at http://www.kernel.org/doc/man-pages/.

Linux								    2011-09-09								   TIME(2)