00:00:00 --- log: started forth/05.02.13
00:05:52 --- join: solar_angel (~jenni@HSE-Toronto-ppp167019.sympatico.ca) joined #forth
01:34:58 --- quit: madwork (Read error: 60 (Operation timed out))
01:40:47 --- join: qFox (C00K13S@82-169-140-229-mx.xdsl.tiscali.nl) joined #forth
03:58:25 --- join: samc (~sam@203-114-131-233.inspire.net.nz) joined #forth
03:58:50 --- quit: solar_angel ("later")
04:34:50 --- part: SeaForth left #forth
06:05:52 --- join: Topaz (~top@cerberus.saywell.net) joined #forth
06:31:52 --- join: saon (1000@c-24-129-90-197.se.client2.attbi.com) joined #forth
06:32:52 --- join: SeaForth (~SeaForth@c-24-1-126-202.client.comcast.net) joined #forth
07:13:51 --- quit: samc (Read error: 60 (Operation timed out))
07:15:06 --- quit: qFox (Read error: 104 (Connection reset by peer))
07:22:07 --- join: madgarden (~madgarden@Ottawa-HSE-ppp4082712.sympatico.ca) joined #forth
07:24:28 --- part: SeaForth left #forth
08:18:28 --- join: samc (~sam@203-114-131-151.inspire.net.nz) joined #forth
08:52:27 --- quit: Topaz ("Leaving")
09:25:13 --- quit: Raystm2 (Read error: 104 (Connection reset by peer))
09:28:26 --- join: tathi (~josh@pcp01375108pcs.milfrd01.pa.comcast.net) joined #forth
09:38:34 --- join: zoly (~l@ppp-62-245-163-248.mnet-online.de) joined #forth
09:38:41 <zoly> g'day
09:39:16 <arke> hi zoly 
09:39:31 <zoly> is there anybody with internet explorer, who could check for me the line delimiters it is using with webdrive blocks (jsforth) ?
09:39:51 <zoly> hi arke
09:40:01 <zoly> what was the browser you are using ?
09:40:10 <arke> I could check
09:40:18 <zoly> i can guide you throu it
09:40:25 <zoly> (there's a hex dump you can load)
09:41:51 <zoly> am about to toss server blocks into jsforth buffers, need to know whether the $0a line delimiter i get with firefox applies for other browsers as well
09:42:04 <zoly> (server blocks are not space padded)
09:42:05 <arke> cool
09:42:08 <arke> hook me up with a link
09:42:14 <zoly> http://wiki.forthfreak.net/jsforth80x25.html
09:42:37 <zoly> 8 load
09:42:48 <zoly> (load block support and hex dump)
09:42:59 <zoly> 14 block 256 dump
09:43:12 <zoly> (loads block from server, dumps it)
09:43:32 <arke> the forth isn't loading, its just giving me some javascript error but not telling me what it is ;/
09:43:38 <zoly> now behind  "hex dump )"   there is a line delimiter
09:43:47 <zoly> oh right.
09:43:49 <zoly> my bad
09:43:56 <zoly> just broke it ...
09:44:14 <zoly> now
09:44:21 <arke> make it quick, i have to run in a moment :)
09:44:26 <zoly> (javascript doesn't like  \  for comments ...)
09:44:31 <arke> hah
09:45:11 <zoly> server block read timeout is set to 5 secs, should be ok for you
09:45:17 <samc> is there meant to be two text entry fields?
09:45:23 <zoly> one is just status
09:45:28 <zoly> output only
09:45:36 <zoly> there's a third one below
09:45:41 <zoly> showing the server block buffer
09:45:58 <zoly> with  14...23 block    its contents should change
09:46:14 <zoly> (i load the server blocks dynamically)
09:46:35 <zoly> but, 8 load  would be the best thing to do
09:46:57 --- quit: saon (Read error: 60 (Operation timed out))
09:47:04 <arke> gotta run
09:47:13 <arke> zoly: send me an email with instructions, I'll try it later
09:47:23 <zoly> 8 load    14 block   256 dump
09:48:42 <samc> doesn't work in safari
09:48:51 <zoly> hmm
09:49:26 <zoly> what's it not doing there ?
09:50:01 <samc> the fields are blank
09:50:03 <zoly> (i was warned that reading contents of iframe like i do may cause browser dependecies)
09:50:27 <zoly> samc, no "ok" when pressing return ?
09:50:38 <samc> no ok
09:50:50 <zoly> ok. looks like the same as konqueror 3.3.1
09:51:01 <zoly> 3.3.2 gets input, 3.3.1 doesn't
09:51:12 <zoly> safari is konqueror based, right ?
09:51:22 <samc> yes
09:51:35 <zoly> i tried to fix it for 3.3.1 but no success
09:51:48 <zoly> the key event handler just doesn't get called
09:51:58 <zoly> i'm sorry
09:53:16 <zoly> that problem is not related to the potential browser issues from reading the webdrive blocks
09:53:41 <zoly> which i have to see running on other browsers first.
09:55:32 <samc> shouldn't it still display the heasder if that was the problem
09:55:53 <zoly> on konqueror 3.3.2, it does not work. just tested it
09:56:00 <zoly> header when ?
09:56:55 <zoly> ah.. you mean the forth hello ?
09:57:01 <zoly> and ok prompt ?
09:57:06 <zoly> yes, right
09:57:17 <samc> yes
09:57:33 <samc> ## JS-Forth 0.03 ...
09:58:34 <zoly> it should, yes
09:59:07 <zoly> just tried opera, server block are transferred, but contents aren't read.
09:59:25 <zoly> looks like i'm pretty browser-specific right now
09:59:53 <zoly> just firefox, mozilla, recent netscapes, and the like.
10:00:01 --- part: hyrax left #forth
10:00:37 <samc> at least your not IE specific ;)
10:01:42 <zoly> as far i tried to maintain cross-browser compatibilty, using the same code for all browsers
10:02:02 <zoly> but i might have to check for browser type now with the new stuff
10:02:16 <zoly> i'm not really happy about that
10:03:00 <zoly> but i'm stretching javascript already a bit for what i'm doing now
10:03:25 <zoly> using transitional stuff
10:03:43 <zoly> means, i'm asking for problems ...
10:08:04 <samc> well, good luck, I'm off
10:08:11 --- quit: samc ()
10:19:56 <crc> Hi all
10:20:02 <zoly> hi
10:24:07 <zoly> you didn't sleep long
10:24:12 <zoly> 4.5 hours
10:24:55 <zoly> (or maybe you sleep at more regular times...)
10:25:50 <crc> sleep?
10:26:01 <crc> I slept for a long time :)
10:28:21 <zoly> new project ?
10:28:52 <crc> I'm still working on RetroForth 8.0
10:29:24 <crc> Quite a bit of work is still needed on that...
10:29:41 <zoly> can imagine
10:30:21 <crc> I have finally made a public release though... 
10:30:38 <zoly> would you consider having your server an mine talk to each other, swapping server disk blocks ?
10:30:50 <crc> how would that work?
10:31:09 <zoly> jrom js, i can only read file contents from the same server
10:31:11 <zoly> from
10:31:26 <zoly> so, in order to open blocks on another server, the servers have to sync blocks
10:32:13 <zoly> mine would have forthfreak blocks, and forthworks blocks from your server on its disk
10:32:20 <zoly> your vice versa
10:32:50 <zoly> (provided you would want to share source screens for jsforth)
10:33:27 <zoly> those are just ascii files, named  blk0  blk1 blk2 and so on
10:33:31 <crc> Sounds good to me
10:33:52 <zoly> they sit in a subdir here, and are retrieved through http load
10:34:33 <zoly> in order to read your screen into a jsforth, started from my server, your screens have to be on my server too
10:34:43 <zoly> therefore they need to sync
10:35:01 <crc> how would that be set up?
10:35:20 <zoly> i'm not sure whether read-on-demand, or mirror would be better
10:35:40 <zoly> mirror would be quicker
10:35:47 <zoly> but less up-to-date
10:36:18 <zoly> read-on-demand, maybe through redirection, or ssi
10:36:27 <zoly> mirror would be easy
10:36:54 <zoly> periodic wget for example
10:37:37 <zoly> on demand would be more elegant if there's more servers
10:38:29 <zoly> t'is just small amounts of data, after all
10:38:57 <zoly> average web page is easily 50 times bigger than a forth source screen
10:39:59 --- join: Herkamire (~jason@h000094d30ba2.ne.client2.attbi.com) joined #forth
10:40:01 --- mode: ChanServ set +o Herkamire
10:40:12 <zoly> i want to avoid that starting jsforth from one server would create a source island
10:40:24 <zoly> because only sources from that server are accessable
10:42:14 <zoly> the alternatives are probably too tricky
10:42:43 <zoly> that is, saving interpreter state to cookie, start from other server, restore state, read block
10:42:56 <crc> ick 
10:43:18 <zoly> well formulated
10:44:57 <zoly> (not even sure whether server side includes would works ... possibly not)
10:45:34 <zoly> i'd go or the easiest solution first
10:45:42 <zoly> if desired, it still can be upgraded
10:47:00 <zoly> that would just be, periodically importing remotely updated screens 
10:48:14 <zoly> or, replace "periodically" against "upon opening screens from remote server"
10:50:18 <zoly> "upon opening" means, upon mapping remote server block range into a client block range
10:51:10 <zoly> this needs no hurry because for the moment my remote blocks are read-only anyway
10:55:35 <zoly> read-on-demand would probably be necessary when attempting to tackle peer-to-peer blocks
10:56:51 <zoly> but that's set to be implemented in the future
11:03:54 --- quit: tathi ("skiing")
11:09:19 * crc can't seem to get jsforth to work on forthworks.com :(
11:13:48 <zoly> *crumble*
11:14:05 <zoly> what's it not doing ?
11:16:04 <crc> The browser stops responding
11:17:52 <zoly> on what operation ? did the start messages show ? "ok" prompt ?
11:18:43 <crc> No
11:18:52 <zoly> i'm gonna turn off loading of the initial ifram contents
11:19:15 <zoly> nope.
11:19:21 <zoly> done in the html wrapper
11:20:38 <zoly> memory ?
11:21:04 <zoly> (firefox is using 123 mb here, whereof 57 mb shared)
11:22:45 <zoly> part of the reason for dynamic screen loading is that i try to keep an eye on its memory use
11:23:41 <zoly> earlier versions had mem leaks
11:24:15 <zoly> took up about 900 mb here once
11:24:19 <crc> No change
11:24:54 <crc> firefox is using 58MB
11:25:10 <crc> I have 512MB RAM in this box...
11:25:16 <zoly> that's just jine
11:25:20 <zoly> fine
11:26:04 <crc> Is there anything in the .js that's tied to your server?
11:26:23 <zoly> cpu load goes up to 98% when it stops responding ?
11:26:41 <crc> 33%
11:27:06 <zoly> there are several hardcoded "forthfreaks" but only referencing to url opened in a new browser window.
11:28:00 <zoly> afair, only place environmental info is gathered from external files is reading the screen resolution from the invoking html file. 
11:28:11 <zoly> but sets to 80x25 if that fails
11:28:35 <zoly> reading the resolution creates a dependancy on the file name
11:30:39 <crc> taking that out...
11:30:42 <crc> now it works :)
11:31:06 <zoly> good. that's done in a very clumsy way anyway
11:31:26 <zoly> the sort of code one better gets rid off
11:32:17 <zoly> server blocks reside in relative directory   webdrive/blk<n>
11:32:23 <crc> http://forthworks.com/jsforth/
11:33:02 <zoly> it is updated very frequently 
11:33:36 <zoly> your versions server blocks aren't scanned for end of line, and padded into buf yet
11:34:06 <zoly> would work by now if i wouldn't have talked so much
11:34:19 <crc> I'll try to keep mine in sync with yours...
11:34:45 <zoly> i'll strengthen version numbering policy
11:34:51 <crc> Once rf8 goes to alpha (a few days), I'll see which words I can add to the "retro" vocabulary for JSForth
11:35:15 <zoly> now *that* would be a great thing 
11:36:31 <zoly> i think about dropping most of the integrated help stuff
11:36:58 <zoly> and open that information from external html pages
11:37:15 <zoly> possibly into an iframe
11:37:46 <zoly> keeps it smaller, and easier to maintain
11:37:55 <zoly> the doc, i mean
11:39:58 <crc> :)
11:40:10 * crc is working on some tools to aid in documenting rf8
11:40:12 <zoly> what's the number of core word in retro ?
11:41:27 <zoly> mean, how much to add to the subset which makes up the retro mode right now ?
11:41:43 <crc> I'm not 100% sure
11:42:00 <crc> There are about 120-130 words in RetroForth (other than colors & editor words)
11:42:24 <zoly> that is, about half of them we got now ?
11:42:39 <crc> You have most of them I think
11:43:00 <zoly> now, that's good news :)
11:43:12 <crc> Some of them only make sense on the x86 retroforth anyway...
11:44:18 <crc> '?if' and 'last' come to mind right off the bat...
11:44:56 * crc added a link to his copy of jsforth on forthworks.com
11:45:03 <zoly> i'm working with the author of helforth/FOeRTHchen on another dialect mode
11:45:20 <crc> HelForth was based on RetroForth :)
11:45:30 <zoly> yes
11:45:37 * crc likes FOeRTHchen too 
11:46:46 <zoly> very suited for first steps, interactive rpn and stack toying
11:48:06 <crc> It's similar to the forth I wrote to teach myself the basics of using the stack
11:53:11 <zoly> first steps in most tutorials are about the same, using about the vocabulary minimal forths like foerthchen offer
11:53:29 <zoly> therefore, they come over much less intimidating than full systems
11:54:13 <zoly> the psychological moment, that, with the few pages of introduction, there's already most part of the word list covered.
11:56:07 <zoly> "that's all there is for the start ?" is very likely more tempting to go on to step2 than "do i have to know all those words?"
11:56:17 <crc> Yup
12:02:32 <zoly> tried    8 load     , and then      w     ?
12:03:35 <crc> nope...
12:03:39 <crc> cool :)
12:04:32 <zoly> it isn't limited to dialect/standard subsets now.
12:04:53 <zoly> is more an idea, tested
12:05:19 <crc> I see that you included a varient of RetroEditor :)
12:06:28 <zoly> "integrated", by reusing those words provided anyway.
12:06:32 <zoly> and renamed the  i
12:06:39 <zoly> name collision
12:07:01 <zoly> added line swap and bubbling up/down
12:10:06 <zoly> move may be cmove now btw
12:10:12 <zoly> does retro have move ?
12:11:13 <crc> cmove
12:12:21 <zoly> i made it cmove again. for the rest it should still be retro-compatible ?
12:12:37 <zoly> screen geometry constants...
12:12:52 <crc> looks good to me :)
12:13:17 <zoly> i like it better when sources can compile with different dialects
12:13:42 <zoly> keeps the amount of duplication lower
12:15:24 <zoly> oops.
12:15:35 <zoly> retro mode characters/screen is 1024..
12:16:20 <zoly> oh sure. geometry loaded from screen 8 ...
12:16:26 <zoly> no "mode"
12:21:10 <crc> block size in retroforth is 512 bytes....
12:37:26 <zoly> ok, server blocks seem to work
12:39:48 <zoly> ls    ( after 8 load )  is quick test
13:12:41 <crc> RetroForth/L4 and RetroForth/Native now have hard drive support!
13:14:07 <zoly> per 100000 kb alloted (and written to) mem in js, 4 mb extra mem are assigned to firefox 
13:14:15 <zoly> per 100 kb ...
13:14:39 <zoly> tolerable
13:15:22 <zoly> 40 bytes/cell :)
13:15:48 <zoly> quite some waste
13:19:02 --- join: I440r (~mark4@216-110-82-203.gen.twtelecom.net) joined #forth
13:19:07 --- join: SeaForth (~SeaForth@c-24-1-126-202.client.comcast.net) joined #forth
13:19:39 <zoly> hi
13:20:48 <I440r> hi
13:21:09 <crc> Hi I440r, SeaForth
13:23:54 --- join: aum (~aum@60-234-138-239.bitstream.orcon.net.nz) joined #forth
13:24:03 <crc> hi aum
13:24:29 <aum> hi crc
13:25:30 <crc> RetroForth/L4 and RetroForth/Native now have hard drive support :)
13:26:01 * crc is excited by this :)
13:27:13 <SeaForth> crc, howdie.
13:27:18 <SeaForth> cool.
13:29:31 <crc> Once I add in the serial port and parallel port drivers, it'll be a pretty useable ForthOS for me
13:31:39 <SeaForth> nice.
13:31:45 <SeaForth> on low end x86?
13:32:01 <crc> 386 and newer
13:32:05 <SeaForth> slick.
13:32:12 <SeaForth> Time for me to get my butt in gear and do the PPC port.
13:32:35 * SeaForth just got his premier issue of 'Make' from Oreilly, neat read.
13:33:12 <SeaForth> DIY mag, and kinda fun to read, perfect for a Forth project with PIC, robotic hardware project, or some other DIY project.
13:33:27 <crc> cool
13:34:00 <SeaForth> I'm thinking maybe I can get someone here to do a PIC controller for my DIY windmill.
13:34:08 <SeaForth> then we can coauthor an article for the mag.
13:34:26 <SeaForth> Tim Oreilly has already told me its a go for such article, as well as a solar cabin building article if I want.
13:41:40 --- join: robert (~purple@c-f778e055.17-1-64736c10.cust.bredbandsbolaget.se) joined #forth
13:41:50 <crc> Hi robert
13:41:57 <robert> Hi crc 
13:42:16 <crc> RetroForth/Native and RetroForth/L4 have hard drive support now :)
13:42:17 <robert> Do you happen to have a listing of the words you use in retro, in some easily machine-readable format?
13:42:22 <robert> Nice
13:42:35 <crc> For the 7.x versions, look in doc/TheRetroBook.txt
13:42:39 <robert> Retro, or any other Forth for that matter.
13:42:44 <crc> Section 1.9
13:45:01 <robert> Thanks.
13:45:21 <robert> Typing "words" in gforth gave a better listing. :)
13:45:39 <robert> Wow, it's HUGE.
13:46:09 <crc> what's huge?
13:46:19 <robert> The gforth word list.
13:46:29 <aum> gforth /is/ huge
13:46:31 <crc> try doing "words" in Win32Forth :)
13:46:33 <robert> Yeah.
13:46:41 --- join: Topaz (~top@cerberus.saywell.net) joined #forth
13:46:42 <robert> Don't have Win32Forth.
13:46:43 <robert> Hi Topaz 
13:46:57 <crc> It has over 10,000 words in my copy
13:47:10 <zoly> robert, lynx -dump "http://www.forthfreak.net/dpans/dpansf.htm" | grep "CORE$"
13:47:11 <crc> "words" only returns the first 8,000 or so...
13:47:39 <Topaz> mjello
13:47:47 <crc> Hi Topaz
13:48:05 <robert> "only"? Heh.
13:48:15 <zoly> lynx -dump "http://www.forthfreak.net/dpans/dpansf.htm" | grep "CORE$" | cut -b 28-38 | sort | uniq
13:48:25 <crc> I have about 120 in RetroForth 7.6 IIRC
13:48:33 <robert> The gforth list is enough, but thanks zoly.
13:49:08 <robert> Just going to experiment a bit with dictionary hashing, and I needed some statistics.
13:49:20 <crc> ok
14:04:26 --- join: TheBlueWizard (TheBlueWiz@modem-006.nyc-tc03a.FCC.NET) joined #forth
14:08:43 --- part: SeaForth left #forth
14:09:45 <robert> Hi, TheBlueWizard 
14:10:51 <TheBlueWizard> hiya robert
14:38:07 --- quit: Topaz ("Leaving")
14:41:01 --- join: Topaz (~top@sown-86.ecs.soton.ac.uk) joined #forth
14:41:49 --- quit: aum ()
14:47:37 --- join: Raystm2 (~Ray@adsl-68-93-114-244.dsl.rcsntx.swbell.net) joined #forth
14:48:26 <robert> Hi
14:48:51 <Raystm2> hey robert :) how the heck are old man ?
14:51:57 * robert is watching Simpsons ;)
14:52:14 <Raystm2> :)
14:52:15 <robert> (background task to doing math homework)
14:53:04 --- quit: Topaz (Remote closed the connection)
14:53:07 * Raystm2 has dr zhivago on PBS in background " Some Where My Love" is starting to drive me a little batty . :)
15:35:31 --- join: KB1FYR (~Alex@196-220.suscom-maine.net) joined #forth
15:38:38 <robert> Hi
15:38:58 <robert> Yet another Forth ham.
15:39:07 <KB1FYR> w00t
15:39:09 <KB1FYR> :-)
15:39:29 <KB1FYR> I just found out about forth today, it sounds interesting...
15:39:41 <Raystm2> kc5tja is on #c4th-ot hes a forth ham. :)
15:40:01 <Raystm2> or a ham forth hmm
15:41:06 <KB1FYR> I found about Forth through my research of old computer technology. I want to build a simple Forth machine using TTL logic, then rebuild it using 70s technology :P
15:41:28 <KB1FYR> found out about*
15:42:16 <robert> I guess you've seen this one? http://www.holmea.demon.co.uk/Mk1/Architecture.htm
15:42:22 <TheBlueWizard> KB1FYR: you might want to read the e-book titled "Stack machines" by Phil Koopman
15:42:59 <KB1FYR> ooo it's an ebook!
15:43:06 <KB1FYR> I didn't realize that!
15:43:20 <KB1FYR> yeah robert
15:44:09 <robert> I have been planning building a computer, too, but not that complex.
15:44:25 <KB1FYR> cool
15:44:30 <robert> The design goal would be (1) Somewhat useful, (2) Using few transistors.
15:44:38 <KB1FYR> I would rather build something less complex
15:44:55 <KB1FYR> yeah
15:45:26 <KB1FYR> I want to make something simple so I can eventually replace everything with metal can transistors, core memory, and nixie tubes :D
15:46:24 <robert> "nixie tubes"?
15:46:27 <KB1FYR> yeah
15:46:31 <robert> What's that?
15:46:32 <KB1FYR> Here, I'll get you a link
15:46:47 <robert> Core memory is cool, but...well...a bit hard core for me. ;)
15:46:52 <KB1FYR> http://en.wikipedia.org/wiki/Nixie_tube
15:46:59 <robert> And metal can transistors are expensive :(
15:47:00 <KB1FYR> haha
15:47:00 <robert> Thanks
15:47:02 <KB1FYR> yeah
15:47:05 <KB1FYR> true :-/
15:47:23 <KB1FYR> I'll have to look for a place to get them surplus maybe
15:47:32 <TheBlueWizard> KB1FYR: Google for that ebook with the author's name
15:47:51 <KB1FYR> ok
15:47:59 * Raystm2 remembers nixie tubes
15:48:04 <robert> One cool thing would be to make a simple sequential computer, without jumps.
15:48:14 <robert> The input could be a tape player.
15:49:07 <zoly> KB1FYR: there are schematics of a reengineered novix cpu around. 
15:49:08 <KB1FYR> hmm
15:49:17 <KB1FYR> oh cool
15:49:26 <KB1FYR> I was reading about the Novix somewhere
15:49:28 <TheBlueWizard> zoly: I wasn't aware of that!
15:49:30 <zoly> that one was a forth cpu, built from 4000 gates
15:49:39 <KB1FYR> o.o
15:49:49 <KB1FYR> awesome
15:50:00 <zoly> TheBlueWizard: that is because you're not checking out the forthfreak wiki often enough :P
15:50:26 <zoly> http://wiki.forthfreak.net/index.cgi?ForthCPUs
15:50:32 <zoly> the fcpu1 it is
15:51:51 <KB1FYR> I'm pretty new to computer architecture and stuff... I've only done things with power electronics before, but I think if I can build something based on a schematic then I will be able to learn.
15:54:30 <zoly> though 44 pages schematics ist not exactly of a complexity suited to grasp the design with a flick of your eyes
15:56:18 <robert> Do you happen to know of a processor simple enough to build yourself with (few and common) 74* parts?
15:56:44 <zoly> the brainfuck engine ?
15:58:09 <robert> I'd prefer something with better program control abilities. :)
15:58:35 <zoly> add some opcodes
15:59:17 <zoly> solder iron microcoding
16:00:17 <robert> Very sexy.
16:01:54 <robert> Hmm..
16:02:08 <robert> How useful are these Gate Array Logic devices?
16:02:30 <zoly> as fpgas ? quite so.
16:02:49 <robert> Well, smaller ones.
16:03:07 <zoly> gals ?
16:03:14 <robert> Yes
16:03:27 <robert> Could they be used for ultra-simple microprocessors?
16:03:34 <zoly> some are, well, between those two
16:03:46 <zoly> like, the lattice (older ones at least) devices
16:04:01 <zoly> wouldn't quite call it fpga, but super-gal
16:04:29 <robert> I'm looking at these GAL16/20/22V* chips.
16:04:41 <robert> AND arrays, 64x16 to 132x44
16:04:49 <zoly> complete cpu ? i doubt you can fit one in a single device
16:05:02 <zoly> but i'm not up-to-date
16:05:29 <robert> Well, it doesn't have to be extremely complex. I saw a TTL processor using a GAL chip and a few external chips (counters, mostly).
16:05:49 <robert> http://www.venturalink.net/~jamesc/ttl/
16:11:37 <robert> http://en.wikipedia.org/wiki/GAL <--- heh. 
16:27:48 --- join: saon (1000@c-24-129-90-197.se.client2.attbi.com) joined #forth
16:29:31 <KB1FYR> hio
16:30:24 <robert> Hi saon 
16:30:32 <robert> These GALs seem pretty interesting.
16:31:03 <KB1FYR> Who doesn't find gals interesting :P
16:31:20 <KB1FYR> whee, lame joke...
16:31:38 <saon> hey all
16:32:10 <robert> KB1FYR: Straight GALs and GAYs.
16:32:37 <KB1FYR> o.O
16:45:23 --- quit: eskimo_r (Read error: 60 (Operation timed out))
16:47:10 --- join: hyrax (~das@adsl-64-219-100-33.dsl.lgvwtx.swbell.net) joined #forth
16:49:05 <crc> back
16:49:30 <robert> Hi
16:49:36 <saon> wb
16:56:52 <TheBlueWizard> gotta go...bye all
16:57:09 --- part: TheBlueWizard left #forth
17:37:27 --- join: SeaForth (~SeaForth@c-24-1-126-202.client.comcast.net) joined #forth
17:38:08 <robert> Hi, SeaForth 
17:41:01 <SeaForth> hello
17:52:35 <arke> dotquote updated! dotquote.forthworks.com
17:53:52 <zoly> i couldn't access it few hours ago
17:54:15 <zoly> server timed out, it said
17:55:44 <robert> Hi arke 
18:09:39 --- part: SeaForth left #forth
18:21:41 --- part: zoly left #forth
18:57:03 --- join: I440r_ (mark4@rrcs-24-242-160-169.sw.biz.rr.com) joined #forth
18:57:10 <robert> Hi
19:03:28 <hyrax> hello
19:11:24 --- join: SeaForth (~SeaForth@c-24-1-126-202.client.comcast.net) joined #forth
19:27:10 --- part: SeaForth left #forth
19:57:25 --- join: rsync_ (~pavel@CPE000c41aac435-CM00111ae4f4cc.cpe.net.cable.rogers.com) joined #forth
20:04:32 --- join: asymptote (~dmesg@68.48.8.92) joined #forth
20:06:29 --- nick: KB1FYR -> KB1FYR|HW
20:07:55 <crc> goodnight
20:12:30 --- quit: saon ("Leaving")
20:13:43 --- quit: asymptote ("Leaving")
20:18:51 --- join: crc2 (~crc2@S01060000b45025b0.cg.shawcable.net) joined #forth
20:19:06 --- quit: crc2 (Read error: 104 (Connection reset by peer))
20:58:03 --- nick: rsync_ -> rsync
21:11:05 --- join: thinfu (thin@bespin.org) joined #forth
21:11:05 --- mode: ChanServ set +o thinfu
21:17:59 --- topic: set to 'Forth: One language, many dialects.  #forth - general forth discussion.  #c4th - ColorForth.   #retro - RetroForth.  #c4th-ot - social channel.  #1xforth - a secret channel for 1x forthers.  #concatenative - the category of language that forth belongs to (sorta)..' by thinfu
21:18:05 --- topic: set to 'Forth: One language, many dialects.  #forth - general forth discussion.  #c4th - ColorForth.   #retro - RetroForth.  #c4th-ot - social channel.  #1xforth - a secret channel for 1x forthers.  #concatenative - the category of language that forth belongs to (sorta).' by thinfu
21:22:52 <thinfu> it amuses me that there's at least 6 forth channels :P
21:22:57 <thinfu> but thats good too
21:23:00 <thinfu> variety is the spice of life
21:24:38 --- join: SeaForth (~SeaForth@c-24-1-126-202.client.comcast.net) joined #forth
21:39:52 <Herkamire> how do you change directories to a: in dos?
21:40:53 <SeaForth> cd a:
21:41:13 <SeaForth> ???
21:42:17 <Herkamire> yeah, I tried that. it just prints "A:\" then gives me the C:\> prompt again
21:42:39 <Herkamire> dir a: prints the contents of the floppy
21:42:52 <Herkamire> I don't seem to have a \ key... hope i
21:42:57 <Herkamire> I don't need one
21:45:07 <Herkamire> hah! found it. cdd a:
21:50:18 <thinfu> huh?
21:51:09 <thinfu> missing the \ does make things tricky..
21:51:19 <thinfu> normally i'd do something like cd a:\blah\blah
21:51:31 <thinfu> and cd c:\something\
21:51:35 <thinfu> then move * a:
21:51:37 <thinfu> or whatever
21:52:11 <thinfu> dos doesn't have "cdd"
21:53:29 --- mode: thinfu set -o thinfu
21:56:28 <Herkamire> freedos does
21:56:39 <Herkamire> keyboard is waaaay messed up
21:56:52 <Herkamire> anyway, enough for tonight. I'm off to bed
21:56:54 --- quit: Herkamire ("off to bed")
22:07:46 --- join: saon (1000@c-24-129-90-197.se.client2.attbi.com) joined #forth
22:09:37 --- quit: saon (Remote closed the connection)
22:24:05 --- join: saon (1000@c-24-129-90-197.se.client2.attbi.com) joined #forth
23:59:59 --- log: ended forth/05.02.13