Egregoros

kinda weird that in C you still have to do -lfoo to link against a system library. I thought the whole point of #include <bar/foo.h> in that style was that the <> indicate to look for it in the system path. Why can't the compiler link them for me?

Crazy that nobody thought to make a C-like language plus like two small improvements. Two pluses, basically. Someone should make that.

@WandererUber everything is manual in C. Headers traditionally only include function prototypes and data type definitions. You can define full functions in a header only if you declare a function with the keywords "static inline" and that is actually a nonstandard extension that is just widely supported. If you declare a function in a header without it you will have link errors if you include it from more than one C file.

@icst @WandererUber C tends to make a lot more sense to people when viewed as being a first abstraction over common assembly patterns. I'm becoming more firm over time in the idea that assembly should be taught before C in order to really "get" it

I like how you guys are explaining it historically as if that's a good reason for it.
The compiler should not be like this anymore is what I am saying. What ends up happening is people write half their program in make and C preprocessor, not C. That's kinda silly. And has basically nothing to do with assembly patterns.

@WandererUber @binkle @icst
ok cool we get rid of the preprocessor, nice libraries are whatever

technically most modern language """compilers""" are wrappers around the proper compiler than handle all of that anyway.

>What ends up happening is people write half their program in make and C preprocessor, not C.
Do you even know what youre talking about