BinaryByter
bright neon blue with white text
Alignant
Ah, right
Alignant
They were nice
Alignant
Turbo C++ is an IDE and a compiler
Alignant
Those guys didn't do it the UNIX way
Alignant
What did Stallman do wrong? :D
BinaryByter
He wrote emacs
Bader
https://saleemrashid.com/2018/03/20/breaking-ledger-security-model/
Bader
pretty great article
Alignant
Disguised as a text editor~
Alignant
Well, actually... emacs is not a kind of software to which the principle "make small programms taht work together" is applied
BinaryByter
Well, actually... emacs is not a kind of software to which the principle "make small programms taht work together" is applied
Actually all the articles of the bible where people get killed are wrong, we only believe in those articles:
Alignant
Actually all the articles of the bible where people get killed are wrong, we only believe in those articles:
Aren't you know breaking some rules
Alignant
😉
BinaryByter
/ban rms for wrote emacs
Alignant
I hope the disguise module is separated from the os
And of course it is. That's where the lisp comes it. The editor is not that large
BinaryByter
Alignant
He used a separate language(and quite an unusual one) to isolate high level stuff form the kernel
Alignant
You lied, you use comments 😂
Marie
Who dis non-admin telling me what to do?
BinaryByter
I don't use a lot of 'em
BinaryByter
And in general i have to revisit the entire current codebase
Alignant
Just admit they aren't always bad 👌🏻
BinaryByter
For example the namespace comment at the end of a namespace
BinaryByter
For example the namespace comment at the end of a namespace
Vsc makes them for me and i'm too lazy lazy to disable them
BinaryByter
So i can't avoid them
BinaryByter
Oh
Alignant
Comment is a statment that helps you understand what's going on or why it is made like this.
BinaryByter
Yea
Alignant
Not just a pair of slashes
BinaryByter
Welr you should avoid em
BinaryByter
Really
BinaryByter
I didn't know about that when i started on clinl
Alignant
I like to leave a comment if I have to do something in an unusual way. Like... I can't think of a generic rule, but when you work with hardware, you'll always find a piece of junk that can't be dealt with the usual way :D
BinaryByter
BinaryByter
Uck
BinaryByter
It's such a shitpile
Alignant
Oh, I liked your acpi unit test
BinaryByter
I have an acpi unit test?
BinaryByter
Wasnt it... Pretty empty? XD
BinaryByter
I am currently catching up on alr the unit testing we didn't do so far
Alignant
Alignant
It's like backwards TDD
Alignant
Why would I make a test that fails and then make it work
Alignant
I'll just make a test that passes :D
Alignant
And see what I can do about it
BinaryByter
Hahahahaha xDD
Alignant
I'm not judging, you know 😂
BinaryByter
I had to deal with acpi
BinaryByter
Acpi is a little shit
BinaryByter
That wants to kill you at night when you reast expect it
BinaryByter
But first, you gotta implement the AML interpreter
Alignant
Nah, at least it's not UEFI
Alignant
Or is it ;)
Alignant
I saw a doc file describing it. It made me sad
Alignant
But I meant... the day you decide that it'd be nice to have a 64 bit version too
BinaryByter
Of clinl? Yea it's already decided
BinaryByter
As soon as the basics work, we'll switch
Alignant
And why do you always use a magic number 4 as a size of a pointer?
Alignant
Instead of sizof(void*)
Alignant
I'm just not sure, maybe I don't get something
Alignant
Ah, sorry. My memory fails me. You did use sizeof(void*)
Like here static_assert(sizeof(void*)==4, "ix86 assumption to have 32bit pointers not met"); in thread.cpp
I must have invented that you haven't
BinaryByter
Oh yea
BinaryByter
Well qneko is imprementing an arch dependent thing