prolem in method signature

[c_weed]

What is wrong with this line of code?

void retrieve(unsigned int position, char output[20]) throw(std::out_of_range);

H:\code_blocks_workspace\src\..\include\LinkedList .h|13|error: expected type-specifier|
H:\code_blocks_workspace\src\..\include\LinkedList .h|13|error: expected ')'|
H:\code_blocks_workspace\src\..\include\LinkedList .h|13|error: expected ';'|
H:\code_blocks_workspace\src\LinkedList.cpp|100|er ror: expected type-specifier|
H:\code_blocks_workspace\src\LinkedList.cpp|100|er ror: expected ')'|
H:\code_blocks_workspace\src\LinkedList.cpp|100|er ror: expected initializer|
||=== Build finished: 6 errors, 0 warnings ===|

[kmdv]

I think nothing.

[nick753]

Shouldn't it just be char output[] ?

[stahta01]

C Programmer with guess
Did you have "#include <stdexcept>" in the file below the line with error.

Tim S.

[c_weed]

C Programmer with guess
Did you have "#include <stdexcept>" in the file below the line with error.

Tim S.

You know, that was a really good guess.
One thing I'm curious about is should I include things in the .h (header) or .cpp (implemntation) file?

[tabstop]

You know, that was a really good guess.
One thing I'm curious about is should I include things in the .h (header) or .cpp (implemntation) file?

You should #include the header in whatever file uses elements from that header.

[kmdv]

You know, that was a really good guess.
One thing I'm curious about is should I include things in the .h (header) or .cpp (implemntation) file?

You should avoid including in header files as much as possible (it makes compilation process longer). Use forward declarations wherever possible. You should also have (a) precompiled header(s) with commonly used headers that does not change often (like external libraries' headers, STL, etc). Most of my inclusions are in .cpp files.

[Elysia]

Throwing declarations are rarely useful, as few, if any, compilers actually heed them. Microsoft's compiler is actually known not to even implement this and gives a warning. They're usually only useful as documentation--that is, understanding what a function may throw.