C PR0gramming..

Neeeed 'C' Help.

I need to read in input from the command line argument and open the text file ( 2nd arguement; nums1.txt in this case)
ie:  ./shitprogram nums1.txt

and so what would i be inputting here:
fopen("????","r");

I know that argv[1] = "nums1.txt" but how would i use this as a variable in fopen() ?

use this as a variable in fopen()
FILE* f = fopen(argv[1], "r");

If you read the manual page of fopen, you understand what the arguments and return value are.

ya kkan read input frum da kernal

five years on DA KERNEL will teach ya dat

sage


#include <stdio.h>
int main(int argc, char** argv) {
    if(argc<2) {
        fprintf(stdio, "usage: %s filename\n", argv[0]);
    }
    int nig;
    FILE* fp = fopen(argv[1], "r");
    fscanf(fp, "%d", &nig);
    fclose(fp);
    return nig;
}

Read K&R.

>>6
Use fread and not fscanf.

>>2
>single character variable name
I always use
FILE* stream;
myself.

>>9
I always use
FILE* reimu;
myself.

>>9
Your name is hardly any better, it isn't very descriptive, it's like FILE * file, of course it's a fucking file, but what is it used for?

>>11
It's a lot better. An 'f' could be anything, whereas a 'stream' is, well, a stream. What else would you call it?

>>12
not that dude, but if the FILE* is a local variable to a function that is initialized to a call to fopen, then I name the variable in accordance to what is stored in the file, or what will be written to the file. If the FILE* is just a parameter to some generic printing or reading function for a data type, then I'll either name the parameter input or output, depending on if data is being read or written to it.

this is all pedantic of course.

I use:
ALL_CAPS for preprocessor constants
some_name for local symbols
First_letter for symbols of function types
_some_name for global symbols
_, __, ___, ... for symbols that should not be used
__name_ for symbols that are deferred by a typedef
name_ for volatile symbols

as for the naming itself:
name_t for types
name_p for pointer types
name_c for types that are part of a bigger type
multiple_words for symbols with multiple words
CamelCase if the symbol is something that implements some OOP principles
camelCase if the symbol is a type of the above OOP implementation
i, j, k, l for generic cycles
ret for a local symbol to hold the return value
s, r, t for generic strings
file_name for most local symbols, the meaning is interesting on the local scope only

>>14
0/10

>>12
>It's a lot better. An 'f' could be anything, whereas a 'stream' is, well, a stream. What else would you call it?

Better is finp as in input file pointer.  A variable with trivial scope deserves a trivial name.

>>16
>finp
Abbreviations are not universally intuitive. I'm sure most people know what an ID is but "finp" is undescriptive. "stream" is still better. If you ever need to have an input and output stream (say you're writing a function that reads from one stream and writes to another), you can just call them "istream" and "ostream". Anyone reading the code immediately knows that both of them are streams, and can hence deduce that one is an input stream and the other an output stream.

>>13
That makes sense, so long as you name them intuitively.

FILE* dick; /* Output stream */
FILE* anus; /* Input stream */

>>17
Lets play a game of find the least intuitively named function in the C std lib.

I choose wcstombs()

>>19
I think wcspbrk() is worse. What does pbrk mean? It supposedly stands for "pointer break" but that's hardly more meaningful.

>>18
cat << /dev/dick >> /dev/anus

>>19
wcs tombs - where wide character strings go to die.

sage

bampu pantsu

The characters initially were too gimmicky to feel like actual characters, though they're starting to flesh out a little bit now.

 Anyone got the chart for latest Nogizaka's handshake event?