search

swig / www

Web pages at http://www.swig.org
10 stars 17 forks source link

Replace broken link for .NET C# #7

Closed breyed closed 7 years ago

breyed commented 7 years ago

This change doesn't address the issue of support for other .NET languages. By using the name C# - MS .NET, there is an implication that other languages such as F# are not supported. Is this true?

wsfulton commented 7 years ago

The generated code is C# which is a .NET framework language and hence all other .NET framework languages can access the assemblies once the C# code has been compiled. This should be obvious to anyone familiar with .NET, but if you think this needs elaborating in the docs, then a patch to https://github.com/swig/swig/blob/master/Doc/Manual/CSharp.html will be most welcome.

breyed commented 7 years ago

Whether a technology is C# dependent depends primarily on whether it relies on C# code generation, such as the entity generators in Entity Frameworks, the XAML designers in WPF/Xamarin, and the method stubbing in Orleans.

It's nice to know that Swig doesn't rely on code generation. To leave more room to clarify that benefit, it would be better to move the language list off the side bar. The sidebar is not a good fit for a language list anyway, since it's not something likely to be helpful to a reader across multiple page visits. A more descriptive summary could look like this:

Swig works with the following runtimes:

  • .NET (including .NET Core and Mono), for example using C#, F#, or Visual Basic
  • JVM, for example using Java, Clojure, or Scala ...