Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[TheBiggerFish]

Anyone who uses tabs is a filthy heathen. Deus vult.

Spaces is heresy. If someone suggested that we replace periods in sentences with "aaaa" we'd think they were crazy. 1 tab == 1 indent, the way God intended.

Because "." and "aaaa", they don't have the same function.
Whereas tabs and spaces are both whitespace characters, meant to separate and indent and all.

[Antsan]

I would be interested in a good argument for spaces over tabs, because I just don't see the benefit of using spaces. The only reason you should ever be messing with source code is because you want to change what it does, not that you need to change how it looks. I get the feeling it has more to do with OSes historically freaking the fuck out if they find tabs in text files, causing this superstitious aversion to tabs.

Common Lisp has such strict indenting guidelines that they can be and are applied automatically while coding. The are never just in increments of tabs but rather in relation to their, uhm, parent node in the source tree. So they are either placed aligned with the arguments on the first line of the node:

Code: [Select]

(some-stuff foo (bar quux)
            baz)  ; note how this kind of indentation not only highlights how this belongs to some-stuff
                  ; but also enhances the visibility of the arguments on the previous line
or, if there are no arguments on the first line, just to the right of the enclosing paren:

Code: [Select]

(yay
 boo)
or, in some special cases one space further to the right, because these special constructs expect something multi-line there:

Code: [Select]

(progn
  (one call)
  (another thing to do))

(let ((a 2)  ; variable definitions line up nicely
      (b 3))
  (+ a b))   ; the code is also easily distinguishable by the way it is less indented
This reads very nicely, lines up things that belong together and so on. This wouldn't be possible with tabs.

For C++ emacs also does auto-indenting and uses different indent widths for different contexts. It makes code more readable because the offset conveys additional information.
So, the big advantage of spaces is the variability and thus readability. I don't want always 2 or always 4 or always 8 spaces for an indent level.

[GiglameshDespair]

I wrote a quick shitty program for Taricus in C#.
It could certainly be improved (error handling, etc), but it does the job.
Haven't programmed anything in months, so it's something at least?

Code: [Select]

int die = 0;
            int noOfDice = 0;
            int check = 0;
            int noOfSuccess = 0;
            int rolledResult= 0;

            Console.Write("GigDice v0.1.5 \nEnter die: ");
            Console.ForegroundColor = ConsoleColor.Red;
            die = Convert.ToInt32(Console.ReadLine());
            Console.ForegroundColor = ConsoleColor.Gray;

            Console.Write("\nEnter number of dice to roll: ");
            Console.ForegroundColor = ConsoleColor.Red;
            noOfDice = Convert.ToInt32(Console.ReadLine());
            Console.ForegroundColor = ConsoleColor.Gray;

            Console.Write("\nEnter number to score to succeed: ");
            Console.ForegroundColor = ConsoleColor.Red;
            check = Convert.ToInt32(Console.ReadLine());
            Console.ForegroundColor = ConsoleColor.Gray;

            Random r = new Random();

            for (int i = 0; i < noOfDice; i++)
            {
                rolledResult = r.Next(1, die);
                Console.WriteLine("Roll was: " + rolledResult);

                if (rolledResult == check || rolledResult > check)
                {
                    Console.WriteLine("Success");
                    noOfSuccess = noOfSuccess +1;
                }
                else
                {
                    Console.WriteLine("Failure");
                }
                noOfDice = noOfDice--;

            };
            Console.Write("\nNumber of successes was: ");
            Console.ForegroundColor = ConsoleColor.Red;
            Console.Write(noOfSuccess);
            Console.ForegroundColor = ConsoleColor.Gray;

            Console.WriteLine("\nPress any key to exit");
            Console.ReadKey();
Output looks like:

Spoiler (click to show/hide)

[cerapa]

Code: [Select]

    int a[10] = {10};
    while (a[0] --> 1) a[1[a-1]] = (a>a)[a];
This is perfectly valid C++ code. Can you guess what it does without compiling it?

[TheBiggerFish]

Code: [Select]

    int a[10] = {10};
    while (a[0] --> 1) a[1[a-1]] = (a>a)[a];
This is perfectly valid C++ code. Can you guess what it does without compiling it?

Nope...

[MagmaMcFry]

Code: [Select]

    int a[10] = {10};
    while (a[0] --> 1) a[1[a-1]] = (a>a)[a];
This is perfectly valid C++ code. Can you guess what it does without compiling it?

It initializes an array of integers with the values 0 to 9.

Spoiler (click to show/hide)

Code: [Select]

int a[10] = {10}
Allocates an integer array of size 10, but initializes only the first element, to 10.

Code: [Select]

while(a[0] --> 1)
Just change up some whitespace:

Code: [Select]

while (a[0]-- > 1)
Iterates a[0] from 9 to 1, then leaves a[0] at 0.

Code: [Select]

a[1[a-1]]
Small detail of C++ you shouldn't ever use: a[i] is just syntactic sugar for *(a+i). Hence a[i] is the same as i[a]. So a[1[a-1]] is the same as a[a[0]].

Code: [Select]

(a>a)[a]
Same deal. (a>a)[a] is the same as 0[a] is the same as a[0].

Cleaned up:

Code: [Select]

    int a[10] = {10};
    while (a[0]-- > 1) a[a[0]] = a[0];

[TheBiggerFish]

It's a code puzzle.  It's supposed to be obfuscated?

[Putnam]

i like --> there

that's silly

while a[0]-- > 1 is a more... not dumb way to put it

[miauw62]

Haha I see what putnam means, I somehow thought that --> was some fancy new operator I hadn't heard of.

[Skyrunner]

It seems like I will need to learn how to implement PID controllers!

And then connect them together to steer my space ships! :/

Maybe I should have left them with simple behaviour...


Edit: so it seems that multiple-in, multiple-out PID controllers are really hard to design.  What now..

[itisnotlogical]

I created a game where you have to slash shapes along their lines of symmetry. Now that all the basic mechanics are down, I just have to create about 50-80 shapes so that the game doesn't get too repetitive... Does anybody else suddenly get intensely bored and frustrated with projects that reach this stage?

[EnigmaticHat]

Sounds like you prefer creating mechanics to creating content.

[Orange Wizard]

The solution is collaboration!

[Antsan]

The solution is to create a shape generator.

[i2amroy]

The solution is collaboration!

The solution is to create a shape generator.

Both of these are wonderful solutions. The first is ideally something you do pretty early in the project to make the whole thing go easier; the second is nifty for letting you have an "infinite mode" to your game.