SDL and C#

Hi Folks

Has anyone done anything with SDL 1.3 and C# yet? I’d be interested to hear from people and their experiences with it.

I am looking into C# as a replacement for the C++ stuff I do…

Thanks
Ed

Hi,

if you want to use C# instead, maybe you are better off with learning XNA.

http://msdn.microsoft.com/en-gb/xna

In order to take full advantage of C# you really need to be on Windows, so
you
don’t gain much by using SDL.

Personally I don’t value mono that much, and prefer other solutions when
portability
is a concern, but when I am on Windows I don’t have any issue with using C#,
or
F# as of lately. So don’t take my comment as a bias against the language.–
Paulo

On Tue, Mar 1, 2011 at 1:17 PM, ebyard <e_byard at yahoo.co.uk> wrote:

Hi Folks

Has anyone done anything with SDL 1.3 and C# yet? I’d be interested to hear
from people and their experiences with it.

I am looking into C# as a replacement for the C++ stuff I do…

Thanks
Ed


SDL mailing list
SDL at lists.libsdl.org
http://lists.libsdl.org/listinfo.cgi/sdl-libsdl.org

Not sure what your beef with mono is, but, in my experience, it works
just fine on many platforms. The mono VM isn’t as fast as the .NET VM,
yet, of course.

Personally, I’ve been shying away from VM based systems, back to C for
most everything, but, if you’re amenable to using a VM in the first
place, mono/.NET is a decent choice.On Tue, Mar 1, 2011 at 08:25, Paulo Pinto wrote:

Hi,

if you want to use C# instead, maybe you are better off with learning XNA.

http://msdn.microsoft.com/en-gb/xna

In order to take full advantage of C# you really need to be on Windows, so
you
don’t gain much by using SDL.

Personally I don’t value mono that much, and prefer other solutions when
portability
is a concern, but when I am on Windows I don’t have any issue with using C#,
or F# as of lately. So don’t take my comment as a bias against the language.


Do what you can, where you are, with what you have. - T. Roosevelt

My problem with mono is that it isn’t a 100% compliant implementation of
.Net.

So while other VM systems I have the garantee, that as long as I don’t use
any
specific platform feature, the code is portable across VM implementations.
Not
so with mono.

Having said that,On Tue, Mar 1, 2011 at 4:53 PM, Greg Jandl <greg.jandl at gmail.com> wrote:

On Tue, Mar 1, 2011 at 08:25, Paulo Pinto <@Paulo_Pinto> wrote:

Hi,

if you want to use C# instead, maybe you are better off with learning
XNA.

http://msdn.microsoft.com/en-gb/xna

In order to take full advantage of C# you really need to be on Windows,
so
you
don’t gain much by using SDL.

Personally I don’t value mono that much, and prefer other solutions when
portability
is a concern, but when I am on Windows I don’t have any issue with using
C#,
or F# as of lately. So don’t take my comment as a bias against the
language.

Not sure what your beef with mono is, but, in my experience, it works
just fine on many platforms. The mono VM isn’t as fast as the .NET VM,
yet, of course.

Personally, I’ve been shying away from VM based systems, back to C for
most everything, but, if you’re amenable to using a VM in the first
place, mono/.NET is a decent choice.


Do what you can, where you are, with what you have. - T. Roosevelt


SDL mailing list
SDL at lists.libsdl.org
http://lists.libsdl.org/listinfo.cgi/sdl-libsdl.org

Sorry for the previous post, hit “Send” by accident.

My problem with mono is that it isn’t a 100% compliant implementation of
.Net.

So while other VM systems I have the guarantee, that as long as I don’t use
any
specific platform feature, the code is portable across VM implementations.
Not
so with mono, since they decided not to implement all .Net APIs.

Having said that, I do conceed that mono does offer quite a few nice
features
that Microsoft still doesn’t, like the linker, AOT and intrinsics.–
Paulo

On Tue, Mar 1, 2011 at 8:04 PM, Paulo Pinto <paulo.jpinto at gmail.com> wrote:

My problem with mono is that it isn’t a 100% compliant implementation of
.Net.

So while other VM systems I have the garantee, that as long as I don’t use
any
specific platform feature, the code is portable across VM implementations.
Not
so with mono.

Having said that,

On Tue, Mar 1, 2011 at 4:53 PM, Greg Jandl <greg.jandl at gmail.com> wrote:

On Tue, Mar 1, 2011 at 08:25, Paulo Pinto <@Paulo_Pinto> wrote:

Hi,

if you want to use C# instead, maybe you are better off with learning
XNA.

http://msdn.microsoft.com/en-gb/xna

In order to take full advantage of C# you really need to be on Windows,
so
you
don’t gain much by using SDL.

Personally I don’t value mono that much, and prefer other solutions when
portability
is a concern, but when I am on Windows I don’t have any issue with using
C#,
or F# as of lately. So don’t take my comment as a bias against the
language.

Not sure what your beef with mono is, but, in my experience, it works
just fine on many platforms. The mono VM isn’t as fast as the .NET VM,
yet, of course.

Personally, I’ve been shying away from VM based systems, back to C for
most everything, but, if you’re amenable to using a VM in the first
place, mono/.NET is a decent choice.


Do what you can, where you are, with what you have. - T. Roosevelt


SDL mailing list
SDL at lists.libsdl.org
http://lists.libsdl.org/listinfo.cgi/sdl-libsdl.org

Hi Ed, have you seen the demos on the Wiki of this project?
http://cs-sdl.sourceforge.net
Not sure how much in sync this is with SDL 1.3 …

Personally, I find C# in VisualStudio quite “productive” and with Mono
one can go cross-platform (although I’ve never tried SDL, I did get a
webservice DLL to work once with mod_mono on a Debian box).

–AndreasOn 3/1/11 4:17 AM, ebyard wrote:

Hi Folks

Has anyone done anything with SDL 1.3 and C# yet? I’d be interested to
hear from people and their experiences with it.

I am looking into C# as a replacement for the C++ stuff I do…

Thanks
Ed


SDL mailing list
SDL at lists.libsdl.org
http://lists.libsdl.org/listinfo.cgi/sdl-libsdl.org