RESERVED WORDS -314 of them

[Rodney Hicks]

Attached is a partial list of Reserved words for PBWin 9. This list is not supplied by PowerBASIC, Inc. nor is it complete. It is merely most words from a dictionary that will highlight in the IDE.
MARK (???)

Posting it in case someone else has a use for it.

[Laurence Jackson]

Interesting exercise. You found 12 words missing from my lists, including four I can find no current use of:

ATTRIB
BEGIN
HIDDEN
MARK

to those, you can add:

DISPPARAMS

[Rodney Hicks]

BEGIN applies to PBForms metastatements.

#PBFORMS CREATED

#PBFORMS BEGIN INCLUDES

ATTRIB not sure about this one. I seem to recall it, but I can't place where.

HIDDEN shows up in the INTERFACE/END INTERFACE Block

MARK does show up as a paritytype in the COMM SET statement but the conventions used don't imply that it's a reserved word.

[Michael Mattias]

ATTRIB is in the (8.03) help index, but it points to GETATTR.

Let me check an older help file...nah, same thing in PB/DLL 6.0, ATTRIB in help index pointing to GETATTR.

Found it... PB/DOS help file

 ATTRIB function
 ───────────────
 Purpose: Returns the DOS attribute of a file.

 Syntax:  x = ATTRIB(filename$)

That must be why it sounds familiar.

MCM

[Rodney Hicks]

Michael
That's it!
I never moved the two feet necessary to grab the PBDOS manual to check there, just checked PBWin 8.04 and 9.0.
Does this mean it's included for backwards compatibility?

[Michael Mattias]

>Does this mean it's included for backwards compatibility?

If ATTRIB returns the attribute, it's compatible, so I guess so.

If ATTRIB returns a compile error, it's not compatible, so I guess not.

MCM

[Laurence Jackson]

q = ATTRIB("Tester.bas")
MSGBOX FORMAT$(q)

works in PB/Win9!

Strange that "BEGIN" is reserved and "CREATED" and "INCLUDES" aren't.

[Laurence Jackson]

Just done some more tests in PB/Win9 ...

"BEGIN", "HIDDEN" and "MARK" are not really reserved - the IDE just marks them as such (they can be used as variable names).

DISPPARAMS is a built-in UDT, but you'll have to go back to the PB/Win8 help to find any reference to it - in "Previous changes (PB/Win 7.0 release)".

[StanHelton]

...
"BEGIN", "HIDDEN" and "MARK" are not really reserved - the IDE just marks them as such (they can be used as variable names)....

Does this mean they work like CLASS did in 8.04? Marked but still usable?

Might not be a good idea to actually use them as variables, then.

I think I'll prepend a type id if I find a reason to use one of these.

Stan

[Cliff Nichols]

DISPPARAMS is a built-in UDT, but you'll have to go back to the PB/Win8 help to find any reference to it - in "Previous changes (PB/Win 7.0 release)".

WHERE??????
I looked through the docs, and even checked the Win32Api.inc itself....I see nothing about DISPPARAMS, or what it does....

I have found some in search, but not sure what it is/does just yet, so hoping its what I am looking for, but dunno

[Laurence Jackson]

WHERE??????

Platform SDK - Automation - Passing Parameters

Arguments to the method or property being invoked are passed in the DISPPARAMS structure. This structure consists of a pointer to an array of arguments represented as variants, a pointer to an array of DISPIDs for named arguments, and the number of arguments in each array.

PB/Win 8 help file - Previous changes (PB/Win 7.0 release)

IDISPATCH, IUNKNOWN, and DISPPARAMS are now reserved keywords, to avoid potential conflict with the Windows and PowerBASIC COM subsystems. DISPPARAMS is an intrinsic structure (UDT) that has the following internal definition:

TYPE DispParams
  VariantArgs AS VARIANT PTR
  NamedDispId AS LONG PTR
  CountArgs AS DWORD
  CountNamed AS DWORD
END TYPE