No, what you are showing works despite the way PB implements its includefile statement since it's the simplest, direct way to use it, what discussed here does not work because PB implemented its includefile statement that wayPB wrote: Is that not what we're discussing?

If you follow the thread, my explanation in this and in the links I posted you cannot miss it.
Especially this example cannot be more clear -> http://www.purebasic.fr/english/viewtop ... 24#p367924
The key is PB looks for the file to include not relative to the path of the file containing the include statement, but relative to the path on the MAIN (M A I N) source file, the one you start the compilation from. In your simple case this it not a problem.
In a not trivial case, like the one in the link above, it is.
As I said many times IMO this was a bad design choice, saved only by the fact we have a way around it thanks to that PB constant.