I agree that it's a workaround, not a real fix. Doing real syntax
checking would be better.
However, it matches the way the 'working' variant is treated. I can write:
/// <seealso cref="4::::B;;;B```````````434343"/>
or
/// <seealso cref="!:List<*>"/>
and don't get any warning or error.
.. and optionally worse, error generation in the output xml such as
<seealso cref="!:List<*>"/>
I don't understand what you mean with that. If I write in my code:
/// <seealso cref="List{*}" />
I get
<seealso cref="List{*}" />
in the output xml file. And if I write in my code:
/// <seealso cref="!:List<*>"/>
I get
<seealso cref="!:List<*>"/>
in the output xml file.
Since the current behavior of not accepting Bla{T} or Bla<T>
breaks compatibility with csc I'd really like to see this patch applied
to the code - maybe add a FIXME comment to check the syntax later.
Thanks,
Eberhard Beilharz
Atsushi Eno
Eberhard Beilharz wrote:
gmcs gives warning CS1584 if you have an XML comment referencing a
generic type like cref="Bla<T>" or cref="Bla{T}". Those two variants
work with Microsoft's csc. The only variant that makes gmcs happy is
cref="T:Bla`1" which gives a warning with Microsoft's csc (it used to be
the way to do it with older versions of csc).
Would someone please review and commit my patch attached to bug #480862
(<https://bugzilla.novell.com/show_bug.cgi?id=480862>) which treats
Bla<T> and Bla{T} as being equal to T:Bla`1 in a cref.
Thanks,
Eberhard Beilharz
_______________________________________________
Mono-devel-list mailing list
[email protected]
http://lists.ximian.com/mailman/listinfo/mono-devel-list
_______________________________________________
Mono-devel-list mailing list
[email protected]
http://lists.ximian.com/mailman/listinfo/mono-devel-list
_______________________________________________
Mono-devel-list mailing list
[email protected]
http://lists.ximian.com/mailman/listinfo/mono-devel-list
