I got a chuckle out of this comment in an XE4 press release:
I got a chuckle out of this comment in an XE4 press release:
You are advised to rewrite code that uses WITH as this is likely to be removed in future versions. I can see the benefit in enforcing this, as I have bumped into so many scope errors caused by over-zealous WITH usage over the years…
Today WITH, tomorrow FreeAndNil :-)
You are advised to rewrite code that uses WITH as this is likely to be removed in future versions. I can see the benefit in enforcing this, as I have bumped into so many scope errors caused by over-zealous WITH usage over the years…
Today WITH, tomorrow FreeAndNil :-)
I would have loved to see - as Eric Grange mentioned - an extended With syntax:
ReplyDeletewith a := array[ix].reference.item; b := some.other.item do
and Pointers.....
ReplyDeleteWith is not good enough, what about using statement in C#/VB.NET http://msdn.microsoft.com/library/yh598w02.aspx ?
ReplyDelete