I have moved all my application to XE3 with no problem. They are all working properly. You have to know that buggy components or "experts" can easily crash the IDE. So if you installation is unstable, first reinstall from scratch without installing any component and see if it still fails for you. Also be sure to install all updates and service packs for Delphi XE3 (See registred user download at Embarcadero website) and Windows.
Linas Naginionis Exactly. Also lots of broken stuff in my favourite unit Rtti.pas which is not only regression but did not work in the first place like 3 years ago and still not fixed!
What's especially annoying is when bugs got fixed in XE2 or XE3 and you write a library that targets also 2010 and XE you have to find workarounds yourself (thanks runtime patching)
Did I mention the internal compiler error O870 that forces you to restart the IDE because it won't go away if you are making heavy use of generics and anonymous methods?
I guess that is what you get when you are working on the bleeding edge of language features.
I was personally hit by http://qc.embarcadero.com/wc/qcmain.aspx?d=108942. There is a workaround for this bug but the worst thing is that compiler raises errors in random places, not on the line which triggered the error, so you are stuck and don't know what's wrong.
Stefan, What is the best way to communicate to you about issues I find in getting started with DSharp? For example, Sample7 needs delphi-coll, but the delphi-coll code has issues, and is not maintained. Also, I get build errors on Samples\MVVM\Explorer. I did add both of these to issues on the delphisorcery site.
Stefan Glienke Well, I have done it again. :) But one was my own fault. Also, I e-mailed you directly about a bindings question--my own issues in understanding how to approach them.
Linas Naginionis this looks like the bug in Delphi 2006 when calling methods on parameters of records you get back from a function. That basically made hassle of most of the operator overloading stuff (because an overload is internally a function) as you had to introduce intermediate variables all over the place.
I'm quite satisfied with XE2, I used XE before it and 2010 before that...
ReplyDeleteWhat kind of regressions are you talking about? (I still use D2007)
ReplyDeleteI have moved all my application to XE3 with no problem. They are all working properly. You have to know that buggy components or "experts" can easily crash the IDE. So if you installation is unstable, first reinstall from scratch without installing any component and see if it still fails for you. Also be sure to install all updates and service packs for Delphi XE3 (See registred user download at Embarcadero website) and Windows.
ReplyDeleteFrançois Piette It's mostly not IDE issues but compiler regressions.
ReplyDeleteHave you entered QC reports for all those regressions ? Please provide the numbers here.
ReplyDeleteLinas Naginionis Exactly. Also lots of broken stuff in my favourite unit Rtti.pas which is not only regression but did not work in the first place like 3 years ago and still not fixed!
ReplyDeleteFrançois Piette Just a few I took from a quick "my reports" query in QC:
http://qc.embarcadero.com/wc/qcmain.aspx?d=98892
http://qc.embarcadero.com/wc/qcmain.aspx?d=99028 (actually not a regression but a feature not working that does for 32-bit)
http://qc.embarcadero.com/wc/qcmain.aspx?d=100849
http://qc.embarcadero.com/wc/qcmain.aspx?d=112068
http://qc.embarcadero.com/wc/qcmain.aspx?d=112096
What's especially annoying is when bugs got fixed in XE2 or XE3 and you write a library that targets also 2010 and XE you have to find workarounds yourself (thanks runtime patching)
Did I mention the internal compiler error O870 that forces you to restart the IDE because it won't go away if you are making heavy use of generics and anonymous methods?
I guess that is what you get when you are working on the bleeding edge of language features.
I was personally hit by http://qc.embarcadero.com/wc/qcmain.aspx?d=108942. There is a workaround for this bug but the worst thing is that compiler raises errors in random places, not on the line which triggered the error, so you are stuck and don't know what's wrong.
ReplyDeleteLinas Naginionis Oh yeah, I remember that one.
ReplyDeleteStefan, What is the best way to communicate to you about issues I find in getting started with DSharp? For example, Sample7 needs delphi-coll, but the delphi-coll code has issues, and is not maintained. Also, I get build errors on Samples\MVVM\Explorer. I did add both of these to issues on the delphisorcery site.
ReplyDeleteBill Meyer Actually that is the best way to report bugs :)
ReplyDeleteStefan Glienke Well, I have done it again. :) But one was my own fault. Also, I e-mailed you directly about a bindings question--my own issues in understanding how to approach them.
ReplyDeleteLinas Naginionis this looks like the bug in Delphi 2006 when calling methods on parameters of records you get back from a function. That basically made hassle of most of the operator overloading stuff (because an overload is internally a function) as you had to introduce intermediate variables all over the place.
ReplyDelete