Nuklear: A single-header ANSI C GUI library • Hacker News Board

Re: Nuklear: A single-header ANSI C GUI library

#11

Post by lou1306 » Sat, Feb 10, 2018, 3:19 PM UTC

cryptos wrote: post #9

Not the best name in times of Trump...

Could be a pun on Electron, though.

Re: Nuklear: A single-header ANSI C GUI library

#12

Post by akvadrako » Sat, Feb 10, 2018, 3:51 PM UTC

You can't build a "ANSI C GUI library", because ANSI C has no graphical capabilities.

Re: Nuklear: A single-header ANSI C GUI library

#13

Post by zevv » Sat, Feb 10, 2018, 4:07 PM UTC

I really do not understand why 'single header' is considered a good thing, but I see this more and more often on libraries. What is the reason all the code is put in the header file?

Re: Nuklear: A single-header ANSI C GUI library

#14

Post by [deleted] » Sat, Feb 10, 2018, 4:11 PM UTC

akvadrako wrote: post #12

You can't build a "ANSI C GUI library", because ANSI C has no graphical capabilities.

[deleted]

Re: Nuklear: A single-header ANSI C GUI library

#15

Post by kzrdude » Sat, Feb 10, 2018, 4:13 PM UTC

zevv wrote: post #13

I really do not understand why 'single header' is considered a good thing, but I see this more and more often on libraries. What is the reason all the code is put in the header file?

because dependency management and build systems are hard to get right and not standardized. It's a simple distribution model that works everywhere.

Re: Nuklear: A single-header ANSI C GUI library

#16

Post by gnud » Sat, Feb 10, 2018, 4:14 PM UTC

I'm guessing this deals with accessibility the same way most other 'light' UI toolkits do - by not dealing with it at all?

Re: Nuklear: A single-header ANSI C GUI library

#17

Post by mwcampbell » Sat, Feb 10, 2018, 4:17 PM UTC

Before you use this in your next important application, please read the comment on accessibility that I posted the other day on the LCUI thread: https://news.ycombinator.com/item?id=16329640

Re: Nuklear: A single-header ANSI C GUI library

#18

Post by printf_kek0 » Sat, Feb 10, 2018, 4:20 PM UTC

zevv wrote: post #13

I really do not understand why 'single header' is considered a good thing, but I see this more and more often on libraries. What is the reason all the code is put in the header file?

I would also like an explanation. The author(s) of Musl (libc alternative) mention on this page that it can potentially invoke undefined behavior: https://wiki.musl-libc.org/alternatives.html

However, having used a few of these "single-header" libraries my main concern is navigating a 9000 sloc header file as opposed to a neatly re-factored version...

An explanation of how undefined behaviour is possible would be welcome.

Re: Nuklear: A single-header ANSI C GUI library

#19

Post by mrtweetyhack » Sat, Feb 10, 2018, 4:32 PM UTC

gnud wrote: post #16

I'm guessing this deals with accessibility the same way most other 'light' UI toolkits do - by not dealing with it at all?

I don't see a problem.

Re: Nuklear: A single-header ANSI C GUI library

#20

Post by jsd1982 » Sat, Feb 10, 2018, 4:36 PM UTC

akvadrako wrote: post #12

You can't build a "ANSI C GUI library", because ANSI C has no graphical capabilities.

It is a GUI library written in ANSI C. Graphical capability is not a property of programming languages. It is an orthogonal matter.