http://dn.codegear.com/article/28972 2008-10-06T22:32:41-07:00 Desmond User http://threads.codegear.com/threads/threads.exe/userall?commentid=39239 http://threads.codegear.com/threads/threads.exe/view?commentid=39239 2006-07-17T22:09:04-07:00 2006-07-17T22:09:04-07:00

re: Delphi for .NET compiler preview

I'm also facing the same problem. Does any solution about this matter? Melos Ibrani http://threads.codegear.com/threads/threads.exe/userall?commentid=39077 http://threads.codegear.com/threads/threads.exe/view?commentid=39077 2006-05-26T01:47:31-07:00 2006-05-26T01:47:31-07:00

Delphi for .NET compiler preview

I apologize if I am posting this on a wrong place but is this a bug? It is reporting the file as missing allthough it is processing the same one.C:\PER INFO\hotelieri>dccil "c:\PER INFO\hotelieri\Project1.dpr" -U"c:\program files\borland\BDS\4.0\lib\cf" -lu"c:\program files\Microsoft SQL Server 2005 Mobile Edition\Device\Client\v2.0\System.Data.SqlClient.dll"=======================================================Borland Delphi for .NET compiler version 18.0Copyright (c) 1983,2005 Borland Software Corporation.NET Framework v1.1.4322 loadedSystem.Data.SqlClient(0) Fatal: F1026 File not found: 'c:\program files\Microsoft SQL Server 2005 Mobile Edition\Device\Client\v2.0\System.Data.SqlClient.dll'Fatal: E2202 Required package 'System.Data.SqlClient' not found=======================================================Is this a bug? Marthein Plat http://threads.codegear.com/threads/threads.exe/userall?commentid=36546 http://threads.codegear.com/threads/threads.exe/view?commentid=36546 2004-04-22T07:43:23-07:00 2004-04-22T07:43:23-07:00

Interface method resolution

In the article, in the part about Interface method resolution there is an example:"Type TMyClass = class(TBaseClass, IFoo) procedure FooBar(paramlist); procedure IFoo.Bar = FooBar; end;The new version would be:Type TMyClass = class(TBaseClass, IFoo) procedure IFoo.Bar(paramlist); end;"What happens if you have "overlapping" interfaces ?Example:Type TMyClass = class(TBaseClass, IFoo , IOops ) procedure Bar(paramlist); procedure IFoo.Bar = Bar; procedure IOops.Bar = Bar; end;Will this still be supported? Kevin Kraus http://threads.codegear.com/threads/threads.exe/userall?commentid=34466 http://threads.codegear.com/threads/threads.exe/view?commentid=34466 2003-04-16T15:30:27-07:00 2003-04-16T15:30:27-07:00

Delphi for .NET compiler preview

We have acquired a new company that has an application build in Delphi, but we develop in C# .Net. Wanted to know if the new Delphi for .NET will allow something similar to what C++ does for .NET, which is take an existing C++ app, with no code modifications and compile it within C++.NET to generate IL code. Allowing any new development to be done within the .NET platform, but leveraging the existing code with no or minimal modifications.If not, are there going to be converters for Delphi -> Delphi.NET conversions?Kevin hbsyzxj hbsyzxj http://threads.codegear.com/threads/threads.exe/userall?commentid=34305 http://threads.codegear.com/threads/threads.exe/view?commentid=34305 2003-03-20T03:42:14-07:00 2003-03-20T03:42:14-07:00

Delphi for .NET compiler preview

good Hansj?rg Reister http://threads.codegear.com/threads/threads.exe/userall?commentid=33273 http://threads.codegear.com/threads/threads.exe/view?commentid=33273 2002-10-06T04:29:49-07:00 2002-10-06T04:29:49-07:00

re: Delphi for .NET compiler preview

Actually Borlands product politics is very hard to understand!A year ago they created the CLX lib to support Linux (i still do not know who demanded this). They shipped it with D6 - which was a very sad product (actually i bought copies that i never used). Now they release Delphi 7 - not really supporting .NET telling us that .NET will enable Delphi written applications on all .NET plattforms - CLX dead??We actually have 3 DB access arcitectures (DB CLX, BDE and ADO - a sad wrapper implementation, what about ADO.NET??), 3 class frameworks (VCL, CLX and .NET framework), 4 distributed application technologies (.NET remoting {WebServices}, DataSnap, Corba, DCOM) ....E.g. DataSnap is now royalty free while you had to pay a lot in the past. Kylix 3 is now contained within Delphi while you had to buy it seperately in the past.I can not see any product strategy in there - can you? Craven Weasel http://threads.codegear.com/threads/threads.exe/userall?commentid=33172 http://threads.codegear.com/threads/threads.exe/view?commentid=33172 2002-09-22T18:02:52-07:00 2002-09-22T18:02:52-07:00

Delphi for .NET compiler preview

excuseme. free for me delphi v7trial or v7.neti'm thank you very must. David Fung http://threads.codegear.com/threads/threads.exe/userall?commentid=33001 http://threads.codegear.com/threads/threads.exe/view?commentid=33001 2002-08-23T17:12:01-07:00 2002-08-23T17:12:01-07:00

Delphi for .NET compiler preview

I am confused in the product position between Delphi 7 and Delphi for .NET. Will Delphi for .NET be the next version of Delphi (i.e. Delphi 8) or it will be a new product branch? I am thinking of upgrading to D7 Professional now but i am hesitated because if Delphi for .NET is D8, i will probably wait till next year for the upgrade. Illya Kysil http://threads.codegear.com/threads/threads.exe/userall?commentid=32936 http://threads.codegear.com/threads/threads.exe/view?commentid=32936 2002-08-14T01:07:59-07:00 2002-08-14T01:07:59-07:00

re: Appropriate use of units in a namespace

> While placing every class in its own unit has advantages, it> certainly has costs as well. You will end up with huge uses clauses> and huge dependency graphs which will take the compiler longer to> process than a moderate number of units with a moderate number of> classes in each unit.That is why I said that units are not equivalent to namespaces.1. I don't want to bother which unit defines a class I need.All I want to know is a namespace. I like the Java way.If I say 'import java.awt.*;' then any unqualified class name is searched in java.lang namespace then java.awt namespace.If I say 'import java.awt.Button;' then any unqualified reference to Button is resolved to java.awt.Button.If I don't include import statement but say java.awt.Button somewhere in my code the reference will be resolved as well.That is what I expect - I want to control how should I write class name references in MY code.2. Keeping more stuff in ONE unit really results in "huge dependency graphs".That is - I can't control access to implementation details between classes defined in one unit. Danny Thorpe http://threads.codegear.com/threads/threads.exe/userall?commentid=32933 http://threads.codegear.com/threads/threads.exe/view?commentid=32933 2002-08-13T16:18:03-07:00 2002-08-13T16:18:03-07:00

Appropriate use of units in a namespace

You will be able to "place" symbols into other namespaces independently of what units those symbols live in. This will be the exception rather than the rule, and it will be done at the package level, not the unit level. Most of the time, using the unit name as the namespace is the simplest and most natural approach for most programmers. Borland Object Pascal and Delphi have been using unit names in a namespace capacity for more than 13 years. You use the unit identifier to disambiguate same-named symbols that live in different units, right? That's exactly what a namespace is. The only things that will be changing for .NET is that the unit names may contain dots, and may refer to things (.NET namespaces) which are not compiled from Delphi code.While placing every class in its own unit has advantages, it certainly has costs as well. You will end up with huge uses clauses and huge dependency graphs which will take the compiler longer to process than a moderate number of units with a moderate number of classes in each unit. Let's face it, there is memory and performance overhead for each unit. Having lots of little tiny units will be more memory intensive and more disk intensive than having fewer units with more stuff in them. Believe it or not, one of the most time-consuming steps in the Delphi compile process is file searching - finding the DCU or PAS file on the search path.All things in moderation - including moderation!-Danny ThorpeBorland