Re: [fpc-devel] VMT compatibility

2005-01-30 Thread Alexey Barkovoy
- Original Message - From: "Michael Van Canneyt" <[EMAIL PROTECTED]> Delphi is compatible at least with Borland C++ and MS VC++. And taking in accout how COM intefaces are implemented in C++ (I'm supposing here all C++ compilers support the same syntax) - each C++ compiler supporting MS

Re: [fpc-devel] VMT compatibility

2005-01-30 Thread Florian Klaempfl
Alexey Barkovoy wrote: - Original Message - From: "Michael Van Canneyt" <[EMAIL PROTECTED]> Delphi is compatible at least with Borland C++ and MS VC++. And taking in accout how COM intefaces are implemented in C++ (I'm supposing here all C++ compilers support the same syntax) - each C++

Re: [fpc-devel] VMT compatibility

2005-01-30 Thread Alexey Barkovoy
- Original Message - From: "Florian Klaempfl" <[EMAIL PROTECTED]> For example "DECLARE_INTERFACE_(IClassFactory, IUnknown)" in C++ is expanded to "struct FAR IClassFactory : public IUnknown", so really public parts of VMT (with positive offset) are always [should be] compatible. Surely

Re: [fpc-devel] VMT compatibility

2005-01-30 Thread Marco van de Voort
> // Call C++ function and pass to it our "special" interface > Result := D3DXLoadMeshHierarchyFromX_FPC_{$}(Filename, MeshOptions, > pD3DDevice, AllocI, pUserDataLoader, ppFrameHierarchy, ppAnimController); > > Dec(PInteger(AllocI)^, $C); // Patch interface VMT - BACK > end; > > But I rea

Re: [fpc-devel] VMT compatibility

2005-01-30 Thread Michael Van Canneyt
On Sun, 30 Jan 2005, Alexey Barkovoy wrote: > - Original Message - > From: "Florian Klaempfl" <[EMAIL PROTECTED]> > > >> For example "DECLARE_INTERFACE_(IClassFactory, IUnknown)" in C++ is > >> expanded > >> to "struct FAR IClassFactory : public IUnknown", so really public parts of > >>

Re: [fpc-devel] Re: File Dates

2005-01-30 Thread Michael Van Canneyt
On Sat, 29 Jan 2005, Jeff Pohlmeyer wrote: > > > AFAIR Unix has some kind of registry for file types, based on file > > extensions and characteristic bytes at the begin of an file. Does > > somebody know more about that registry, so that it could be integrated > > into the intended registry for

Re: [fpc-devel] File Dates

2005-01-30 Thread Michael Van Canneyt
On Sun, 30 Jan 2005, DrDiettrich wrote: > Michael Van Canneyt wrote: > > > > FPC defines 1900-1-1 as the start date, whereas Delphi defines > > > 1899-12-30 as the start date - note: neither 1900 nor dec. 31! > > > This requires different constants for converting a Unix date into > > > TDateTime

Re: [fpc-devel] VMT compatibility

2005-01-30 Thread Alexey Barkovoy
Delphi and FreePascal simplest interfaces already includes IUnknown. So using raw interfaces is incompatible here too. No. You could try to use CORBA interfaces, they don't have IInterface (or IUnknown) as the parent. There is a compiler switch for this. Thanks, I'll look at it. Seems really bette

Re: [fpc-devel] VMT compatibility

2005-01-30 Thread Michael Van Canneyt
On Sun, 30 Jan 2005, Marco van de Voort wrote: > > // Call C++ function and pass to it our "special" interface > > Result := D3DXLoadMeshHierarchyFromX_FPC_{$}(Filename, MeshOptions, > > pD3DDevice, AllocI, pUserDataLoader, ppFrameHierarchy, ppAnimController); > > > > Dec(PInteger(AllocI)^

[fpc-devel] Re: File Dates

2005-01-30 Thread Jeff Pohlmeyer
> > unit libmagic; > Can we include this in the FPC packages ? I think it would be useful. > Michael. It's okay with me, I'm always glad to contribute what I can to FPC. - Jeff . __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam

Re: [fpc-devel] Re: File Dates

2005-01-30 Thread Michael Van Canneyt
On Sun, 30 Jan 2005, Jeff Pohlmeyer wrote: > > > unit libmagic; > > > Can we include this in the FPC packages ? I think it would be useful. > > Michael. > > It's okay with me, I'm always glad to contribute what I can to FPC. > - Jeff Thank you. I'll add dynamical loading of the libmagic librar