Server Help

[Cyan~Fire]

Well duh! It doesn't work in C, so it must be bad!
_________________
This help is informational only. No representation is made or warranty given as to its content. User assumes all risk of use. Cyan~Fire assumes no responsibility for any loss or delay resulting from such use.
Wise men STILL seek Him.

[CypherJF]

so cry me a river...


_________________
Performance is often the art of cheating carefully. - James Gosling

[Mr Ekted]

iostream is about 27 levels of function calls away from the operating system. And do you know what it uses? printf!
_________________
4,691 irradiated haggis!

[Dr Brain]

And the OS is probably another 50 function calls away from the assembly.

Iostream makes it easier for programmers to develop programs. That's why it's there. Not so that it can print to the console with blindingly fast speed, because, after all, no one really cares how long it takes.
_________________
Hyperspace Owner

Smong> so long as 99% deaths feel lame it will always be hyperspace to me

[lp_street_soldier]

Bleh <_<

[Mr Ekted]

[SuSE]

Anybody read "The C Programming Language" or "The C++ Programming Language"? Comments?

[k0zy]

[-Smong-]

I prefer to put opening curly brackets on their own line as you can then find code blocks easier. Although when I first started I only had 160x160 screen and 4k file size limit so I was trying to cram as much as posible onto each line.

Also when passing parameters and such I put a space after the comma so it reads well.

[Mr Ekted]

Reformatted to my tastes. Also, scanf may fail if the input isn't very specific. You should use gets(), parse, and display appropriate errors.

Code: Show/Hide #include <stdio.h> int main (void) { double a0 = 0;   // erster Faktor der Gleichung double a1 = 0;   // zweiter Faktor der Gleichung double x = 0;    // x das berechnet werden soll puts("a1*x + a0 = 0"); puts("a1 und a0 eingeben:"); scanf("%lf %lf", &a1, &a0);      // Zahlen vom Typ double einlesen /* Lösung der Gleichung:    a1 * x + a0 = 0    a1 * x = -a0    x = -a0/a1 */ // Keine Lösung für a1=0, weil man nicht du 0 teilen darf, also Fehler abfangen. if (a1 != 0)    {    x = -a0 / a1;    printf("x= %.2lf\n", x);    } else    puts("Keine Lösung der Gleichung für a1 = 0"); return (0); }

[Mr Ekted]

Here's a picture I made showing most of my style issues...

[CypherJF]

style natzi jk... I think it's good advice to have a consistent clean programming style.

[Mine GO BOOM]

I like the function's to be indented. Other than that, its pretty much the same. I have the {}'s indented or not depending on whatever editor I use at the time sets up as the default.

I prefer /* */ for large comment blocks over //'s. And when I do, I always have each new line started with a *, and all the *'s line up vertically.

[Onlyone]

Dang Ekted... i thought i was a neat freak

[Solo Ace]

I dislike a few things in Ekted's style, although most of it is the same as mine.

Sourceforge has some project called "astyle", I hate how it was written but it works, anyway, it can restyle source code into a bunch of styles.
Could be interesting for "style nazis".

[Cyan~Fire]

I basically have the same style as MGB: Ekted's style but with indented functions. Actually, why do you not indent your functions, Ekted?

[Mr Ekted]

I don't indent functions because it's just extra work, wasted space, at the lowest level. Since function are always delimited by green comments, it's easy to see where they begin and end. It's not important to me that everyone use my style. They just need to be consistent within their own style, and be relatively clean. When people code using their own style, it's easier for them to code with fewer mistakes. I also believe in 1-file 1-coder methodology. I do not share code on projects. If someone takes over file(s) of yours, they own it and can format it how they wish.

[Dr Brain]

That's bacicly how I feel about peoeple's styles, with a few exceptions. When I code for ASSS, I try to follow the ASSS coding style. As it's not all that different from the way I code, this wasn't a big strech. Though I've recently given up this habit, I do feel that people should make a small effort to keep files in a public project similar to each other.

[Mr Ekted]

I found the ASSS source files that I saw to be unreadable. grel and I are on opposite ends of the spectrum for code design, coding style, and open source issues, so it's best that we don't work together anyways.