This is as horrific as it is wonderful.
Pretty.c
101–110 of 227 posts
Re: Pretty.c
#102Type names are nice; Perfect choice for the in-built func macros (like min); Len -- love it. Named boolean operators -- might be a bit much but go for it; Ternaries are illegible so you can only improve them; Not completely sold on all your loop definitions but some make sense to me; Resource tracking is impressive; The for... look a bit ugly -- could probably call it something else. All in all: quite a solid attempt…
Re: Pretty.c
#103I cannot wait to show this to a colleague of mine. He will kill me XD
Re: Pretty.c
#104I feel compelled to try it out in a serious way and contribute to it. I have strong knowledge of python and am learning C. Are there good reasons -apart from attracting the ire of c-programmers- to not use it?
Re: Pretty.c
#105love. It.
Re: Pretty.c
#106So sweet :))
Re: Pretty.c
#107Can we just pascal?
Re: Pretty.c
#108Earlier quoted context omitted.
How did you think people outside the US learn programming?
setxkbmap us -option ctrl:swapcaps -option compose:rwin Problem solved. US layout, and with the right Window keys you can compose European characters.
For starters, that they’re on Linux, they feel comfortable running complex CLI commands, they can memorize the U.S. layout just like that, and that they can type without looking at the physical keys (because changing the virtual mapping means keys produce something else than what the label says).
In reality, the learner’s first exposure to C family languages is more likely to be a website where you can run some JavaScript in a text box. And the first hurdle is to figure out how to even type {}. American developers just completely forget about that.
Re: Pretty.c
#109The code asumes that C17 has C++-style auto ( https://github.com/aartaka/pretty.c/blob/master/pretty.h#L11... ), it does not (in C auto is storage specifier that is equivalent to no storage specifier).
Re: Pretty.c
#110> if (argc above 1) I give up.