|
Bugzilla – Full Text Bug Listing |
| Summary: | mcs prefers corlib types to assembly types | ||
|---|---|---|---|
| Product: | [Mono] Mono: Compilers | Reporter: | Sebastien Pouliot <spouliot> |
| Component: | C# | Assignee: | Mono Bugs <mono-bugs> |
| Status: | RESOLVED FIXED | QA Contact: | Mono Bugs <mono-bugs> |
| Severity: | Normal | ||
| Priority: | P5 - None | ||
| Version: | SVN | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: | test case from (uncommitted) moonlight unit tests | ||
Fixed in trunk. |
Created attachment 317224 [details] test case from (uncommitted) moonlight unit tests If the same type name (including namespace) is defined in both the assembly being compiled and mscorlib (possibly others too) then *mcs prefers the one in corlib while MS csc prefers the one in the assembly. Not sure what the specs are in this case (and I prefer out own behavior) but it could break compatibility since our compiled assembly would be different from the one MS compile.