> Didn't you just recompile one of your 32bit ones?

Sort of. All the main projects we have have too many have 3rd party dependencies and no XE2 versions yet. Most we have source code for but not all so i have not bothered to recompile them yet  - i can wait a month or few.


> I haven't seen anything about a starter edition for XE2.
it's available for $150 as upgrade (claim you have VS or such) or $200 new - European prices are actually OK for this one - 106 UK pounds for upgrade or 142 for new.

Lot of "missing" features though:
http://edn.embarcadero.com/article/images/41563/Delphi_XE2_Feature_Matrix.pdf

Raul

> What is SA?

Sorry - I keep using wrong terms. Embarcadero version is actually S&M (seriously) : Support and Maintenance.

Raul

>>

Sorry - I keep using wrong terms. Embarcadero version is actually S&M
(seriously) : Support and Maintenance.
<<

Yeah Perhaps S&M is not the best phrase to use.

Michael Riley
GySgt USMC Retired
www.zilchworks.com

Raul

>> Didn't you just recompile one of your 32bit ones?
>
>Sort of. All the main projects we have have too many have 3rd party dependencies and no XE2 versions yet. Most we have source code for but not all so i have not bothered to recompile them yet - i can wait a month or few.
>
cue the sound of mad hysterical laughter as you wait for the pricing from many suppliers.

>> I haven't seen anything about a starter edition for XE2.
>it's available for $150 as upgrade (claim you have VS or such) or $200 new - European prices are actually OK for this one - 106 UK pounds for upgrade or 142 for new.
>
>Lot of "missing" features though:
>http://edn.embarcadero.com/article/images/41563/Delphi_XE2_Feature_Matrix.pdf

Thanks for that. Restricting to 32bits seems sensible but a lot of the other stuff they've left out (eg code formatting) seems designed to just persuade people its not a good development environment and stop them upgrading to the full product.

Roy Lambert

On 3/09/2011 3:10 AM, J.B. Ferguson wrote:
> I am on the Embarcadero maintenance plan so I get all new updates and
> upgrades throughout the year. The maintenance plan actually ends up
> being less expensive in the long run.

Only if you're going to upgrade with every Delphi Version...

I jumped from D7 to D2007, and have now just decided to jump to DXE2.  I
would have been happy to have upgraded inbetween, but being forced to
buy locally at rediculously enhanced prices compared to the USA store
got the better of me each time, (especially because I didn't need to
upgrade) and I ended up refusing.

> Roy Lambert wrote:
> cue the sound of mad hysterical laughter as you wait for the pricing from many suppliers.

Actually that part is OK - when we went thru the whole Unicode/D2009 we dropped anything not supported (or too expensive) and put everything on maintenance.

Though it will be interesting to see how the whole 32/64 + Firemonkey is handled - my hope is that vendors would just include support for VCL32 in and VCL64 with existing components with maintenance release.

Firemonkey is fair game though especially as it comes to visual components as it would be a rewrite. Non-visual would be interesting as it's supposed to mostly just work.

Time will tell

Raul

Jan,

<< I am a neophyte regarding 64-bit vs. 32-bit applications, other than
knowing that more memory can be used by a 64-bit application. With that
in mind, will components which currently work in DXE also work with DXE2
(including to but not limited to EDB and DBISAM) or will component
developers have to upgrade their components as well. >>

It depends upon how the vendor wrote their code.  At the very least, if you
only have .dcus, then those will most likely not be the same between the
32-bit and 64-bit versions (I haven't confirmed this yet, but my gut says
that this will be the case).  As for the source code, the major change is
that 64-bit pointers are 8 bytes in size instead of 4 bytes, so if any of
the components does casting to and from an Integer for object references or
pointers, then the code will have issues when running under 64-bit.

--
Tim Young
Elevate Software
www.elevatesoft.com

Thanks for the insight Tim.
--
Jan


Tim Young [Elevate Software] wrote:

> Jan,
>
> It depends upon how the vendor wrote their code.  At the very least,
> if you only have .dcus, then those will most likely not be the same
> between the 32-bit and 64-bit versions (I haven't confirmed this yet,
> but my gut says that this will be the case).  As for the source code,
> the major change is that 64-bit pointers are 8 bytes in size instead
> of 4 bytes, so if any of the components does casting to and from an
> Integer for object references or pointers, then the code will have
> issues when running under 64-bit.