Kind of an odd ?bug?

[Michael Mattias]

Path$ is a keyword for the EXE read only user defined type, EXE.Path$. You may freely use Path$ in your source.....

So "Path$" is truly only a keyword worthy of highlighting when it appears as part of "EXE.Path$"

????

This sounds like a little thing, but let me tell you, words suddenly being hilighted in my "keyword color of choice" tend to make me a little nervous. It's REALLY kind of hairy when I am migrating from a prior version of the compiler and some of my variables now appear to be "keywords".... except when they aren't. e.g "path$"

MCM

[Mel Bishop]

Boy, support is fast responding

Here's their "official" response:

Hi Mel,

Path$ is a keyword for the EXE read only user defined type, EXE.Path$. You may freely use Path$ in your source, but the IDE will highlight it as a keyword.

Sincerely,
Jeff Daniels
PowerBASIC Staff

[Steve Rossell]

It is a keyword for EXE.Path$.

[Paul Dixon]

Mel,
PATH is used as a key word in the PATHNAME$ function:
http://www.powerbasic.com/support/help/pbcc/pathname$_function.htm

Paul.

[Mel Bishop]

Re: CC501

If I need to store the path of a file in a string, I use "path$" in the program.

The odd thing is that the word "path$" auto-caps like it's a reserved word. I bring up the help file and all it shows is "PATHNAME$" and "PATHSCAN$".

Using PATH$ by itself seems to work as advertised (for my exclusive use) and doesn't seem to present a problem. The program compiles and runs okay with (mostly) expected results.

Any comments? Should I use it or not? Why does it auto-cap?

I'm going to send this to support and see what they say.