The problem is that not all version of C# are completely backwards compatible themselves. And for some reason I am still missing the point. Mono going to 4.0 just means dmcs is available. Then when you move your project to 4.0, you set the makefile to target dmcs. Where is the friction going on? When you project is version X, it won't work with a previous compiler anyway, and using a newer compiler isn't needed. -- Mark
On Sun, Jun 27, 2010 at 7:36 PM, Russell Wallace <russell.wall...@gmail.com>wrote: > Yes, cc is an excellent analogy. And csc would definitely make sense, > except it seems to be already used for something else? > > a...@a-desktop:~$ csc > The program 'csc' is currently not installed. You can install it by > typing: > sudo apt-get install chicken-bin > > On Sun, Jun 27, 2010 at 6:13 PM, Andreas Färber <andreas.faer...@web.de> > wrote: > > Am 27.06.2010 um 18:37 schrieb Russell Wallace: > > > >> Would it be possible to define a command to run whatever the > >> latest/currently installed C# compiler is? It seems to me that command > >> should be mcs, but it doesn't really matter what it is, as long as it > >> works reliably on all systems. > > > > I would prefer a csc command (like the usual cc symlink) that invokes the > > available/required Mono C# compiler. It would help with .NET > compatibility > > at the same time. > > > > Andreas > > > _______________________________________________ > Mono-devel-list mailing list > Mono-devel-list@lists.ximian.com > http://lists.ximian.com/mailman/listinfo/mono-devel-list >
_______________________________________________ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
