#include <iostream> #include <memory.h> using namespace std; int main(void) {
int c;
cin >> c;
char array[c];
memset(array,0,sizeof(array));
cout << "sizeof(array) is " << sizeof(array) << endl; }
That compiles and runs on Linux and QNX and cygwin without any warnings or errors. Care to post another example of where g++ is "busted" on QNX? Please be sure to test it on other platforms first.
You can get a used iPaq (36xx/37xx/38xx) on eBay very cheap, and you can have a good time hacking on it with QNX, Linux, Plan9, etc. It's a good and cheap ARM development platform.
Not everyone develops for an OS under that OS. So we have cross development tools for targetting hardware running QNX that run under Solaris, Windows and Linux.
Actually, QNX is a hard realtime system. Upper bounds are fixed and QNX is in fact used in many medical devices because of this behavior. Linux is a soft realtime system, since it can provide good response times but the upper bound is unlimited so it cannot assure those times when placed under load. The only real solution to this today is RTLinux.
The paper in the first link is very weak on details, not surprising for a 300 level undergraduate course.
Re:I don't get the attraction
on
QNX 6.3 Released
·
· Score: 4, Informative
QNX isn't a Linux clone. QNX is a POSIX based OS that has a history that goes back a decade before Linux was even a glimmer in Linus's eye.
There is nothing given away for "free" either, there is an evaluation that is free - much the same as vmware has a 30 day eval of their product. After that 30 days, Neutrino will fall back into a more limited mode but will remain operational (like it was with NC before 6.3.0).
Re:QNX is the bad touch
on
QNX 6.3 Released
·
· Score: 2, Informative
QNX 2.x? There was no GNU toolchain for QNX 2.x, so I strongly doubt you are using it.
QNX isn't Linux, our default/bin/sh is ksh not bash, although you can just fire up qnxinstall and go to the QNX Online repository and install bash. All my x86 workstation machines have bash installed with no trouble at all.
It would have been more informative if you had actually said what was broken with g++ rather then saying it was just broken. The only thing that is different from our 2.95.3 g++ vs. say Linux or BSD is that we have exceptions turned OFF by default instead of turned on. So you have to give the command line option for them to be enabled - "-fexceptions" I belive.
NC Download Changes
on
QNX 6.3 Released
·
· Score: 5, Informative
With 6.3.0 the download version of QNX will actually be our full commerical product, with downloads avaliable for both Windows, Solaris, Linux and Neutrino. After 30 days, these PE (pro edition) versions will turn into what was once the NC edition with the pro features disabled.
I suspect the downloads will be up and ready very soon. You can find more details here:
Actually, QNX just allows you to mmap() in anything from userspace (without a direct device fd) and hook interrupts from user space, etc. A requirement when you move everything out of the kernel and into processes.
You actually don't have to rebuild anything but you do need to test it on all platforms. However, there are more then three UI toolkits:
Win32
GTK2
Motif
MacOS (not sure which API)
Photon
Different bugs on different OSes using these UI toolkits not withstanding, you can probably get away with testing on Win2K, Linux, MacOS X and QNX6. However, for true testing of Motif you should probably give Solaris a whirl as well.
Actually, very VERY little of SWT on any given platform is written in C. The vast majority is all written in Java. The nice part is that all the code (java and C) is under the CPL so there are no big sticky license issues like with Swing.
Actually, you are wrong. IBM has two jvm's. They have the Hursley JVM which is a port/licensed jvm based on Sun's source base. However, IBM also own's OTI and OTI has j9, which is a totally clean-room jvm that recently got full certification. So IBM does in fact have it's own JVM.
You are right, nothing that you download with Eclipse nor part of the org.eclipse classes. However, there are many projects on the go adding in language support for other languages like C#, Ruby, Eiffel, etc.
The C/C++ is actually quite an active project with many companies (QNX, Rational, RedHat) participating to make a top-tier C/C++ IDE environment.
Most of these languages are also supported (or in the process of being supported) in Eclipse. Which is open-source and cross platform and easy to extend.
Perhaps if you wanted to claim *Apache* has a large market share that would be okay. But, just so you know, Apahce != Linux. In fact, these days, Apache != UNIX! It runs great on Windows and OS/2. Oh, and OpenSource != Linux either, depsite what the uninformed may think. This sort of thinking is no better then people who think that PC == Microsoft.
Years now? Sounds like you are used to using QNX4. And under QNX4 I think you are correct that it is just non-standard enough (mostly due to the use of watcom instead of gcc) to make porting a pain. However, QNX6 is a major step forward from QNX4 and most of your issues are no longer a factor. Just FYI - might be waste since you are just an AC.:)
Check out get.qnx.com.
It is a full download of the QNX6 Realtime Platform that you can try out. Full desktop system. It is pretty nice if you don't need to run Word.;)
QNX on the iPaq will be free for personal use, QNX is a POSIX based OS (from the outset, so things like threads are not a hack onto the side of a UNIX kernel), and, to top it all off, it runs really well on the iPaq.:)
Eeeek! I just implied that QNX was a monolithic kernel - it isn't. It is a micro-kernel where the OS only provides a limitied set of features that enable all the rest of the system to be built. ACK!
First of all - those numbers are for QNX4 (our previous generation kernel, x86 only). The iPaq is running QNX6. And we do have numbers - I am not sure if they are posted on our website yet or not but they are going to be made with each and every release. And yet another thing - QNX isn't your average monolithic kernel. There is no "kernel" mode for timings that mean anything. Everything is based on a message passing infustructure (from device drivers to networking to filesystems to the GUI).
There is an application running called ipaq_input. It takes care of resizing apps and coming forward when they need/want input (handwriting, keyboard, etc). You can see from the screen shots that it is forward when the URL area is in focus and the terminal always requets to have the input area present.
Yes you can! I do "cd/proc/boot" all the time and you can also do a "cd/proc/self", or, in C code , open( "/proc/self/as", O_RDWR ), to get access to information on yourself.
I doubt these are faked considering the fact that there is a directory named after the internal 3COM name of the project.:) I guess he could have worked @ QNX or 3COM and been smart enough to add that in - but I doubt it.:)
Very easy,/proc on QNX Neutrino is not like/proc on Linux. In fact, on Neutrino the size of/proc is actually the amount of free physical memory in the system (looks like a little over 8M). And the shots are very "real" looking to me, install QNX somtime and checkout the normal terminal. And since the Audrey's look-n-feel is done via a UI plugin it is totally possible to get a window that looks like a normal QNX/Photon terminal.
Slashdot Mirror
You can get a used iPaq (36xx/37xx/38xx) on eBay very cheap, and you can have a good time hacking on it with QNX, Linux, Plan9, etc. It's a good and cheap ARM development platform.
Not everyone develops for an OS under that OS. So we have cross development tools for targetting hardware running QNX that run under Solaris, Windows and Linux.
Actually, QNX is a hard realtime system. Upper bounds are fixed and QNX is in fact used in many medical devices because of this behavior. Linux is a soft realtime system, since it can provide good response times but the upper bound is unlimited so it cannot assure those times when placed under load. The only real solution to this today is RTLinux.
The paper in the first link is very weak on details, not surprising for a 300 level undergraduate course.
QNX isn't a Linux clone. QNX is a POSIX based OS that has a history that goes back a decade before Linux was even a glimmer in Linus's eye.
There is nothing given away for "free" either, there is an evaluation that is free - much the same as vmware has a 30 day eval of their product. After that 30 days, Neutrino will fall back into a more limited mode but will remain operational (like it was with NC before 6.3.0).
www.qnx.com
www.qnxzone.com
www.openqnx.com
Some reading to bring you up to speed on things.
QNX 2.x? There was no GNU toolchain for QNX 2.x, so I strongly doubt you are using it.
/bin/sh is ksh not bash, although you can just fire up qnxinstall and go to the QNX Online repository and install bash. All my x86 workstation machines have bash installed with no trouble at all.
QNX isn't Linux, our default
It would have been more informative if you had actually said what was broken with g++ rather then saying it was just broken. The only thing that is different from our 2.95.3 g++ vs. say Linux or BSD is that we have exceptions turned OFF by default instead of turned on. So you have to give the command line option for them to be enabled - "-fexceptions" I belive.
With 6.3.0 the download version of QNX will actually be our full commerical product, with downloads avaliable for both Windows, Solaris, Linux and Neutrino. After 30 days, these PE (pro edition) versions will turn into what was once the NC edition with the pro features disabled.
I suspect the downloads will be up and ready very soon. You can find more details here:
http://www.qnxzone.com/
QNX Momentics is our development toolset - it exists on Windows, Solaris and Neutrino. The "desktop" OS is actually QNX Neutrino.
Actually, QNX just allows you to mmap() in anything from userspace (without a direct device fd) and hook interrupts from user space, etc. A requirement when you move everything out of the kernel and into processes.
Nope, QNX does not run in a flat memory mode. It is a fully memory protected, SMP, realtime microkernel.
- Win32
- GTK2
- Motif
- MacOS (not sure which API)
- Photon
Different bugs on different OSes using these UI toolkits not withstanding, you can probably get away with testing on Win2K, Linux, MacOS X and QNX6. However, for true testing of Motif you should probably give Solaris a whirl as well.Just for some eye candy - here is Eclipse running on QNX with the CDT:
http://qnx.wox.org/qnx/screenshots/ide2/
Actually, very VERY little of SWT on any given platform is written in C. The vast majority is all written in Java. The nice part is that all the code (java and C) is under the CPL so there are no big sticky license issues like with Swing.
Actually, you are wrong. IBM has two jvm's. They have the Hursley JVM which is a port/licensed jvm based on Sun's source base. However, IBM also own's OTI and OTI has j9, which is a totally clean-room jvm that recently got full certification. So IBM does in fact have it's own JVM.
You are right, nothing that you download with Eclipse nor part of the org.eclipse classes. However, there are many projects on the go adding in language support for other languages like C#, Ruby, Eiffel, etc.
The C/C++ is actually quite an active project with many companies (QNX, Rational, RedHat) participating to make a top-tier C/C++ IDE environment.
Most of these languages are also supported (or in the process of being supported) in Eclipse. Which is open-source and cross platform and easy to extend.
Perhaps if you wanted to claim *Apache* has a large market share that would be okay. But, just so you know, Apahce != Linux. In fact, these days, Apache != UNIX! It runs great on Windows and OS/2. Oh, and OpenSource != Linux either, depsite what the uninformed may think. This sort of thinking is no better then people who think that PC == Microsoft.
Years now? Sounds like you are used to using QNX4. And under QNX4 I think you are correct that it is just non-standard enough (mostly due to the use of watcom instead of gcc) to make porting a pain. However, QNX6 is a major step forward from QNX4 and most of your issues are no longer a factor. Just FYI - might be waste since you are just an AC. :)
Check out get.qnx.com. ;)
It is a full download of the QNX6 Realtime Platform that you can try out. Full desktop system. It is pretty nice if you don't need to run Word.
QNX on the iPaq will be free for personal use, QNX is a POSIX based OS (from the outset, so things like threads are not a hack onto the side of a UNIX kernel), and, to top it all off, it runs really well on the iPaq. :)
Eeeek! I just implied that QNX was a monolithic kernel - it isn't. It is a micro-kernel where the OS only provides a limitied set of features that enable all the rest of the system to be built. ACK!
First of all - those numbers are for QNX4 (our previous generation kernel, x86 only). The iPaq is running QNX6. And we do have numbers - I am not sure if they are posted on our website yet or not but they are going to be made with each and every release. And yet another thing - QNX isn't your average monolithic kernel. There is no "kernel" mode for timings that mean anything. Everything is based on a message passing infustructure (from device drivers to networking to filesystems to the GUI).
There is an application running called ipaq_input. It takes care of resizing apps and coming forward when they need/want input (handwriting, keyboard, etc). You can see from the screen shots that it is forward when the URL area is in focus and the terminal always requets to have the input area present.
Yes you can! I do "cd /proc/boot" all the time and you can also do a "cd /proc/self", or, in C code
, open( "/proc/self/as", O_RDWR ),
to get access to information on yourself.
I doubt these are faked considering the fact that there is a directory named after the internal 3COM name of the project. :) I guess he could have worked @ QNX or 3COM and been smart enough to add that in - but I doubt it. :)
Very easy, /proc on QNX Neutrino is not like /proc on Linux. In fact, on Neutrino the size of /proc is actually the amount of free physical memory in the system (looks like a little over 8M). And the shots are very "real" looking to me, install QNX somtime and checkout the normal terminal. And since the Audrey's look-n-feel is done via a UI plugin it is totally possible to get a window that looks like a normal QNX/Photon terminal.