|
 |
Disnel <dis### [at] hlavacek-partner cz> wrote:
: #include "some_include.inc" searches for include in
: actual directory (directory from which was parent file
: readed, NOT directory where main scene file is located)
: and #include <some_include.inc> searches in paths
: given with +l switch in commandline.
Doesn't the current #include do both? Why do we need separate include
commands?
It's usually not a good idea to make an include file with the same name
with a standard include file.
--
main(i,_){for(_?--i,main(i+2,"FhhQHFIJD|FQTITFN]zRFHhhTBFHhhTBFysdB"[i]
):_;i&&_>1;printf("%s",_-70?_&1?"[]":" ":(_=0,"\n")),_/=2);} /*- Warp -*/
Post a reply to this message
|
|
|
|
Warp wrote:
>
> Disnel <dis### [at] hlavacek-partnercz> wrote:
> : #include "some_include.inc" searches for include in
> : actual directory (directory from which was parent file
> : readed, NOT directory where main scene file is located)
>
> : and #include <some_include.inc> searches in paths
> : given with +l switch in commandline.
>
> Doesn't the current #include do both? Why do we need separate include
> commands?
> It's usually not a good idea to make an include file with the same name
> with a standard include file.
Sure, but for example I want to have one system wide directory for
includes (/usr/local/POV/include). In this directory I want to have
some "packages", for example in /usr/local/POV/include/arch should
be architecture.inc, ar_furniture.inc, ar_beams.inc, ....
at_<something> is automatically included from architecture.inc, thus
in scene I want to write only "include <arch/architecture.inc>" without
the need to add /usr/local/POV/include/architecture to +l path.
This don't work.
... sorry for sending it directly to you, mouse-like control is not
every time the best ...
>
> --
> main(i,_){for(_?--i,main(i+2,"FhhQHFIJD|FQTITFN]zRFHhhTBFHhhTBFysdB"[i]
> ):_;i&&_>1;printf("%s",_-70?_&1?"[]":" ":(_=0,"\n")),_/=2);} /*- Warp -*/
Post a reply to this message
|
|
