PureBasic Forums - English

Why is current directory for operators IncludeFile and XIncludeFile does not correspond to directory with the file?
Test code. http://depositfiles.com/files/np3qenm48

Post your code on the forum - that download site is potentially dangerous.

In addition to what IdeasVacuum wrote:

This is not a bug report. Please post questions like this in the appropriate subforum.
Before calling something a bug (in PureBasic), be sure that you have understood what's going on.

User_Russian wrote:Why is current directory for operators IncludeFile and XIncludeFile does not correspond to directory with the file ?

Ask Fred, I would really like to know why he choose to do it this way !

As a workaround, we can do this:

change
to
It's a little ugly and long to type, but we don't have another choice.

Feature Request and discussions about it -> http://www.purebasic.fr/english/viewtop ... =3&t=35292

And yes, you should have post the code in the forum, no need for a zip for some lines of code, moreover the link will cease to work sooner or later, whilst the code you post here will not.

luis wrote:

Code: Select all

IncludeFile #PB_Compiler_FilePath + "Inc_2.pbi"

It's a little ugly and long to type, but we don't have another choice.

I made a macro and added it to the compiler as a resident (so no need to include it in the source): If you need to publish your code somewhere...a quick search and replace and it's done.
No problem there either.

User_Russian wrote:Why is current directory for operators IncludeFile and XIncludeFile does not correspond to directory with the file?

http://www.purebasic.com/documentation/ ... ludes.html :
"IncludePath will specify a default path for all files included after the call of this command."

You are right, IncludePath in the simple case proposed by User_Russian can solve the problem, but it's not a solution for the general case where you want the included files to include other files relative to THEIR position in the tree to make the whole tree structure always working independently from its position in the filesystem and between different computers.
I think you are better off in taking the habit of use #PB_Compiler_FilePath and solve the problem always and once for all.
In any case anyone can always learn this on his own skin the day he will try to make a tree structure a little more complicated than this one

I just came across the same issue: If you ask me always having to use "XIncludeFile #PB_Compiler_FilePath+FILENAME" instead of just "XIncludeFile FILENAME" is a step backward because that's something the compiler can do for us.

By the way, if it's not considered to be a bug I'd say this thread should at least be moved into the feature requests section.

c4s wrote:I just came across the same issue

Did you see topic Working out Include Path issues?

• Fred wrote:It can probably changed to be source relative, yes.

• Fred wrote:Changed for the next version, optimism can pay !

Danilo, thanks for the hint. I overlooked that after all the years (I found a couple of rather old threads) it got fixed - just now when I need it. Great!

I never believed in miracles until now.