The header file usbdi.h has the C++ reserved word ‘class’ on line 170 within
the definition of ‘usbd_device_ident’. This therefore makes it impossible to
write a USB device driver application using C++ as it won’t compile:(
Are there any fundamental reasons (other than the above) why I should not be
able to use C++? My driver application is stand-alone and does not use any
other standard system interfaces e.g.resource manager.
Jim Douglas
What am I to infer from the fact that no-one has replied to this post…
a) Nobody but me reads this newsgroup anymore
b) Someone in QSSL has posted an internal bug report, but doesn’t want to
admit the mistake
c) I should give up QNX programming and turn to Visual Basic instead.
d) A C++ friendly version of the DDK is ready for imminent release
Jim Douglas
“Jim Douglas” <jim@dramatec.co.uk> wrote in message
news:9702sh$fug$1@nntp.qnx.com…
The header file usbdi.h has the C++ reserved word ‘class’ on line 170
within
the definition of ‘usbd_device_ident’. This therefore makes it impossible
to
write a USB device driver application using C++ as it won’t compile:(Are there any fundamental reasons (other than the above) why I should not
be
able to use C++? My driver application is stand-alone and does not use any
other standard system interfaces e.g.resource manager.Jim Douglas
“Jim Douglas” <jim@dramatec.co.uk> wrote in message
news:97tdr4$1to$1@nntp.qnx.com…
What am I to infer from the fact that no-one has replied to this post…
a) Nobody but me reads this newsgroup anymore
b) Someone in QSSL has posted an internal bug report, but doesn’t want to
admit the mistake
c) I should give up QNX programming and turn to Visual Basic instead.
d) A C++ friendly version of the DDK is ready for imminent release
e) Somebody assumed that you could do a global search and replace
of “class” to “klass” in the relevant header, and they are doing the same
at QSSL, hopefully to be released in the next beta.
Actually, c) is not such a bad option. My experience has been that
Visual Basic exhibits almost identical real-time behaviour to both QNX4
and QNX6.
Cheers,
Andrew
Many thanks. I wasn’t sure about changing the header. I didn’t know if it
would effect anything else if I messed around with it.
Jim
“Andrew Thomas” <andrew.nospam@cogent.ca> wrote in message
news:97t12i$364$1@inn.qnx.com…
“Jim Douglas” <> jim@dramatec.co.uk> > wrote in message
news:97tdr4$1to$> 1@nntp.qnx.com> …
What am I to infer from the fact that no-one has replied to this post…a) Nobody but me reads this newsgroup anymore
b) Someone in QSSL has posted an internal bug report, but doesn’t want
to
admit the mistake
c) I should give up QNX programming and turn to Visual Basic instead.
d) A C++ friendly version of the DDK is ready for imminent releasee) Somebody assumed that you could do a global search and replace
of “class” to “klass” in the relevant header, and they are doing the
same
at QSSL, hopefully to be released in the next beta.Actually, c) is not such a bad option. My experience has been that
Visual Basic exhibits almost identical real-time behaviour to both QNX4
and QNX6. >Cheers,
Andrew
Jim Douglas <jim@dramatec.co.uk> wrote:
The header file usbdi.h has the C++ reserved word ‘class’ on line 170 within
the definition of ‘usbd_device_ident’. This therefore makes it impossible to
write a USB device driver application using C++ as it won’t compile:(
QA is in the process of testing/building a new archive that fixes the above
problem.
Are there any fundamental reasons (other than the above) why I should not be
able to use C++? My driver application is stand-alone and does not use any
other standard system interfaces e.g.resource manager.
I can’t think of any reasons why it wouldn’t work.