On Mon, Nov 19, 2001 at 10:21:06PM +0200, Arpi wrote:
> Hi,
>
> > > >Hmm. How did you do that? (C++->C)
> > > >I tried it some time ago but finally found it very impossible.
>
> > > Yes, it is. Eugene's comments says "Sh*t. MSVC++ and g++ use different
> > > methods of storing vtables." and manually implements the directshow api
> > > in plain C using pointers to functions. Nice work indeed. ;)
> >
> > Ok I've started to convert C++ -> C in a true way
>
> ehh. does it have any sense of converting c++ -> c _again_?
> i mean you didn't do it before, and now as you got it ready-to use you
> re-do it... or you just fix/cleanup the C version did by Xine guy?
Yes it does for me
Simply it should look consistently - you know - I prefer the 'right' way
to do the things.
Also I do not like to see the use of 'this' C++ reserved keyword in C code.
'This' is different story...
> > which means the library will propler export only two symbols per
> > object Create & Destroy - the rest will be hidden and defined as
> > static and accessible in exactly the same was as is now via pointer
> > dereference...
> we'll see.
Lot of libraries seems to be exproting a lot of 'junk' symbols - this doesn't
mean libwin32 should do that as well.
--
.''`. Which fundamental human right do you want to give up today?
: :' : Debian GNU/Linux maintainer - www.debian.{org,cz}
`. `' Zdenek Kabelac kabi@{debian.org, users.sf.net, fi.muni.cz}
`- Resistance is futile. You all will be packaged
_______________________________________________
Avifile mailing list
[EMAIL PROTECTED]
http://prak.org/mailman/listinfo/avifile