Wut ? C

AviStruct* GetVideoInfo(char*file)
{
    AviStruct* MyVideo = (AviStruct*)s_alloc(sizeof(AviStruct));
    FILE*f = fopen(file,"rb");
    if (f)
    {
        unsigned int dwRate;
        unsigned int dwScale;
        unsigned int dwLength;
        fseek(f,0x84, SEEK_SET );
        fread(&dwRate,4,1,f);
        fseek(f,0x80, SEEK_SET );
        fread(&dwScale,4,1,f);
        fseek(f,0x8C, SEEK_SET );
        fread(&dwLength,4,1,f);
        fseek(f,0x40, SEEK_SET );
        fread(&MyVideo->width,4,1,f);
        fseek(f,0x44, SEEK_SET );
        fread(&MyVideo->height,4,1,f);
        MyVideo->fFps = (float)((float)(dwRate)/(float)(dwScale));
        MyVideo->fDuration = (float)((float)(dwLength)/(float)(MyVideo->fFps));
        return MyVideo;

    }
    return 0x0;
}

>>28
That's shitCase, and itsUgly. Also, how the fuck will you tell a function from a variable when it's only one word? Fucking niggers.

>>31
Useless? Nigger! If you capitalize functions to tell them from variables, then what the fuck fuck is? A function? A variable? And don't give me that "verbs are for... while you use..." bullshit, I hate your retarded naming conventions and all the "software engineering" idiots who think programming can be rationalized to that point.

Also, shitCase looks like shit, is harder to transform, etc.

So the bottom line is, UseCamelCase, not shitCase, faggot. You're ugly.

ITT haskellFags

>>41
functions are variables too. you don't need to tell them apart.

>>41
 I just can't understand why you think there's a need to separate functions from variables using some ``naming convention''; I've never had such problem with any language, ever.

I just use whatever naming convention is used by the language's standard library, and several languages happen to use shitCase without any problems, which has led me to believe that the rabid shitCase haters are just C++ kiddies or mindless [Java,Haskell,Obj-C,whatever] bashers who desperately try to rationalize their worthless opinions.

Just use the Hungarian naming convention and stfu goddamnit.

>>43
The fact they're variables is absolutely true. However, I prefer to separate applicable variables from non-applicable ones using some naming convention. On Python (one word, the forced indentation of code) this means I'll CamelCase all variables bound to functions (be them anonymous or uh... nonymous), classes and other objects which happen to be callable (property __call__ defined and set to an applicable value). For example, I'd start defining map like:
define Map(F, *iters):
For very basic, non-application utilities such as map, I make an exception, though, and stay with lowercase.

>>44
If you don't understand naming conventions, then why do you adhere to them, and shitCase of all of them?

>>45
moronanon45.methDoAction(actnSTFU)

reach satori

>>43
No, no, no. Variables are simply functions that no longer require arguments.

No no no no, serious business!

>>43,48
No, no, no, no. It depends solely from the definition given from the language spec.

52 Name: Anonymous 2011-03-31 22:22