Nicolas Calimet <pov### [at] freefr> wrote:
>
>  Now the question is: why do you prepend $CPLUS_INCLUDE_PATH in the
> first place ?  I'd expect to _append_ it to your own list of paths, thus
> preventing this implicit "." to be added automatically:
>
> export CPLUS_INCLUDE_PATH=/dir/to/add:/another/one:${CPLUS_INCLUDE_PATH}
>

sure, but this still isn't a guaranteed win.  CPLUS_INCLUDE_PATH could be
modified further by some other program/script, and there's no way one can
be sure to be consistent/correct 100% of the time.  I guess thats why I
like using the bash:

${param:+word}

construct - it will check if param is set, at least, and do the Right Thing
if it isn't.

The struggle continues.  ;)

Regards,
Tim

Post a reply to this message