OS/2, eCS & ArcaOS - Technical > Programming

VSQM.H - errror due to comment?

(1/1)

Dariusz Piatkowski:
Looking at this header file and found the following:


--- Code: ---...
/**********************************************************************/
/*                                                                    */
/* String table IDs                                                   */
/*                                                                    */
/**********************************************************************/
#define IDSNAME          10
#define IDSTITLE         20
#define IDSHELP          21    /* Help window title string
#define IDSDTLSTL        30
#define IDSQUEUE1        40
...

--- End code ---

It would appear to me that the "/* Help window title string" has an un-ended comment which actually causes all teh remaining #define's to be commented out as well.

This carries on for about 40 line of code until the following:


--- Code: ---...
#define VQINTERNALERROR  82
#define VQDRIVENOTREADY  83
#define VQBADPRIOSTR     84

#define ID_LISTBOX       90     /* Queues listbox ID

/**********************************************************************/
/*                                                                    */
/* Menu IDs                                                           */
/*                                                                    */
/**********************************************************************/

--- End code ---

...which despite being an un-ended comment is OK since the "/* Queues listbox IS" is followed by multi-line comment anyways which correctly ends the full comment section.

Does anyone know if this is correct? Or is this an un-documented but otherwise intentional exclusion of all these DEFINEs?

Dariusz Piatkowski:
Heck...further on I find the following:


--- Code: ---#define IDH_IDMRLSALL   :ç 421

--- End code ---

That ":ç" doesn't look right to me...but is that supposed to be some kind of double-byte code character with a special meaning?

Dave Yeo:
Looks to me like typos. Probably should open an issue at Bitwise as I believe they're looking after the toolkit.
Seems no one has used the header, which I assume is for the print spool, as even the copy in the 2.1 toolkit has the same issues.

Navigation

[0] Message Index

Go to full version