Re: Cool! A Variant in Delphi.NET is just a TObject!



Bob Dawson a écrit :

As I recall you were pretty amused with making untyped parameters implicit
Objects as well--you talked about breaking the news to Anders H that untyped
method params were not only possible in Delphi for .NET, but would be type
safe <g>.

Hmmm, sounds like generics to me ;-)

Joanna

--
Joanna Carter [TeamB]
Consultant Software Engineer
.



Relevant Pages

  • Re: Sale collapse
    ... Do you realize it has now been 10 years since Anders left Borland? ... some time before Delphi *3* was released, and apparently, while he still had ... talent, but only due to the very reasons that have finally ... "Those who disdain wealth as a worthy goal for an individual or a ...
    (borland.public.delphi.non-technical)
  • Re: Embarcadero newsgroups
    ... this kind or "protected" Delphi news messages. ... Usenet News services are currently unreliable; I may not see all articles here. ...
    (comp.lang.pascal.delphi.misc)
  • Re: Class References
    ... Considering that both languages had common ... I asked Anders Hejlsberg about this when he visited Oslo in April 2005 ... I still think that class references, ... methods are neat Delphi features, but I understand that they didn't want to ...
    (borland.public.delphi.non-technical)
  • Re: Sale collapse
    ... I know a whole bunch of guys work on Delphi and visit here but why should ... would it cost to employ Anders Heilsberg or better still could you ... Do you realize it has now been 10 years since Anders left Borland? ... Yes Anders is *obviously* a great talent, ...
    (borland.public.delphi.non-technical)
  • Re: Sale collapse
    ... would it cost to employ Anders Heilsberg or better still could you ... Do you realize it has now been 10 years since Anders left Borland? ... He left some time before Delphi *3* was released, and apparently, while he still had *some* involvement with version 3, it was already much reduced from his involvement with 1 and 2 and the TP product line before that. ... The problems that Delphi has had over it's history have *extremely* little to do with talent, but only due to the very reasons that have finally resulted in the new company being formed. ...
    (borland.public.delphi.non-technical)