kelas

8 ms·

31.
by kelas 3y ago
> Whitney is an unrealized IOCCC champion. no, that'd be fabrice bellard, who is actually a "realized" ioccc champ. atw doesn't do obfuscated c. you are led astray.
32.
by kelas 3y ago
you must have seen a lot of code.
33.
by kelas 3y ago
"contributors" is essentially me. what needs to be clarified? it is by arthur whitney. anything else?
34.
by kelas 3y ago
> How do we pick up that writing style. since the discussion here revolves around "intentionally obfuscated c", i'd like to recommend three sources which elucidate what obfuscated c is: 1. this is not how you want to write
35.
by kelas 3y ago
> math notation is indeed high-yield and low-effort low-effort is perhaps “your mileage may wary”, as they say :) but the yield per square inch of paper does indeed make math the most powerful and expressive language known to humans. On
36.
by kelas 3y ago
> represents his coding style the most i agree that atw’s inequality test is a bit cheeky, but like everything else it is a matter of habit. a convention. eventually you just begin to see what is subtraction and what is comparison. here’
37.
by kelas 3y ago
> statically typed APL that’d be a curious case indeed, why not, only it won’t be APL even remotely :)
38.
by kelas 3y ago
> C is a historical accident strong words. in the context of civil aviation, for example, there is a fine line between incident and accident. in our context, an accident is COBOL/ABAP, which is, thank god almighty, not as ubiquitous
39.
by kelas 3y ago
true. only k is faster, easier to learn, and does the trick :) that said, i hold the view that mastering programming in an ultra-high level language such as APL or k does not absolve a computer programmer from learning lingua franca of our
40.
by kelas 3y ago
guys, my two pennies: most beginners have no idea what they want. but what we know is that what they don’t want is to produce more endless ugly and buggy code into the world - we’ve produced enough of that before they learned how to locate
41.
by kelas 3y ago
sir, please - make an effort. recover that audio. it is a f%ck#g shame that CHM failed to do their job and lost the legendary footage of the celebration of KEI. Arthur took the last word and opened with the iconic line “deeds of great men d
42.
by kelas 3y ago
> soon to be lost to obscurity well, about that i’m just not so sure. as we like to say, “skill”, for whatever reason you chose to use quotes, cannot be easily bought on a Turkish fish market. there are people out there who write atwc, a
43.
by kelas 3y ago
> please do now that i think of it, i already did just that once, only forgot. getting old sucks, and also forgetting things is a great skill i learned from atw. as he likes to say, “kelas, ignorance is bliss”. Here you go - all you ever
44.
by kelas 3y ago
> README good idea, why not for a more throw-me-in-the-water introduction, here are my notes on another famous public domain release from atw. some remarks are specific to the codebase, but essentially it is a general introduction to atw
45.
by kelas 3y ago
One possible way is to look at a header file i once gave to a 13yo girl. ever since she says she has no idea why people write tall c: https://github.com/aaalt/altc
46.
by kelas 3y ago
porting from k&r to iso is super easy. fun, too.
47.
by kelas 3y ago
> not obfuscated absolutely not. porting it to ISO C was a very fun and smooth ride, also added two adverbs atw forgot to add in 1989 (see over/scan) and a header file with some handy accesssors (atw usually does that, but he was la
48.
by kelas 3y ago
> The code in C that suppose to be written like this is usually never written first like that usually not. but we prefer to write it first this exact way, and there are good reasons for rhat. > obfuscated c it is not. this style is ex
49.
by kelas 3y ago
> k is a fancy calculator [put your favorite Java here] is also a fancy calculator by the virtue of Turing completeness. what’s your point?
50.
by kelas 3y ago
(author of the modern port here) > Arthur Whitney is a mad genius atw is atw :) our old man is awesome. a bit grumpy at times, but then who isn’t :)
51.
by kelas 3y ago
as of yet, it doesn’t shine quite as bright as current C/rv64 original. but as they say, a long road begins with a single step.
52.
by kelas 3y ago
Thanks, that’s what I expected, but I don’t think I’m poorly received. It came out pretty positive and insightful. Hopefully not just for me.
53.
by kelas 3y ago
I think I see your point. Thing is, a C program can be built and executed without that cargo dependency pyramid sandwiched into a gigantic runtime polyp. The whole operating system is your environment, and yes - if ‘man ldconfig’ is not you
54.
by kelas 3y ago
> The paper is entirely free. That's why I posted a link. Go read it. It's not very long, it's interesting, it's accessible, it's provocative and insightful and profound… …and I already read it and you already ha
55.
by kelas 3y ago
> No, [C is not a high-level assembler], and it hasn't been for about 40 years. «C Is Not a Low-level Language Your computer is not a fast PDP-11.» some dude in ACM Queue Please correct me if I’m wrong, but this ACM rant seems to am
56.
by kelas 3y ago
> True, but when making an OS, assembly code is an incredibly small part of it. A few comments up this thread i briefly mentioned r/xv6 entry.S, so here’s what i meant: rv64: https://github.com/mit-pdos/xv6-risc
57.
by kelas 3y ago
> Different things entirely yes, they are. > System-specific packages have no concept of C building or linking. every day i learn something new, but this time around I’m gonna go ahead a tell you that you are very mistaken. > Thing
58.
by kelas 3y ago
Sounds expensive, thanks. So: Preface to the Digital Edition of Kernighan and Ritchie's The C Programming Language Oct 31, 2012 “… Remarkably, in spite of all of this change, C retains a central position. It is still the core language
59.
by kelas 3y ago
thanks, this is useful, let me ponder. obviously i am also a subject of severe cognitive bias, granted. but ok, if not uart driver - what other direct comparison in r/xv6 kernel spaces you would use to show where rust shows a real hard
60.
by kelas 3y ago
+1 only xv6 gives traps, stack, uart, kalloc, preemptive scheduler, rudimentary fs, init(0) and minimal userland out of the box. students are not expected to implement any of that, it is hard - instead, is a book to read, a beautiful one. a

More ›