Comments for Delphi Corner Weblog

Comment on Delphi for .NET namespaces misunderstood? by Dmitry

Dmitry — Thu, 08 May 2008 13:06:57 +0000

Hello,

Sorry for posting off topic here, I just can’t find direct mail or other communication channel at your site.

In your article you have mentioned a possible solution to CRTL external functions problem by declaring them as external in msvcrt.dll I’ve found another way how to solve this problem- extract all OBJ files directly from BCB55’s cw32.lib file using tlib as a helper tool. __ftol and _ftol are in ftol.obj This way I was able to bind sqlite3.lib directly into my Delphi project without DLL file (81 obj files, the order of $L is important) The only unresolved external is _wsprintfA wich is in user32.dll

Comment on Delphi for .NET namespaces misunderstood? by Olaf Monien

Olaf Monien — Tue, 10 Oct 2006 20:48:25 +0000

I don’t see a technical problem either with the "Units" subnamespace. It’s purely cosmetic - IMO.

Comment on Delphi for .NET namespaces misunderstood? by Rudy Velthuis

Rudy Velthuis — Mon, 09 Oct 2006 16:43:53 +0000

AFAIK, the Units subnamespace is the namespace binding non-method functions and procedures in Delphi to .NET classes. There is no way to get rid of it, and I personally don’t see it as a problem. It may look weird in Reflector, but Reflector is not .NET, it is only a tool for it.

Comment on Delphi for .NET namespaces misunderstood? by Olaf Monien

Olaf Monien — Mon, 09 Oct 2006 00:47:54 +0000

Actually discard #2 - it’s been a compiler error ….

This just leaves #1 - the "mysterious Units" namespace - which make Delphi assemblies look weird to non-Delphi users. They just have to ignore it, as everything else works fine.

Comment on Delphi for .NET namespaces misunderstood? by Olaf Monien

Olaf Monien — Sat, 07 Oct 2006 21:50:44 +0000

Good post! There seem to be indeed some misunderstandings about namespaces out there - not just in the Delphi world ;-)

Anyway, there are two things which may lead to confusion in Delphi.NET:

1: Delphi always emits an *additional* implicit "Units" name space. If you have a unit "Foo.Bar.Test.pas" containing a class "Test" Then you will see a name space "Foo.Bar" as expected, but also a name space Foo.Bar.Units, also containing a class "Test".

This is not just an "alias", in fact Delphi will mark any class in these "Units" name spaces as "sealed", and these classes appear incomplete (no constructors, etc). In other words this is just some "magic", used by Delphi only. In other .NET languages you should not touch these "Units" namespaces.

2: Error Insight (at least on my machine) does not like stuff like this:

unit Foo.Bar.Class1;

…

end;

unit Foo.Bar.Class2;

interface

…

implementation

uses Class1;

…

This will compile fine, but "uses Class1" will be underlined in red. Errorinsight only likes the full reference - no matter what’s defined as Default Namespace:

unit Foo.Bar.Class2;

interface

…

implementation

uses Foo.Bar.Class1;

…

Comment on Delphi for .NET namespaces misunderstood? by Marco van de Voort

Marco van de Voort — Thu, 05 Oct 2006 10:42:20 +0000

/me puts in a vote for Modula-2 namespace handling.

Actually I M2ed a while before returning to Pascal (then still TP), but that choice was more based on the compiler than the language.

Inner modules and the import behaviour are still the nice parts of M2.

Comment on My quotes.txt file by Bill Mogk

Bill Mogk — Wed, 02 Aug 2006 08:53:39 +0000

Seeing the quote by PhR (about dentists) brought back memories of other Non-Tech "characters" from past years.

Comment on My quotes.txt file by Rudy Velthuis

Rudy Velthuis — Mon, 31 Jul 2006 05:06:04 +0000

You can specify the signature in the identity. In your signature, use the %sigfile% variable. My signature for my TeamB identity looks like:

—————————————————————-8<——

Rudy Velthuis [TeamB] http://rvelthuis.de/

%sigfile%

—————————————————————-8<——

Comment on My quotes.txt file by BradP

BradP — Sun, 30 Jul 2006 03:09:32 +0000

How do you get XanaNews to use your quote file?

Comment on More undocumented Win32 language features by Roozbeh GHolizadeh

Roozbeh GHolizadeh — Wed, 05 Oct 2005 11:06:02 +0000

Well i think this is also undocumented!
in delphi help about virtual methods in properties stated
"If fieldOrMethod is a method, it cannot be dynamic and, if virtual, cannot be overloaded"

but following code compiles fine

myclass=class
procedure SetTestValue(invalue : integer);overload;virtual;
procedure SetTestValue(invalue : string);overload;virtual;
property testvalue:integer write SetTestValue;
end;

and doesnt compile in delphi 7!

i also found this intresting thing(i dont know if in help stated or not)

property only works with first overloaded procedure so the following doesnt compile!

procedure SetTestValue(invalue : integer);overload;virtual;
procedure SetTestValue(invalue : string);overload;virtual;
property testvalue:string write SetTestValue;

forgive me if all was documented and told before ;)