00:00:00 --- log: started forth/21.06.12 00:15:27 --- quit: gravicappa (Read error: Connection reset by peer) 00:16:36 --- join: gravicappa joined #forth 00:21:11 --- join: proteusguy joined #forth 00:21:11 --- mode: ChanServ set +v proteusguy 00:48:35 skimming in the reference it seems it is how many bits to shift, from 0 to 31, but i'm a newb at best at these things 00:55:38 --- quit: gravicappa (Ping timeout: 240 seconds) 00:58:26 I suspected that too 01:01:10 but it doesn't seem right because the more specific portion of the manual about the thumb version of LSL(immediate) has the 'xx' filled in with 0s and a field for the number of bits to shift by 01:03:37 trying to use an online disassembler is not making things more clear, if I try to fill in those bits I get different instructions but can't seem to find the documentation to back them up 01:07:00 no I think I figured it out now 01:07:48 xx bits become part of the immediate value that says how many bits to shift 01:08:10 it's confusing because the diagrams are broken up in different ways 01:08:43 in different places 01:10:45 --- quit: cbridge_ (Remote host closed the connection) 01:10:57 --- join: cbridge_ joined #forth 01:13:50 it says "in general, a thumb instruction is |opcode 5 bits|rest 11 bits| a thumb instruction starting with '00' looks like |00|opcode 5 bits|rest 9 bits| and an LSL instruction looks like |000|00|imm5|Rm|Rd|" so it even changes from breaking it into something like |00|rest| to something like |000|rest| 01:14:02 naughty document 01:51:32 --- join: gravicappa joined #forth 02:28:55 KipIngram, how does .: differ than smudge? Semantically the same but different memory usage properties? 02:52:04 --- join: Glider_IRC_ joined #forth 02:55:44 --- quit: Glider_IRC (Ping timeout: 258 seconds) 04:49:53 --- quit: Glider_IRC_ (Remote host closed the connection) 05:03:23 --- join: Glider_IRC joined #forth 06:39:12 --- quit: cbridge_ (Remote host closed the connection) 06:39:28 --- join: cbridge_ joined #forth 06:51:10 crc: I also would like to not be relayed via the bridge 06:52:35 --- quit: cbridge_ (Remote host closed the connection) 06:52:51 --- join: cbridge_ joined #forth 06:53:03 siraben: done 06:53:19 No problem 07:01:56 http://forth.works/share/e43d5dd3c1daa8aba95ee58a96bafae4.html was the initial version 07:02:54 The current one is mostly the same, but a bit messier since I added in bridging #retro to oftc as well as freenode/libera 07:05:26 http://forth.works/share/640b0ea7ef33a3e885295aed1cc88a27 is the current one 07:07:11 (I'm working on a cleaner implementation, but have been bogged down with other tasks, so it's not ready yet) 07:33:55 --- quit: Glider_IRC (Quit: Leaving) 07:35:28 --- join: Glider_IRC joined #forth 08:46:16 where is the bridging happening from 08:50:17 Morning, folks! 08:50:24 Happy Saturday! 09:38:43 Good morning (er... evening here... 11:39p BKK time) 10:33:26 --- join: neuro joined #forth 10:33:26 --- nick: neuro -> neuro_ 10:50:51 --- quit: gravicappa (Ping timeout: 255 seconds) 10:51:19 --- join: gravicappa joined #forth 11:01:24 Crab: the bridge runs on one of my servers (forth.works, currently) 11:33:17 Is the bridge written in retro? xD 11:35:40 neuro_: it's partially retro, partially C. The code that processes & relays messages is in retro; the actual connection is managed by `ii`, a fifo-based irc client 11:38:05 neuro_: see http://forth.works/share/640b0ea7ef33a3e885295aed1cc88a27 (and forgive the messiness & repetition; it was a quickly thrown together solution to the problem; a better implementation is coming) 11:47:22 --- join: gustaf joined #forth 12:40:38 --- quit: gravicappa (Ping timeout: 240 seconds) 14:15:24 --- quit: neuro_ (Ping timeout: 245 seconds) 14:51:56 --- join: Glider_IRC_ joined #forth 14:55:15 --- quit: Glider_IRC (Ping timeout: 258 seconds) 18:58:45 Always fun to see examples of other people's code. 19:39:06 I need to get back to work on my system. I got a little busy with work and haven't worked on it in 2-3 weeks now. 19:42:42 I can relate to that; work has been busier than normal for me as well 19:47:52 I still think the most logical next step is to code up the storage management stuff. 19:49:02 That article on hashing crab posted will help - A good hash algorithm plays an important part in this. 20:00:33 hashing crab sounds like a legitimate sea animal 20:30:08 Heh. 20:52:59 aye 21:24:25 --- quit: crab (Quit: WeeChat 3.0.1) 21:36:56 --- join: gravicappa joined #forth 23:59:59 --- log: ended forth/21.06.12