AW: AW: AW: Converting C/C++ DLL to Delphi

I stand correct about mixing up languages and development tools from M$ ;-)

But in my cases, most of the C/C++ code is done with M$ Visual Studio...
And most companies I know do C code with Visual Studio...

It's like mixing up Operating Systems with M$ Windows. Have you got an alternative
If you want "smooth" desktop operation? (Surely some Linux guys go out of the box now hehe ;-)

But that represents only my personal opinion and situation ;-)

There are allways solutions for problems which you describe.
The only thing one allways should keep in mind is: can you "maintain and support" this code
For long times? I asked myself this question in certain  M$VC and BORDELPHI combinations, and
Had to say "nope". So I had to change my basic thinking. I was a REAL delphi minded guy until
I came across such stuff. And it made me think about my strategies a LOT!

Which does not mean I don't do Delphi Coding anymore. For many things it's my first choice over all ;-)
But I consider .net as a serious "concurrent" for the future Delphi development@Borland. 
It starts with pricing of the Produkts and ends up with the question
"why do I need a Vcl.Net if I have already a Windows.Net class library" ;-)

But I'm getting off-topic here... Sorry...


-----Ursprüngliche Nachricht-----
Von: [email protected] [mailto:[email protected]] 
Gesendet: Samstag, 11. September 2004 16:31
An: [email protected]
Betreff: Re: AW: AW: [Delphi-JEDI] Converting C/C++ DLL to Delphi


> Ok I get the point.
> But do you like the idea of it? I certainly don't ;-)

Nope. This is why FPC has a {$packrecords C} to turn on such alignment, since it is quite common.

I'm not to deep into BCB<->Delphi interoperability, but I assume one can fix that there too. I just don't know about it, and the manual way always work.
 
> In my view, this is one reason not to combine Delphi and C code for 
> exchanging data between DLL's
> 
> I changed from Delphi to C#(.net), and I don't regret it.

I think it is much to early to seriously consider .NET, regardless of language Anyway, I work multiplatform, so then .NET is not a serious option (yet). 

Specially with the delay of Longhorn/Avalon, I postpone .NET even further. I _don't want to rewrite my apps again_ then.

> Especially in calling C++ dll's.

One can call C++ dlls from Delphi afaik, just not MSVC dlls. Keep languages and implementations apart.
- So Microsoft compilers work with other Microsoft compilers
- Borland with Borland,
- Free Pascal with GNU.

etc

(Kylix also works with GNU afaik, don't know if that trickled into D6/D7)



------------------------ Yahoo! Groups Sponsor --------------------~-->
$9.95 domain names from Yahoo!. Register anything.
http://us.click.yahoo.com/J8kdrA/y20IAA/yQLSAA/i7folB/TM
--------------------------------------------------------------------~-> 

 
Yahoo! Groups Links



 










------------------------ Yahoo! Groups Sponsor --------------------~--> 
$9.95 domain names from Yahoo!. Register anything.
http://us.click.yahoo.com/J8kdrA/y20IAA/yQLSAA/i7folB/TM
--------------------------------------------------------------------~-> 

 
Yahoo! Groups Links

<*> To visit your group on the web, go to:
    http://groups.yahoo.com/group/Delphi-JEDI/

<*> To unsubscribe from this group, send an email to:
    [email protected]

<*> Your use of Yahoo! Groups is subject to:
    http://docs.yahoo.com/info/terms/