> Allen Bauer wrote:
>
> >
> > So, when you're giving us feedback, rather thant saying, "I need a
> > 64bit compiler, NOW!" saying, "I need to make sure my MS Office
> > extension will work with all versions of the new Office 2010" or "My
> > Explorer shell extension needs to work with all the new 64bit
> > versions of Windows."
> >
> > I hope people understand the distinction. The first one doesn't
> > convey the problem you're trying to solve, nor is it implicitly or
> > explcitly describing how said solution (or lack thereof) would help
> > (or hinder) your business. We love the latter form of feedback, and
> > have real trouble categorizing and quantifying the former.
>
>
> Yes, I understand but the problem is we really need 64-bit compiler
> now. ;o)
There's always that one guy in the crowd ;-)...
> I am quite sure that you already know perfectly well the majority of
> scenarios where 64-bit compiler is a necessity as far as a strictly
> technical point is considered.
>
> However, the other aspect of the situation is uncertainity. Since
> Embarcadero is not willing to make a strong commitment about the
> approximate timeframe when we can expect the new compiler to be here,
> it is really difficult for its customers to decide that it is safe to
> continue investing in Delphi. Also, there is a growing pressure to
> start converting the existing code to something like .Net.
We're certainly working on the 64bit compiler since I regularly see
checkins like this at least once or more a week:
====
27406 trunk/com/ decl.c 8/0 Thu Jan 21 06:05:09 2010 UTC ytagawa
27406 trunk/com/ objout.c 4/0 Thu Jan 21 06:05:09 2010 UTC ytagawa
Log:
[dcc64] initial parOff is 16 for x64 instead of 8 for 32bit.
====
That doesn't mean it is "all-hands-on-deck" for the 64 bit compiler,
that distinction belongs to the Fulcrum (x-plat) project as that is the
closest release. However, please know that we're working to the best of
our ability to ensure we're going to be able to "hit the ground
running" once we're able to shift focus to 64bit. *If* that is the
release immediately after Fulcrum, I cannot comment.
> I think it would be beneficial for everyone if Embarcadero could make
> a commitment that after X-Platform project is completed the next
> priority will be Windows 64-bit suff and not for example support for
> iPone or something else.
Making a commitment like that today doesn't mean that other events down
the line require a change in priorities. Yes, it doesn't mean that
those event will cause a change either, but the crystal ball gets
murkier and murkier as we peer farther into the future.
> I see some people downplaying the immediate need for Delphi/CPP Builde
> Windows 64-bit compilers but if that is true would you be willing to
> advertise Delphi using the slogan like : "Delphi, the worlds best IDE
> to write your 32-bit native applications." ?
I, personally, *don't* want to downplay the importance either. I get it
that for an increasingly larger segment of our customers, it is *very*
important and even critical. The same can be said for x-plat.
There have been times that I've seen management come in and say, "this
is the top priority" and then a week later come back and say "that is
the top priority" and when asked, well which one is more important they
say, they both are... (NOTE: I'm not at all saying that is the way it
is now with EMBT!).
My response is simply, "If *everything* is top priority, then *nothing*
is."
--
Allen Bauer
Embarcadero Chief Scientist
http://blogs.embarcadero.com/abauer