CC65 Question.

[mysecretgarden]

Hi to everyone!
I want to write my owm function to use with the CC65 compiler.
For example, if I want to include

#include <myfunction.h>

I need to write the myfunction file, with the functions signatures, and teh myfunction.c with the code implementation.

The compiler return me an error, because don't find the files myfunction.h and myfunction.c...I'm wrong?


Bye!

[pallas]

try:

#include "myfunction.h"

[mysecretgarden]

try:

#include "myfunction.h"

wow!! Great!!!!

Thanks!!

[Mike]

For example, if I want to include

#include <myfunction.h>

I need to write the myfunction file, with the functions signatures, and teh myfunction.c with the code implementation.

The compiler return me an error, because don't find the files myfunction.h and myfunction.c...

I'm sorry to write this, but this kind of question reveals that you might be missing some really basic concepts of the C programming language.

To answer your question, an #include with a file name in angle brackets ("<" and ">") searches for the file in an implementation dependent manner. More accurately, the path to these files is supposed to contain only the ANSI headers and extra headers specific to the compiler.

If nothing other has been specified by the linker or the command line of the compiler invocation, an #include with the file name in double quotes searches in the same directory as the corresponding *.c file.

If I am right with my assumption, that you are just about to start out with C, I'd recommend you first learn it with an ANSI standard conformant compiler (cc65 only implements a subset of C). For Windows, the C/C++.net Express Edition is available from Microsoft at no cost. Otherwise, all Unix derivates always provide you with a C compiler.

K&R, The C Programming Language is still THE reference for ANSI C.

For Commodore computers, cc65 is possibly a good development tool, if the slight speed loss against pure assembly can be tolerated, and you can live with its restrictions (for example, float numbers are not supported in cc65). Using it to its full potential requires a good grasp of the idiosyncracies of the cc65 interface to the CBM KERNAL and the memory architecture of the target platform.

[rhurst]

I'm sorry to write this, ...

Good stuff, Mike. All relevant info and supporting opinion, regardless the state of any underlying assumption with the poster's plea. I know I get something out of every one of your posts.

[Kweepa]

Agree with everything except this:

I'd recommend you first learn it with an ANSI standard conformant compiler (cc65 only implements a subset of C).

I recommend learning with whatever helps you write the game/program you want to write, otherwise you'll lose motivation.
cc65 is sufficiently similar to C that you're not going be learning many terrible habits.

[mysecretgarden]

For example, if I want to include

#include <myfunction.h>

I need to write the myfunction file, with the functions signatures, and teh myfunction.c with the code implementation.

The compiler return me an error, because don't find the files myfunction.h and myfunction.c...

I'm sorry to write this, but this kind of question reveals that you might be missing some really basic concepts of the C programming language.

To answer your question, an #include with a file name in angle brackets ("<" and ">") searches for the file in an implementation dependent manner. More accurately, the path to these files is supposed to contain only the ANSI headers and extra headers specific to the compiler.

If nothing other has been specified by the linker or the command line of the compiler invocation, an #include with the file name in double quotes searches in the same directory as the corresponding *.c file.

If I am right with my assumption, that you are just about to start out with C, I'd recommend you first learn it with an ANSI standard conformant compiler (cc65 only implements a subset of C). For Windows, the C/C++.net Express Edition is available from Microsoft at no cost. Otherwise, all Unix derivates always provide you with a C compiler.

K&R, The C Programming Language is still THE reference for ANSI C.

For Commodore computers, cc65 is possibly a good development tool, if the slight speed loss against pure assembly can be tolerated, and you can live with its restrictions (for example, float numbers are not supported in cc65). Using it to its full potential requires a good grasp of the idiosyncracies of the cc65 interface to the CBM KERNAL and the memory architecture of the target platform.

Mike, thank you for your answer, but the question is smaller than your answer. I simply ask a little question about the include directive, I'm c# programmer, I simply forget how this directive work because the C ansi is not my language!