|
From: John P. <jo...@ma...> - 2000-10-19 01:38:24
|
Scratch that. I get it now. A few items:
Do you think that parameter constructors are necisary? I always viewed them
as convinence and they do dirty up the code a bit with the macros. Also you
are stuck with being able to construct parameterized constructors only if you
have a macro that matches the number of parameters. I have a sever dislike
of macros ever since I tried to program for windows and wondered why they
didn't just go the ANSI way.
The Info class is a nice way to abstract things. I quite liked it after I
understood it. It can be expanded in the future for use with dynamic
interfaces. I still think it can be automated.
BasicPluginInterface should be a pure virtual class with no implementation in
it. Kinda confused me when an interface has actual code in it.
Also I belive the SOME_EXPORT macro can consume the extern "C" directive so
that is no longer a worry of the developers.
John Palmieri wrote:
> 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
>
> _______________________________________________
> somelib-devel mailing list
> som...@li...
> http://lists.sourceforge.net/mailman/listinfo/somelib-devel
|