2021-07-19 04:37:47 <veltas      > siraben: Personally? This new B language
2021-07-19 04:46:18 <siraben     > veltas: B? the predecessor to C?
2021-07-19 04:46:25 <siraben     > or, another B? hehe
2021-07-19 05:54:04 <veltas      > siraben: Yes, the predecessor
2021-07-19 06:35:38 <siraben     > Ah, interesting.
2021-07-19 06:35:43 <siraben     > veltas: what implementations exist?
2021-07-19 07:06:32 <veltas      > Don't know, I think there's at least a couple for modern POSIX systems, there have been a few dotted around for DOS, ATARI etc
2021-07-19 07:06:45 <veltas      > Older ones existed for original UNIX on PDP-11, honeywell, etc
2021-07-19 07:07:11 <veltas      > The B implementations around probably all simulate B's hardware assumptions in a VM
2021-07-19 07:07:28 <veltas      > Whereas I want to change the semantics a bit to generate native code instead
2021-07-19 07:08:00 <veltas      > The other approach to getting native code on byte-addressed machines is adding types, which is the approach C took
2021-07-19 08:37:51 <veltas      > There's just one thing about B which has been confusing me, which is how external vectors vs. external simple variables are handled.
2021-07-19 08:38:30 <veltas      > There are no types, so no special handling can happen between vectors and variables. But a vector is linked by providing the address of vector, and its value is that address
2021-07-19 08:38:50 <veltas      > And a variable provides its address when linking, and its value is indirectly accessed through that address
2021-07-19 08:39:24 <veltas      > I think the way they must have done it is having every vector have a variable that just points to that vector, because I've seen it mentioned elsewhere you can overwrite a vector's pointer
2021-07-19 08:39:47 <veltas      > i.e. you can do   auto a[10], b[10]; a = b; /* now a points to b, rather than its own storage */
2021-07-19 08:40:29 <veltas      > I shouldn't say 'pointer' because that's a C thing, in B they're called addresses
2021-07-19 11:16:23 <cbridge     > -!- ChanServ changed mode/#forth -> +o  ChanServ
2021-07-19 14:53:51 <cbridge     > <mark4> USB_HID [=y]!=y  <-- anyone here know wtf this is saying?
2021-07-19 14:54:02 <cbridge     > <mark4> its part of a depends on a search in menuconfig
2021-07-19 14:54:09 <cbridge     > <mark4> Depends on: USB_HID [=y]!=y && EXPERT [=n] && USB [=y] && INPUT [=y]
2021-07-19 14:54:21 <cbridge     > <mark4> yea everything thats supposed to be Y is Y, everything thats supposed to be N is N
2021-07-19 14:54:35 <cbridge     > <mark4> but the item i am searching for still cannot be found anywhere in menuconfig
2021-07-19 15:06:27 <cbridge     > <mark4> nvm
2021-07-19 15:06:57 <cbridge     > <mark4> freeking search help is broken. the missing menuconfig items suddenlhy appeared when i set USB_HID = M instead of the Y the help says to set it to
2021-07-19 18:39:51 <dave0       > maw
2021-07-19 19:07:57 <cbridge     > <cmtptr> isn't the stuff in braces telling you what it currently is
2021-07-19 19:08:21 <cbridge     > <cmtptr> i know i'm late
2021-07-19 19:08:48 <cbridge     > <cmtptr> and he's not even here
2021-07-19 22:31:47 <dave0       > re maw