>One small point comes to light now you've released this: version.h is >quite a common thing to have on your include path; certainly under MS >operating systems there tends to be a version.h already on the include >path which may cause confusion. Any reason not to call it jk_version.h? +1 for jk_version.h Sure it will take less than 30ms to JF :)
- Re: #define JK_VERSION in j-... jean-frederic clere
- Re: #define JK_VERSION in j-... Andy Armstrong
- Re: #define JK_VERSION in j-... Andy Armstrong
- RE: #define JK_VERSION in j-t-c (doesn't exist) GOMEZ Henri
- Re: #define JK_VERSION in j-t-c (doesn't exist) Andy Armstrong
- RE: #define JK_VERSION in j-t-c (doesn't exist) GOMEZ Henri
- Re: #define JK_VERSION in j-t-c (doesn't exist) Andy Armstrong
- RE: #define JK_VERSION in j-t-c (doesn't exist) GOMEZ Henri
- Re: #define JK_VERSION in j-t-c (doesn't exist) Andy Armstrong
- RE: #define JK_VERSION in j-t-c (doesn't exist) GOMEZ Henri
- Re: #define JK_VERSION in j-t-c (doesn't exist) GOMEZ Henri
- Re: #define JK_VERSION in j-t-c (doesn't exist) jean-frederic clere
- Re: #define JK_VERSION in j-t-c (doesn't exis... Andy Armstrong