Luca Piccioni

Here is my thoughts about the issue. > Change `Gl` to `GL` This has always disturbed me. I don't remember why I've chosen the camel case convention for the project...

> Provide methods with `ref` parameters I found the emblematic use case. P/Invoke default marshaller can pass arguments by value, for free for basic system types, including `IntPtr`. The `IntPtr`...

@mellinoe - _Allocation-less_: generally speaking the wrapper methods really try to avoid allocation of temporary objects. The `Gen*` commands returning a single GL object were loosely based on the complete...

Thank you! Evidently it means that arguments are intended as row-major matrices. Ouch. Indeed we need to transpose 3x times? Maybe it's better to remove Numerics from Matrix*.

Numerics structure have special JIT management, and the generic functions on some platforms uses the "obscure" __makeref keyword, which assumes that the value is allocate on stack. On what platform...

Correct. Tonight I'll check with some unit tests...

I've checked the unit tests for glUniform[1-4](f|i|ui|d)v, and they are currently calling generic Uniform calls (but not the generic GetUniform calls), and they run successfully on my machine. I thought...

I don't see any major issue in the code you posted; I would avoid repeated `_dc.MakeCurrent(_ctx);` and `_dc.MakeCurrent(IntPtr.Zero);` since they would reload all GL context function pointers at each WM_PAINT...

@21c-HK The [.Net Standard 1.4](https://github.com/luca-piccioni/OpenGL.Net/blob/master/OpenGL.Net/OpenGL.Net_netstd1.4.csproj) currently compiles. I suppose it runs well as the others. Have you tried it? @JimSEOW I currently run .NET Standard 2.0 with [.NET Core 2.0...

@HUg0005 It is necessary to build, test and deploy using VS 2017 on AppVeyor. Currently builds fine; it would be nice to have a unit test set for .NET Core....