Re: Why 64bit Delphi compiler from Borland may be meaningless!

From: Abdullah Kauchali (non_at_non.com)
Date: 01/24/05 

Date: Mon, 24 Jan 2005 21:29:10 +0200

Nick Hodges [TeamB] wrote:

> You of course have a choice, it's just not necessarily the choice you
> would pick in a world of unlimited choices.

The *real* choice would be a recompile to 64 bit. No or little code
changes and we should be done. That's the alternative that the 64 bit
protagonists are looking for. It's a simple request that seems to be
a victim at the hands of .NET obscurantists here. Moving to .NET, for
many of us, at any rate, is a *re-write* of the applications we have
been slogging on for years. This is the point that you guys seem to be
missing. It's not about .NET is slower, or win32 is more efficient,
it's about investments made in the software developed for *business*.

Claiming that .NET is the only alternative to move on to 64 bit
computing is what I refer to as "being forced". Existing win32 C++
applications (MFC included) can gracefully migrate to win64 with
the new versions of Visual Studio's C++ compilers. That's the type
of alternatives that we're looking for. A few changes, thorough testing
is ok. But a rewrite in .NET is asking too much. As if *Delphi* for
.NET is going to be less painful! It isn't.

> You have alternatives, just not all the alternatives you want.

It's disappointing that you seem unable to understand in simple terms
the issues faced here. By making these unfortunate statements you only
show your lack of sincerity for the concerns of many here. That's sad.

Yes. My alternatives *have been* clear. All our .NET applications are
written with Microsoft's Visual Studio. We investigated Delphi 8 and
decided we wouldn't touch it with a loooooong stick. Visual Studio is
serving us well. If I am given no choice but to rewrite my existing
win32 *Delphi* applications as .NET ones, I will *certainly* be doing
that with Microsoft's toolset too. :(

I hope you understand it in those clear terms.

Relevant Pages

  • Problems with VS2008 SP1 install
    ... So I guess I COMPLETELY uninstall/reinstall Visual Studio now and hope ... Completed Feature Enumeration for product: ... this patch is applicable ... Searching for related applications] ...
    (microsoft.public.vstudio.general)
  • Re: hmm..interesting
    ... resource free to run my applications, not end up with a slow system ... As for the person who claimed Visual Studio the greatest thing ever, ... native C compilers. ...
    (comp.sys.acorn.hardware)
  • Re: Visual C++ versus Visual Basic
    ... Although not everyone will switch .NET applications, ... The CLR (Common Language Runtime) is proposed to exist across multiple ... Now - that doesn't mean not to learn MFC: it exist in Visual Studio ...
    (microsoft.public.vc.mfc)
  • Re: Error: (Type initializer threw an exception)
    ... In my idea you have a failure in either running your program in the new Visual Studio or either running your programm in Vista. ... Vista and VB 2008 + Framework 3.5, but while testing our applications the ... 1 app and 3 class libraries which are ...
    (microsoft.public.dotnet.languages.vb)
  • Re: Which future for WINDOWSFORMS ?
    ... Visual Studio with WindowsForms ... Win API, MFC, ATL, .NET WinForms to name a few. ... why do you assume that you will have to rewrite your ... After almost 10 years, these applications work just fine and while I *could* rewrite them in .NET C++/CLI Winforms, I have no reason, or need, to do so. ...
    (microsoft.public.dotnet.general)