Re: [DotGNU]What's this error?

[Rhys Weatherley]

On Wednesday 13 August 2003 04:28 am, DrDiettrich wrote:

> I have just removed the ".dll" from the call, which makes the error
> disappear, but then FindType doesn't find anything. Have you tested
> FindType.cs with the updated library? I'll try now to find out more
> about the sample code, and notify you when I find more problems.

I didn't run FindType - only the other test cases you sent.  FindType was too 
complex of a test case for me to work from and I have no idea what it is 
supposed to do when it works correctly.  If you were to strip it down to a 
simpler test case, then I can look into it.  Please log the bug in Savannah.

> There seems to exist at least one more problem, with testAssy.Location
> or Path, the retrieved directory string seems to be empty.

The CVS version has a new implementation of "Assembly.Location", which did not 
exist in 0.5.10.

> I also couldn't use Debug.Assert. The ECMA HTML docs only show
> ConditionalAttribute in the System.Diagnostics namespace, so I'm
> somewhat confused about what really should be implemented in that
> namespace. The pnetlib source code at least implements a lot more. This
> leads me to more questions:

Debug.Assert is available in the "System.dll" assembly, which you will need to 
import using the "-lSystem" option to "cscc".  The MS compiler imports all 
system libraries by default, which is why you get "Debug.Assert" 
automatically - cscc only imports "mscorlib.dll" by default.

> Should we implement everything what MS has implemented in .NET, so that
> all .NET programs will run on pnet?

That's the goal.

> How to add MS extensions to the pnetlib? Shouldn't we separate the
> source code for all extensions from the standard, e.g. in separate
> subdirectories?

The source code uses "#if" pre-processor blocks around MS extensions.  
Separate subdirectories wouldn't work very well because some classes have 
different contents in MS and ECMA modes.  Maintaining separate copies of the 
same class would quickly lead to errors in common code.

Cheers,

Rhys.