No culling sims 4 registration#

One thing I would probably be critical of, is the editor. I like systems that utilise tools and frameworks to allow the developer to achieve their goals - and more importantly, extensible enough that you can find ways around problems. I like the way it works вЂ¦ but thats just me. Not sure how package management and extension management would occur - might be more problematic.ДЄs it stands at the moment.Potentially nefarious code could get in - although with open source, this is more difficult in reality.Difficult to control and manage the environment and thus track bugs and issues (this is quite a large prob).A wider array of libs would almost be directly accessible.It should be nicer to manage on the Java/integration side because you end up with some simple C handlers rather than problematic method conversions.

An extension could simply provide static cdecl definitions and thus allow a wider array of calling conventions (allowed by C).

The interface is then defined where you use it (in lua) and thus needs minimal documentation.

However if you could use the ffi.cdef (or similar) to define the wrapping calls then it would make things very clean when building external interfaces. This is fine and how normal lua does it, so its probably quite familiar to most people anyway.

No culling sims 4 registration#

Your current api is traditional registration setup via C/C++. Im thinking this as I go, so stay with me I do wonder if theres a nice way to make it ffi friendly вЂ¦ I know html is pretty much impossible for that, but it makes me think there might be a nice way under the hood to map C libs like like ffi does - or even using the powerful ffi.cdef system to do so. I work a great deal with C libs and C wrappers in my work and in the past, so I find it very convenient and powerful. From an initial use case perspective (early days) I like the native extension setup.