Tree: f00e3c0f82

master

cln_1-3-4

Branches Tags

${ item.name }

Create tag ${ searchTerm }

Create branch ${ searchTerm }

from 'f00e3c0f82'

${ noResults }

Commit Graph

3 Commits (f00e3c0f820e60d286bece18e84a9726f75b9905)

Author	SHA1	Message	Date
Alexei Sheplyakov	8169a19b38	Use paths relative the `src' directory in the #include directives. Typical CLN source file starts with // General includes. #include "cl_sysdep.h" // Specification. #include "cl_2DS.h" // Implementation. #include "cl_2D.h" #include "cl_DS.h" It takes a while to figure out which files are included. So, use paths relative to the `src' directory, like this: // General includes. #include "base/cl_sysdep.h" // Specification. #include "src/base/digitseq/cl_2DS.h" // Implementation. #include "base/digit/cl_2D.h" #include "base/digitseq/cl_DS.h" This makes CLN less hacker hostile.	17 years ago
Richard Kreckel	850abfde7f	* All Files have been modified for inclusion of namespace cln; I am too lazy for a detailed discussion of all the changes. Many identifiers got their `cl_' stripped off. Ok, this is a clumpsy CVS log-entry. Promise: more will soon go into the file ChangeLog. I apologize for the inconvenience. :-(	26 years ago
Richard Kreckel	dd9e0f894e	Initial revision	26 years ago