Viewing profile — Questron
Questron
HN member- Joined
- Sun, Apr 30, 2017, 11:30 AM UTC
- HN karma
- -9
- Public activity
- 12 items
- HN profile
- View on Hacker News ↗
About Questron
No profile information was provided.
Recent public activity
-
comment
Comment #14267450
If I'm as busy as OP (claims to be), then no way. EDIT: Think about marathon runners: they drink water and electrolytes. I'm pretty sure I can handle a workday fully concentrated w…
-
comment
Comment #14267181
It's: "Look! I'm busy! I'm important! I eat special food!"
-
comment
Comment #14266672
The "more and smaller meals" applies only to people with diseases (diabetes, obesity, etc.). People prone to hypoglycaemia are called diabetics with insulin overdose. Moreover, soy…
-
comment
Comment #14266495
Yes, but three times in 8 hours? I think it's more of an unhealthy habit to constantly eat. That's how you get diabetes.
-
comment
Comment #14266380
Weird. You need food during an eight hour shift?
-
comment
Comment #14254257
You can create closures in CBM BASIC V2 by referencing arrays or creating thunks as an extension. But that's beside the original point. Implementing is not a lot of work but since …
-
comment
Comment #14249966
Not really in machine language or even BASIC (see below).
-
comment
Comment #14248751
Yes, pointers to pointers etc. are difficult to grasp, but then again, so is passing functions as arguments. Also, information wasn't as readily available then as it is now. Anyway…
-
comment
Comment #14248140
Probably hadn't thought of passing a subroutine address to a routine in z80 machine language he was familiar with?
-
comment
Comment #14236633
Only the condition code was removed. Otherwise the parent is right and there really is an enormous amount of instructions. Fortunately less than intel, but still a lot.
-
comment
Comment #14236430
All the different instructions are listed in intel's instruction reference manuals. What is not very wise about this article is that he's using AT&T syntax. It adds one pointless l…
-
comment
Comment #14231071
There's also something else: Try shifting unsigned char x to right. >> 1 through 3 produce correct results, 4 changes the shift to some optimization too early, and the >> 5 the cor…