364 karma · joined May 22, 2019
Also: embedded linux / C++ development
Contact: hn -at- ayaken.net
Previously: type safety x unit safety
Previously: semantic mediation in production networks
Previously: embedded linux development for industrial automation
History: - Tcl -> Scheme -> C -> C++ -> C -> Common Lisp -> C -> Clojure -> Tcl -> C/++ & wanting zig (unimportant deadends like e.g. ruby, icon, python, perl elided)
- DOS 4.11 -> Win 3.11 -> Win95 -> Linux -> NetBSD -> Linux -> FreeBSD -> Linux (those damn hardware drivers)
"Lisp Programmers know the value of everything and the cost of nothing."
C programmers ought to know the cost and sizeof everything...
I hope the committee sees it like this as well.
I also believe the feature (auto) makes sense for C++ with its verbose and lengthy types nobody but your compiler cares about (say, e.g., multimap::equal_range). For C? Get out of here..
this passes, and suddenly zig becomes a whole lot more interesting ;) (but zig also has type inference you say? Well, it's a consistent proposition, and not a tacked-on "feature".)
D'oh. Who writes a lisp with macros where you can't use macros at macro-expansion-time??
struct A { int a, b, c};
you need to do this: A a = { .a = 1, .c = 3};
but you can't do this: A a = { .c = 3, .a = 1};
because... well, because C++. There is no reason to disallow the second form except for .. what exactly? What is the reasoning of the C++ committee to not be able to mirror what one can do in C (where, aside of the missing typedef or "struct" in front of A, both forms are valid)?Just as you're saying, the C++ committee seems to be confused about order-dependent and named initializations, and for some love-of-bean-counting insist that named initialization needs to respect order _as well_.
// Point2D point2d {.y = 2, .x = 1}; // (1) error
Oh my. The C++ committee keeps their flight altitude rivaling moles and worms. This is another brittle feature, just like the initializer lists that have to mirror the declaration order. In what world is this a better option than allowing any order? Can't compiler implementors be bothered or what is the rationale?? C does this better.I've been using racket quite a lot lately, really like it. The thing I do not like about racket is the whole "racket 2" effort. Abandon S-exps? Really? To leave behind the 'popularity boundaries' of lisps? d'oh How about you drop your common USP that you share with the other lisps to become .. what, exactly.. irrelevant?
Cf. your 'dialect' point: In reality, the languages are just (supposed to be) DSLs for specific (sub-)problems of your problem-space. I don't mind, at all. You just require the libraries written in that other dialect from racket and use the stuff in there, et voila.
...anyways, moving on with my life...
Nowadays, I am happy to see a few bees around.
I think we are just too "busy" to step back, open our eyes and actually watch the world we live in.
I value individuals and companies sharing their developments with a community. One has to remember though, to own something is different from benefitting from other's work, and if you want to have a say, you'll need to get your hands dirty, fork, and work.