00:00:00 --- log: started retro/11.05.01
00:14:42 --- quit: zzing (Ping timeout: 258 seconds)
00:15:07 --- join: zzing (~zzing@CPE0024369fd268-CM0012254195d6.cpe.net.cable.rogers.com) joined #retro
01:37:15 --- quit: zzing (Ping timeout: 240 seconds)
01:37:40 --- join: zzing (~zzing@CPE0024369fd268-CM0012254195d6.cpe.net.cable.rogers.com) joined #retro
03:59:57 --- quit: zzing (Ping timeout: 250 seconds)
04:01:15 --- join: zzing (~zzing@CPE0024369fd268-CM0012254195d6.cpe.net.cable.rogers.com) joined #retro
05:31:21 --- quit: zzing (Ping timeout: 250 seconds)
05:33:01 --- join: zzing (~zzing@CPE0024369fd268-CM0012254195d6.cpe.net.cable.rogers.com) joined #retro
07:19:49 <crc> good morning
07:44:13 <zzing> guten morgen
07:45:03 <zzing> crc, what is your feeling about a statement like "When you are programming, of course, we encourage the use of comments and stack diagrams to make your code more readable."   I am fairly sure I read that Moore would not agree with that statement.
07:50:23 <crc> stack comments are useful, but step by step diagrams are overkill IMO
07:51:26 <crc> I see room for commenting on specific pieces of code, but the comments shouldn't overwhelm the code. comments in separate files are ok
07:52:31 <crc> moore uses comments in shadow blocks
07:53:11 <crc> see http://colorforthray.info/new_site/OkadWork1.html for an example
07:53:37 <zzing> oh yes, blocks... I never quite understood that block system - seems very esoteric
07:54:04 <zzing> ok, that doesn't look evil :p
07:54:46 <crc> I (optionally) support blocks with Retro. files are better in most cases though.
07:57:17 <zzing> When I implement something on hardware, I hope to have files working good
07:57:41 <zzing> The idea is to have a basic forth setup within the chip flash and that it can load the rest from sd