07-18-2016
Scrutinizer - sysadmins do put two or three commands together on the fly. I do. Pipe this command into this other command and then sort the output. That is essentially what the -exec predicate does for the find command.
Scripts coded as giant one-liners are out of bounds. Period. rbatte1 covers why really well.
I thought we were discussing the massive one-liners we see here a lot. We seem to want to define good and bad one-liners here. So let's say one-liners in scripts meant to be part of production should not be written as "multi-blobs" of piped commands.
4 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
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 Replies)
Discussion started by: u6ik
2 Replies
2. Shell Programming and Scripting
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... (6 Replies)
Discussion started by: PikK45
6 Replies
3. What is on Your Mind?
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... (6 Replies)
Discussion started by: ahamed101
6 Replies
4. What is on Your Mind?
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... (3 Replies)
Discussion started by: wisecracker
3 Replies
LEARN ABOUT DEBIAN
libcaca-style
libcaca-style(3caca) libcaca libcaca-style(3caca)
NAME
libcaca-style - Libcaca coding style
General guidelines
A pretty safe rule of thumb is: look at what has already been done and try to do the same.
o Tabulations should be avoided and replaced with eight spaces.
o Indentation is generally 4 spaces.
o Lines should wrap at most at 79 characters.
o Do not leave whitespace at the end of lines.
o Do not use multiple spaces for anything else than indentation.
o Code qui fait des warnings == code de porc == deux baffes dans ta gueule
C coding style
Try to use short names whenever possible (i for indices, w for width, cv for canvas...). Macros are always uppercase, variable and function
names are always lowercase. Use the underscore to separate words within names:
#define BROKEN 0
#define MAX(x, y) ((x > y) ? (x) : (y))
unsigned int x, y, w, h;
char *font_name;
void frobulate_every_three_seconds(void);
const is a suffix. It's char const *foo, not const char *foo.
Use spaces after commas and between operators. Do not use spaces after an opening parenthesis or before a closing one:
a += 2;
b = (a * (c + d));
x = min(x1, x2, x3);
Do not put a space between functions and the corresponding opening parenthesis:
int function(int);
A space can be inserted after keywords such as for, while or if, but consistency with the rest of the page is encouraged:
if(a == b)
return;
if (p == NULL)
Do not put parentheses around return values:
return a + (b & x) + d[10];
Opening braces should be on a line of their own, aligned with the current block. Braces are optional for one-liners:
int function(int a)
{
if(a & 0x84)
return a;
if(a < 0)
{
return -a;
}
else
{
a /= 2;
switch(a)
{
case 0:
case 1:
return -1;
break;
default:
return a;
}
}
}
C++ coding style
Nothing here yet.
Version 0.99.beta18 Fri Apr 6 2012 libcaca-style(3caca)