#Include Naming conventions

[sadlpx]

I'm tryng to improve the readability and ease of usage on my include files

Currently my include statement looks like this.

#include "C:\Documents and Settings\Zac.ZAC-6227651BFB7\My Documents\Programming\CCS PIC C Released\Battery Tester Rev 5_0\Battery Tester R5.h"

What I'd like to do is break it into two parts where the buld of the path structure is in a define statement, all other include line use that define to shorten the path

example:
#Define _porter_ccs C:\Documents and Settings\Zac.ZAC-6227651BFB7\My Documents\Programming\CCS PIC C Released

#include "_porter_ccs\Battery Tester Rev 5_0\Battery Tester R5.h"

This is a simple example of what i'm trying to do ( actual structure more complicated) BUT
am I one the right track :question: :question: :question:
Can I do what I want

[RF_Developer]

It's more conventional to name include files simply and set the project options search paths to the relevant locations on your directory structure. The problem is a) readability, long path names or even path names at all, are not easily readable and b) portability: paths change depending on where the project is located and where its compiled, therefore paths usually go in the IDEs project options, not in your code.

Library code, drivers for your favourite I2C and SPI peripheral ICs can go in a library directory somewhere handy, e.g. on a network drive, while your own project specific code generally sits in a single directory, maybe with subdirectories in some complex projects.

In general for readability and portability I try to keep it simple. If I see something like: