00:00:00 --- log: started forth/20.10.17 01:08:23 --- join: [1]MrMobius joined #forth 01:10:29 --- quit: MrMobius (Ping timeout: 246 seconds) 01:10:29 --- nick: [1]MrMobius -> MrMobius 01:29:00 --- join: irsol_ joined #forth 01:30:00 --- quit: irsol (Read error: No route to host) 01:30:06 --- nick: irsol_ -> irsol 01:52:45 --- quit: jsoft (Ping timeout: 272 seconds) 02:29:30 --- quit: _whitelogger (Remote host closed the connection) 02:32:28 --- join: _whitelogger joined #forth 02:38:05 --- join: f-a joined #forth 02:51:24 --- join: X-Scale` joined #forth 02:52:11 --- quit: X-Scale (Ping timeout: 264 seconds) 02:52:22 --- nick: X-Scale` -> X-Scale 03:36:26 --- quit: f-a (Ping timeout: 246 seconds) 03:45:26 --- join: proteusguy joined #forth 03:47:28 --- join: TCZ joined #forth 04:38:47 --- join: f-a joined #forth 04:50:52 --- join: jsoft joined #forth 06:39:20 --- quit: Lord_Nightmare (Ping timeout: 260 seconds) 06:42:21 --- quit: TCZ (Quit: Leaving) 07:20:11 --- quit: Zarutian_HTC (Remote host closed the connection) 07:28:02 --- join: TCZ joined #forth 07:35:36 --- join: Doob joined #forth 07:41:52 Hello all. Is the number of bits in a Forth-number dependent on the processor or the standard? 07:41:56 Just i read old books about Forth, where they work with 16 bits everywhere, and then they expand to 32 and 64 by the Forth itself. 07:49:49 --- quit: jsoft (Quit: Leaving) 08:05:39 Doob: Well, what i think is, it depends on the implementer. If you implement a Forth, you start with what the machine provides and build what you need. Then extend further. 08:09:22 Doob: In the good old time ( ;) ) this might be a 8-bit machine, implementing 16-bit Forth in assembly. Then if needed 32-bit Forth in Forth. 08:12:13 sts-q: Ok. This means that if I make a fort in a high-level language with 64-bit numbers, then I do not need to lower the precision and expand the set of words to 16 bits. 08:14:37 Can I use a data stack for floating point numbers? Or is it necessary to work with them in a special float-stack? 08:15:57 --- part: f-a left #forth 08:17:28 Doob: Floats are data and therefore go on the data-stack, that's fine. 08:21:57 Doob: I think there are Forth standards: ANSI-something and others. I think, it is a good idea, to start with these, if only for the sake of readability. 08:23:41 I didn't find anything about the bit length, only about memory alignment. 08:26:23 Doob: In many languages '+' is '+', no matter if int, int32, float, whatever. Forth needs an operator for each type, there are a lot of them. 08:28:01 http://forth.sourceforge.net/std/fst83/ 08:32:40 http://www.complang.tuwien.ac.at/projects/forth.html 08:32:45 Yeah, but I can hide it from the user. so that the calculation results are correct. I just need to know to what bit size it is critical. 08:33:13 And the existing implementations are confusing. Everyone does it their own way. 08:33:35 :)) Yes 08:34:50 --- join: f-a joined #forth 08:34:58 bit-size, byte-size or word-size? 08:35:59 In 'old' books they should have 16-bit-words. 08:37:13 HTH, need to leave now. Regards. 08:37:37 (bbiab) 08:52:46 --- quit: f-a (Quit: leaving) 08:59:31 --- quit: TCZ (Quit: Leaving) 09:10:47 --- join: Lord_Nightmare joined #forth 09:35:23 --- quit: Keshl (Ping timeout: 264 seconds) 09:36:25 --- join: WickedShell joined #forth 10:21:50 --- quit: Doob (Remote host closed the connection) 11:02:33 --- join: f-a joined #forth 11:20:38 --- quit: Vedran (Quit: The Lounge - https://thelounge.github.io) 11:21:56 --- join: Vedran joined #forth 11:51:43 --- quit: iyzsong (Quit: ZNC 1.7.5 - https://znc.in) 11:52:00 --- join: iyzsong joined #forth 12:15:48 --- join: Mat5 joined #forth 12:20:55 --- part: Mat5 left #forth 13:03:58 --- quit: WickedShell (Remote host closed the connection) 13:04:28 --- join: Gromboli joined #forth 13:17:15 --- quit: gravicappa (Ping timeout: 256 seconds) 13:19:04 --- join: gravicappa joined #forth 13:53:23 --- quit: f-a (Ping timeout: 264 seconds) 13:54:43 --- join: f-a joined #forth 14:39:44 --- quit: f-a (Quit: leaving) 14:56:16 --- quit: gravicappa (Ping timeout: 256 seconds) 15:02:33 --- join: Zarutian_HTC joined #forth 16:01:27 --- join: Keshl joined #forth 16:26:41 --- join: dave0 joined #forth 17:11:51 --- quit: dave0 (Quit: dave's not here) 18:04:23 --- join: WickedShell joined #forth 18:07:49 --- quit: Zarutian_HTC (Remote host closed the connection) 18:08:24 --- join: jsoft joined #forth 18:27:45 --- quit: sts-q (Remote host closed the connection) 18:30:01 --- join: boru` joined #forth 18:30:04 --- quit: boru (Disconnected by services) 18:30:06 --- nick: boru` -> boru 19:54:12 --- quit: Gromboli (Read error: Connection reset by peer) 21:36:36 --- quit: WickedShell (Remote host closed the connection) 22:13:52 --- join: gravicappa joined #forth 22:20:50 --- join: sts-q joined #forth 22:21:13 --- quit: sts-q (Client Quit) 22:21:45 --- join: sts-q joined #forth 23:59:59 --- log: ended forth/20.10.17