Search Results

You're thinking of configure scripts - they take a --prefix argument, makefiles don't.



Order of arguments with "make val=arg" doesn't matter either, and I don't know what you mean by the...

The problem is that:

*i--;

decrements the pointer, not the pointed-to value. I.e. it's equivalent to:


*(i--);


What you really want is:


(*i)--;


(On my machine at least, your...

Kind of, but you seem to just be checking for a specific error. Generally for *NIX system calls:


The return value tells you whether there was an error or not, and
errno tells you the specific...

You're trying to make a template specialization, which means you need to use a concrete type instead of the generic T. So you could do e.g.:


template<> int* AddFun<int*>(int* i, int* j) {
...

When a number starts with a leading "0", it's interpreted as an octal number, which can only use digits 0-7 (inclusive). Fix this, recompile and see what the output is.

Also, do you know that...

They could - it's just a matter of style. Using '(1 << 3)' makes it explicitly clear that what you're dealing with a bit. They both mean the same thing to the compiler, it's just what they signal to...

See the man pages for opendir() and readdir().

These errors are nothing to do with #include files - your compiler is finding them just fine.

Your problem is that the compiler can't find where these functions are defined - it's seen a header...

When the compiler sees this, it sees " Hello "World"" as three things - a string " Hello ", the token World and an empty string, "". To get it to recognise the middle quotes as part of the string, as...

Could you post the code you're using?

That's a variable declaration without a variable name; normally (only?) used in function signatures where you have to accept that type of argument, but don't actually want to use the variable. With...

Yes, this is a feature of both C and C++ - array names automatically decay into pointers where appropriate. When passing an array to a function, the array is never placed on the stack (how would the...

One mistake I notice straight-off is:


retval2=msgrcv(ad,&receive,1,1,0777);


The size parameter is in bytes, so it should be sizeof(receive) - your current code allows only a single byte to...

How are point1, point2 and randStart declared?

Also, as agma points out, it looks like you are confusing assignment and comparison:


// '=' assigns x the value 3
x = 3;

// '==' tests if x...

This is part of the C standard. Because the compiler can unambiguously determine that f in is a function pointer, it knows that "f()" can't mean anything else other than "a call to a function...

I believe it conforms to C99, but not C89 - you'll get an error if you compile in 89 mode with the -pedantic flag.

I only see cons if you're going to port to a compiler that doesn't support this....

You'd define the type of the struct in the header file, and declare (but not define) MEM_IO_PTRS in the header using extern:


/* in header file */

struct mem_ptrs
{
... /* members */
};...

That's an unusual question... why?

There is no signal to specifically flush all buffers, unless (i) a particular application includes a facility for specifically doing that or (ii) you don't mind...

You mean other than the C standard library (http://en.wikipedia.org/wiki/C_standard_library)? Well, on POSIX systems you have the POSIX library (http://en.wikipedia.org/wiki/C_POSIX_library) in...

No, file/socket descriptors are assigned on a per-process basis, so simply passing the descriptor to another process isn't possible. There are methods to do this, but they're more complicated than...

Are you sure you're entering "-c billy" and not "-n billy"?

Also, one of your lines:


if(optarg=="billy")


will result in undefined behaviour. Try changing it to "if...

ssize_t is not a built-in type - I believe you'll get it if you #include <stddef.h>.

EDIT: No, my bad - stddef.h is just for size_t - the signed variant is only POSIX, so it's in <sys/types.h>.

You probably don't have a static version of your c library installed - confirm by running "whereis libc" (it should show a libc.so, but no libc.a) and search your package manager for "libc.a", "gcc...

The last line essentially makes the macro evaluate to value, almost like it being "return value;" if SEARCH() were a function.

As a general rule (and this is only my opinion) it's generally better to use the C standard library functions in stdio.h where you can (i.e. for file I/O) and then use the POSIX standard functions in...