digitalmars.D.announce - Iup and nukclear interface in D.
- mogu (8/8) Jun 22 2016 http://code.dlang.org/packages/iupd
- Mike Parker (8/10) Jun 23 2016 A couple of points:
- mogu (4/15) Jun 23 2016 Thx, iup is the first project i tried to binding in D. So it has
- David Nadlinger (6/8) Jun 23 2016 Be careful, though, if the C library supports user-specified
- Mike Parker (2/9) Jun 23 2016 True. I should have added that caveat myself.
- Jordan Wilson (3/11) Jun 23 2016 Great, look forward to checking it out. Any plans for the CD
- mogu (2/14) Jun 24 2016 Coming soon. :)
http://code.dlang.org/packages/iupd http://code.dlang.org/packages/nukleard iupd removes all deprecated items in IUP, current version is IUP 3.18. nukleard may have some bugs in name mangling. Does a struct's field name like `null`, i changed it to null_, may be issue? Can pragma(mangle, "name") help in this context?
Jun 22 2016
On Thursday, 23 June 2016 at 06:32:09 UTC, mogu wrote:http://code.dlang.org/packages/iupd http://code.dlang.org/packages/nukleardA couple of points: * All of those 'static immutable' you have would be better as manifest constants, or logically grouped in anonymous enums. The former are lvalues and will wind up in the data segment, but you likely don't need them to be. * extern(C) functions should, at a minimum, be declared as nogc and nothrow for client code using those attributes.
Jun 23 2016
mogu <mogucpp 163.com> On Thursday, 23 June 2016 at 08:14:42 UTC, Mike Parker wrote:On Thursday, 23 June 2016 at 06:32:09 UTC, mogu wrote:Thx, iup is the first project i tried to binding in D. So it has so many issues. They all be reconsidered in nuklear binding. Also, i'll fix iup binding after some busy company work.http://code.dlang.org/packages/iupd http://code.dlang.org/packages/nukleardA couple of points: * All of those 'static immutable' you have would be better as manifest constants, or logically grouped in anonymous enums. The former are lvalues and will wind up in the data segment, but you likely don't need them to be. * extern(C) functions should, at a minimum, be declared as nogc and nothrow for client code using those attributes.
Jun 23 2016
On Thursday, 23 June 2016 at 08:14:42 UTC, Mike Parker wrote:* extern(C) functions should, at a minimum, be declared as nogc and nothrow for client code using those attributes.Be careful, though, if the C library supports user-specified callbacks to be set for some functionality – unless you also require those to be nogc, that guarantee could easily be violated. — David
Jun 23 2016
On Thursday, 23 June 2016 at 23:01:16 UTC, David Nadlinger wrote:On Thursday, 23 June 2016 at 08:14:42 UTC, Mike Parker wrote:True. I should have added that caveat myself.* extern(C) functions should, at a minimum, be declared as nogc and nothrow for client code using those attributes.Be careful, though, if the C library supports user-specified callbacks to be set for some functionality – unless you also require those to be nogc, that guarantee could easily be violated.
Jun 23 2016
On Thursday, 23 June 2016 at 06:32:09 UTC, mogu wrote:http://code.dlang.org/packages/iupd http://code.dlang.org/packages/nukleard iupd removes all deprecated items in IUP, current version is IUP 3.18. nukleard may have some bugs in name mangling. Does a struct's field name like `null`, i changed it to null_, may be issue? Can pragma(mangle, "name") help in this context?Great, look forward to checking it out. Any plans for the CD library?
Jun 23 2016
On Thursday, 23 June 2016 at 20:04:51 UTC, Jordan Wilson wrote:On Thursday, 23 June 2016 at 06:32:09 UTC, mogu wrote:Coming soon. :)http://code.dlang.org/packages/iupd http://code.dlang.org/packages/nukleard iupd removes all deprecated items in IUP, current version is IUP 3.18. nukleard may have some bugs in name mangling. Does a struct's field name like `null`, i changed it to null_, may be issue? Can pragma(mangle, "name") help in this context?Great, look forward to checking it out. Any plans for the CD library?
Jun 24 2016