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

"Beeing a real delphi guy" is something which one cannot put in question.
One never asked me what kind of projects I have been working on for the last
10 years, and what changed in the last 2 years of my professional career.
So back off.

As I again have to notice, if some people get some other thougts or some questions
About the way they are thinking, they have to get personal. It's a pitty, but
A wellknown syndrom for me as a programmer. I Think I better unlink this group,
Because I thought it can be used to exchange thoughts.

Somehow I don't like this reaktion ;-)

As I said, we are going way out of topic here...
 

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

> But in my cases, most of the C/C++ code is done with M$ Visual Studio...

Note that what I said goes for C++ code. C code should be possible.

> And most companies I know do C code with Visual Studio...

C++ probably.

> 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 ;-)

- Mac always was smooter than Windows.
- And indeed *nix in general is quite smooth nowadays. But IMHO smooth is overrated anyway. Windows
	is much too "integrated" and that causes most of its problems. If *nix follows that, it will
	get the same problems.

> There are allways solutions for problems which you describe.

Yes. But changing everything (platform, managed vs unmanaged, vendor etc) because you have a minor alignment problem is quite drastic. Typically these things only take a minimal effort to adapt too, and don't really affect productivity.

> The only thing one allways should keep in mind is: can you "maintain 
> and support" this code For long times?

Of course I can. I never was able to be somewhat productive in VS6, and it is way too early for .NET, either Borlands version or M$'s. Being an early adopter only pays off if you are in situation that people pay you (way
extra) to use .NET now. IOW that you are paid (or your main product is) to make early .NET apps.

> I asked myself this question in certain  M$VC and BORDELPHI 
> combinations, and Had to say "nope".

There is no alternative yet.

> 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!

It's strange to be a real Delphi guy (or any compiled language for that matter), and never run into alignment issues. The problems are as old as computers pretty much :-)

> 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" ;-)

I would use neither. Both are either going to disappear, or mutate a lot in the coming years (Longhorn,Avalon).
 


------------------------ 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/