Hi everybody,
For the Indy project we use the SSL/TLS implementation of Mono.Security.dll.
You guys did a great job with that.
But we have a problem. We're trying to build the project without compiler
hints/warning but when linking to the Mono.Security.dll assembly, the delphi
compiler can't cope
On Sat, 2005-05-28 at 09:28 +0200, Matthijs ter Woord (meddochat) wrote:
> Is this the coding style used in the class libraries? or could this be
> changed?
This coding style (having two members that differ only in case) is
somewhat common in the class libraries. The primary difference is that
ty
Hi,
I have never tried to use Delphi.NET but it is really weird if it
really tries to validate(?) non-CLSCompliant types while it should
not (MiniParser is not CLS compliant) and rejects them because
of that.
It sounds like a bug in Delphi.NET.
Atsushi Eno
Matthijs ter Woord (meddochat) wrote
Hi Atsushi,
I get your point. MiniParser isn't CLS Compliant.
[Error] E2421 Imported identifier 'Names' conflicts with 'names' in
'MiniParser.AttrListImpl'
[Error] E2421 Imported identifier 'Values' conflicts with 'values' in
'MiniParser.AttrListImpl'
[Error] E2421 Imported identifier 'Line' conf
ECTED]>
Sent: Saturday, June 11, 2005 10:49 AM
Subject: Re: [Mono-devel-list] Mono.Xml.MiniParser
> No. Those types which inside non-CLSCompliant type can never be
> CLSCompliant. Such inner type itself may already be in conflict
> with another member in the outer non-CLSCompliant ty
No. Those types which inside non-CLSCompliant type can never be
CLSCompliant. Such inner type itself may already be in conflict
with another member in the outer non-CLSCompliant type.
BTW you could also copy my SmallXmlParser in corlib into your
project. It is a replacement of MiniParser.
Atsush
