if ((fd = open(...)) != -1) {
/* do something with fd */
} else {
perror("open");
}
int fd; /* fd must be declared in order to be assigned */
if ((fd = open(...)) != -1) {
/* do something with fd */
} else {
perror("open");
}
int fd = open(...);
if (fd != -1) /* etc */
if ((int fd = open(...)) != -1) /* etc */
if ((int fd == open(...)) != -1) /* etc */
Anyways, I am a bit torn about the second option. I like the idea of putting the call inside the if clause as it makes for a very explicit error handling but the uninitialized declaration is ugly. What I do in practice tends to depend on the situation but it is rarely satisfying.
Your last suggestion would be ideal, but as you said, it is invalid code unfortunately.
Maybe this
for (int fd = open(...); fd != -1; fd = -1) {
/* do stuff */
}
> for (int fd = open(...); fd != -1; fd = -1) {
#define LET(...) for(__VA_ARGS__,_tmp[0],*_once=_tmp; _once ;_once=0)
/* ^^^ goes in a header file */
LET(int fd = open())
{
if(fd == -1) { /* handle error, return or break */ }
/* do stuff */
} char *strcpy(char *d, char *s) {
char *r = d;
while (*d++ = *s++);
return r;
}
while((i = getchar()) != EOF) putchar(i);
This type of thing seems to be "encouraged"...