G
Guest
gcc provides the libc which have more functions than standard C libraries.
I saw in Windows API similar functions too, with identical parameters!
So, I ask again:
Why not, a committee specifies libraries which are not standard C++ libraries
but *all* compilers include these libraries as part of them?
I mean libraries like socket using, window managment, file system, thread using etc
These libraries with *identical API* in any compiler will be a powerfull tool for any programmer
and then, we can *anything* in C++ which is *cross-platfrom*.
Another concept is the ability to write WEB Applets with C++.
With these libraries I refer above, we can do anything.
For Applets the problem is that C++ Compiler produces natural binary files.
How Java works? Java sucks... Java compile the code to virtual opcodes
and then Virtual Machine converts any virtual opcode to a group of natural opcodes.
This is unacceptable and very bad idea.
A higher-level (than Assembly) Language which is cross-platform must not "converted"
to low-level and after compiled or interpreted.
The better solution is Applet will kept as source code and Virtual Machine compile the
Applet before run it.
However, many people don't want make public their code.
So, A "converter" must exist. This "converter" has this job:
It converts C++ Applet source code to a binary which is almost identical to source code
but comments are removed, classes have changed to simple C functions, spaces are removed
and every reserved word or operator (like for, if, ++, *) is converted to a binary pepresentation.
Now, it is more difficult to steal source code of Applet and compilation-time is shorter.
With this except of Applets you can write stand-alone applications exactly like Java but with C++ speed.
And then, Java will die!...
What is your opinion?
I saw in Windows API similar functions too, with identical parameters!
So, I ask again:
Why not, a committee specifies libraries which are not standard C++ libraries
but *all* compilers include these libraries as part of them?
I mean libraries like socket using, window managment, file system, thread using etc
These libraries with *identical API* in any compiler will be a powerfull tool for any programmer
and then, we can *anything* in C++ which is *cross-platfrom*.
Another concept is the ability to write WEB Applets with C++.
With these libraries I refer above, we can do anything.
For Applets the problem is that C++ Compiler produces natural binary files.
How Java works? Java sucks... Java compile the code to virtual opcodes
and then Virtual Machine converts any virtual opcode to a group of natural opcodes.
This is unacceptable and very bad idea.
A higher-level (than Assembly) Language which is cross-platform must not "converted"
to low-level and after compiled or interpreted.
The better solution is Applet will kept as source code and Virtual Machine compile the
Applet before run it.
However, many people don't want make public their code.
So, A "converter" must exist. This "converter" has this job:
It converts C++ Applet source code to a binary which is almost identical to source code
but comments are removed, classes have changed to simple C functions, spaces are removed
and every reserved word or operator (like for, if, ++, *) is converted to a binary pepresentation.
Now, it is more difficult to steal source code of Applet and compilation-time is shorter.
With this except of Applets you can write stand-alone applications exactly like Java but with C++ speed.
And then, Java will die!...
What is your opinion?