4 replies to this topic

[Aereshaa]

Check out this initializer from my tetris implementation:

typedef struct {struct {int x,y;} block[4];} piece;
piece deck[7]={{{{4,0},{5,0},{6,0},{7,0}}},{{{4,0},{5,0},{6,0},{4,1}}},{{{4,0},{5,0},{6,0},{5,1}}},{{{4,0},{5,0},{6,0},{6,1}}},{{{6,0},{5,0},{5,1},{4,1}}},{{{4,0},{5,0},{5,1},{6,1}}},{{{4,0},{5,0},{5,1},{4,1}}}};
//ILTJSZO

Do you think it could be longer?

[frenchy]

I reckon perhaps, if you expand to 3D tetris.

Enjoy

[dargueta]

Dude...this is horrendous. At least break it up a bit:

typedef struct {
    struct {
        int x, y;
    } block[4];
} piece;

piece deck[7]={
    {
        {
            {4,0},
            {5,0},
            {6,0},
            {7,0}
        }
    },
    {
        {
            {4,0},
            {5,0},
            {6,0},
            {4,1}
        }
    },
    {
        {
            {4,0},
            {5,0},
            {6,0},
            {5,1}
        }
    },
    {
        {
            {4,0},
            {5,0},
            {6,0},
            {6,1}
        }
    },
    {
        {
            {6,0},
            {5,0},
            {5,1},
            {4,1}
        }
    },
    {
        {
            {4,0},
            {5,0},
            {5,1},
            {6,1}
        }
    },
    {
        {
            {4,0},
            {5,0},
            {5,1},
            {4,1}
        }
    }
};

[jwxie518]

While there is no law that forbit you from doing that, your professor / boss will fail you with that code you have in the first place.
What is the very first rule of software engineering?
1. Readability

LOL

[dargueta]

Virtues of a Programmer:

#1: Laziness