02:05:18 -!- kpreid has joined.
02:18:47 -!- calamari_ has quit (Read error: 110 (Connection timed out)).
02:29:44 -!- lament has joined.
03:10:11 -!- calamari_ has joined.
04:16:30 -!- calamari- has joined.
04:35:14 -!- calamari_ has quit (Read error: 110 (Connection timed out)).
04:36:53 <calamari-> started on the EsoAPI.. "installation check" is working :)
04:58:33 -!- lament has quit (Read error: 104 (Connection reset by peer)).
06:31:42 <calamari-> cool.. seems to be working now. 24 bytes to spare :)
06:32:56 <calamari-> ; 00h 08h INSTALLATION CHECK, returns 0
07:59:59 -!- clog has quit (ended).
08:00:00 -!- clog has joined.
08:17:32 -!- calamari_ has joined.
08:31:16 <calamari_> okay.. bos 1.00 is on my website: http://lilly.csoft.net/~jeffryj/programs/bf/bf.html
08:33:02 -!- calamari_ has quit ("Leaving").
08:37:23 -!- calamari- has quit (Read error: 110 (Connection timed out)).
18:14:23 -!- calamari has joined.
18:35:08 -!- calamari_ has joined.
18:37:57 -!- calamari has quit (Read error: 110 (Connection timed out)).
21:08:02 <mtve> calamari: wouldn't it be better to add some kind of syncronization? i mean Type/Lenght/Value approach are more extendable.
21:16:21 <calamari_> mtve: ? not sure what you're referring to
21:16:59 <mtve> EsoAPI. there is an escape code 00h (header), type byte.
21:17:27 <mtve> there could probably be a value part. but no lenght, so there will be some hairy protocol,
21:17:49 <mtve> with exceptions, special cases, hard to evolve and so on.
21:18:43 <calamari_> I don't follow you I guess.. are you having trouble understanding how to issue api commands?
21:19:15 <mtve> nope, for now api is very clean and simple.
21:19:58 <calamari_> are you wanting a two character escape code?
21:20:10 <calamari_> where the second char tells how long the escape is?
21:20:16 <mtve> but in case one day you will think about adding new features, it will become more complicated.
21:20:51 <mtve> so it will be versions, (in)compatibility and so on. that's what i mean :)
21:22:20 <mtve> there can be utf8-like approach. 00 00 - 00 7F codes are for one-byte commands, 00 80 xx - 00 BF xx are for 12-bits commands, and so on.
21:22:51 <mtve> i just want to say we could think about it now.
21:23:31 <mtve> sorry, bad math, 14-bits commands.
21:26:16 <calamari_> well, check this out.. 00 05 is free, so use that if you like, 00 05 02 xx xx can be a two byte command
21:26:57 <calamari_> I'm hoping that there will be different versions
21:27:48 <mtve> oh, it's better to be only one API and i think everyone here would like to see _you_ as the keeper/commander for it :)
21:28:11 <calamari_> its GPL, so everyone is commander ;)
21:29:14 <calamari_> unfortunately, bos is maxed out, I think I have about 16 bytes free, not enough to add any more to the api 1.0
21:29:40 <calamari_> I think I gave it enough to write an os using bf commands, though
22:13:32 -!- lament has joined.
22:35:42 -!- calamari- has joined.
22:48:05 -!- calamari_ has quit (Read error: 110 (Connection timed out)).