Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
IntraWeb 15.0.16 is out! Includes Delphi 10.3 Rio support!
#1
Hi guys,

New IntraWeb 15.0.16 is available. Includes Delphi 10.3 Rio support.

Delphi Rio build is 26.0.32429.4364 (make sure you don't use an older beta build - although they might work, we cannot guarantee binary compatibility).

Enjoy! Smile

https://www.atozed.com/2018/11/15-0-16/

Version history: https://www.atozed.com/2018/11/15-0-16-h/
Reply
#2
I must point out that I'm genuinely impressed with the amount of effort put into Delphi 10.3 release.

The number of bugs fixed is impressive, not to mention the new additions to the language which are more than welcome:

http://docwiki.embarcadero.com/RADStudio...tudio_10.3
Reply
#3
https://www.codeproject.com/Articles/125...uggestions

Smile
Reply
#4
(11-22-2018, 09:09 AM)Alexandre Machado Wrote: I must point out that I'm genuinely impressed with the amount of effort put into Delphi 10.3 release.

The number of bugs fixed is impressive, not to mention the new additions to the language which are more than welcome:

http://docwiki.embarcadero.com/RADStudio...tudio_10.3

I watched the recorded webinar a couple of days ago.  A lot looked good, though I was doing some other things and may have missed some details.  If I recall, ARC is taking on water and being sunk?  Perhaps even in mobile?  R.I.P.

Some of the variable scope and declaration changes seemed handy, but I'd have thought they'd use a slightly different syntax that seems more consistent elsewhere in Delphi.  Do I remember correctly that inline declaration would be like:
   var  Varname:vartype:=value;
I figured they'd use what seems more Delphi-like to me:
   var  Varname:vartype=value;  // may be misremembering their syntax
That's kind of a nit, but I thought curious.  I always pictured that as the purpose of the :=

The "auto" variables and inferential types seem a bit dangerous (said by a VB guy no less).  I've been a fan, in that world, of sometimes using inferred types while tinkering but forcing full declaration before I'm done (with Option Explicit).  Can inferred types be disabled?

Your ability to prepare a release against it so quickly says a lot about forward compatibility of code, which has been a hot button with me.

Not sure if I'll go there (a lot of landmines between XE2 and there), but they've got my attention again.  Too bad they didn't make all the upgrades as seamless.  They scared me with a couple.

Let me know what I misunderstood.

Dan
Reply
#5
ARC is dead yes. Not sure what they will do for OSX which was why they said ARC was required in Delphi in the first place.

Autos are safe. They aren't ref counted, just auto freed in a finally.
Reply
#6
(11-25-2018, 02:37 PM)kudzu Wrote: ARC is dead yes. Not sure what they will do for OSX which was why they said ARC was required in Delphi in the first place.

Autos are safe. They aren't ref counted, just auto freed in a finally.

OK.  I may have misunderstood their auto (I think it was a C++ feature) as different than the one you described.  I had the impression it was auto type variables, but I could have misunderstood.

Yes, auto as you described would be great.

Dan
Reply
#7
Check my article again:

https://www.codeproject.com/Articles/125...uggestions
Reply
#8
(11-26-2018, 01:43 PM)kudzu Wrote: Check my article again:

https://www.codeproject.com/Articles/125...uggestions

I understood your article and the auto described in it.  That usage would be great.

I did not understand that "auto" described in the Delphi webinar was what you described.  If so, that's great.  I didn't take notes during the webinar and haven't watched it a second time.

Dan
Reply
#9
I havent seen the webinar in question, but it was my understanding that it was as I described. I may be wrong, but if I am then they flubbed up something that was otherwise simple.

See here regarding scope etc:
http://www.delphifeeds.com/go/s/148744
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)