the project sounds cool; but i think (i might be wrong, i only looked at 2 or 3 sources) you should also make use of C++ features (i always missed the conversion operators in Java). FOr instance, Class.toString should have a C++ counterpart like operator String& (). (which will in its turn call toString() so that when you concatenate an Object with a string you get the Object's toString result). One more thing, should not all the methods be virtual ? I am pretty sure Java only uses virtuals.
oh, and one more thing (for the wishlist :): a regexp search method in String pretty-pretty please !!!!
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
yes, the source i loaded over the net is preliminery, it is just
kind of warm-up for this project. Since the library is so large, it is easier to write one by one. We can not finish thing all at a time.. :) I believe the object model need to make a little correction. in java, it does have virtual, it called abstract, however, java can not do multiple inheritance but c++ can, so we should definitely utilitze this feature, by the way, we may just converting jakelib as the way that we wish them to work and moreover, we hope to implement AWT component using GLUT, maybe some wraper class. however, it is open to discussion......
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
When you state that Java cannot do multiple inheritance, I think you misunderstand. The multiple inheritance that java has comes from both class implementation and interface definitions. Therefore, if you extend a class you can then also implement multiple interfaces, allowing for strong typing of objects as well as allowing the ability for usable inheritance trees. The difficulty is that to design a inheritance tree, you would need to stick to the java standard to make it java like, but c++ has so much to offer, specifically with operator overloading and such, that these might also be helpful. Why not include this capability of c++ into this library as well as provide the ability to use Java like commands, such as extends, implements. And what about synchronized, this would be cool if you could design a piece that could implement different thread/process handlers such as mutexes or semaphores. It seems that this project has too many 'features', like trying to extend to a gui, before the core is complete. Maybe we should consider core completeness before extending our library to items that need the core.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
the project sounds cool; but i think (i might be wrong, i only looked at 2 or 3 sources) you should also make use of C++ features (i always missed the conversion operators in Java). FOr instance, Class.toString should have a C++ counterpart like operator String& (). (which will in its turn call toString() so that when you concatenate an Object with a string you get the Object's toString result). One more thing, should not all the methods be virtual ? I am pretty sure Java only uses virtuals.
oh, and one more thing (for the wishlist :): a regexp search method in String pretty-pretty please !!!!
yes, the source i loaded over the net is preliminery, it is just
kind of warm-up for this project. Since the library is so large, it is easier to write one by one. We can not finish thing all at a time.. :) I believe the object model need to make a little correction. in java, it does have virtual, it called abstract, however, java can not do multiple inheritance but c++ can, so we should definitely utilitze this feature, by the way, we may just converting jakelib as the way that we wish them to work and moreover, we hope to implement AWT component using GLUT, maybe some wraper class. however, it is open to discussion......
When you state that Java cannot do multiple inheritance, I think you misunderstand. The multiple inheritance that java has comes from both class implementation and interface definitions. Therefore, if you extend a class you can then also implement multiple interfaces, allowing for strong typing of objects as well as allowing the ability for usable inheritance trees. The difficulty is that to design a inheritance tree, you would need to stick to the java standard to make it java like, but c++ has so much to offer, specifically with operator overloading and such, that these might also be helpful. Why not include this capability of c++ into this library as well as provide the ability to use Java like commands, such as extends, implements. And what about synchronized, this would be cool if you could design a piece that could implement different thread/process handlers such as mutexes or semaphores. It seems that this project has too many 'features', like trying to extend to a gui, before the core is complete. Maybe we should consider core completeness before extending our library to items that need the core.