From: John P. <jo...@ma...> - 2000-10-19 01:10:20
|
Sounds good. I'll look at it tomorow. I just made some major breakthroughs in my other project and I will be integrating SOMELib soon. One thought on the Info classes. Can you show me how these work. I don't quite follow the code. Say I have a class such as: class Sprite { public: Sprite(); Sprite( string fileName ); ~Sprite(); void render( int x, int y ); bool load( string fileName ); private: string _fileName; char *rawGraphics; }; How would I convert this into a SOMEObj? and say I normaly use it like this: main(){ . . . Sprite sp = new Sprite("tux.png"); sp->render(100,100); . . . } How would I convert this for use with SOMELib? You see I want to keep the syntax generaly the same with a few extras but not so much that it becomes as complicated as COM or Corba. If that ever happend then we are beyond the scope of our project. If extras like the Info class are absolutly needed then perhaps we can rig a pre-parser to handle all the gorry details of setting up the vectors. Well just a thought. -John Palmieri Thomas Matelich wrote: > I made some of the changes we talked about. I have not added the > ability to get a SOMEObj directly from the factory yet (kind of dragging > my heels on that one because I just don't like it). John, if you could > fix up the configure stuff when you get a chance. I noticed that I was > linking BasicTestLib to TestApp which is silly. But because I did that, > I had to make libSOME into an SO, because TestApp wasn't pulling in all > the symbols necessary. > > How would we go about making configure automatically set up our choice > of dll access? > > -- > Thomas O Matelich > Senior Software Designer > Zetec, Inc. > sos...@us... > tma...@ze... > > _______________________________________________ > somelib-devel mailing list > som...@li... > http://lists.sourceforge.net/mailman/listinfo/somelib-devel |