00:00:33 <arke> lindi-: keyboard input, screen output. The rest is up to you
00:00:41 <arke> (I'm using int 0x21, al=0x06)
00:03:27 <lindi-> ok
00:03:59 <heatsink> You probably have so few contestants because you chose an esoteric operating system for the contest. ;)
00:10:41 <lindi-> operating system doesn't really play any role here, except for the I/O stuff
00:10:41 -!- arke has quit (Remote closed the connection).
00:10:41 -!- arke has joined.
04:46:40 -!- kipple has quit (Read error: 110 (Connection timed out)).
05:47:53 -!- heatsink has quit ("Leaving").
06:07:14 <cpressey> {^Raven^}: will do
07:59:59 -!- clog has quit (ended).
08:00:00 -!- clog has joined.
10:28:37 <{^Raven^}> thx
12:06:25 -!- kipple has joined.
12:35:59 -!- kipple has quit (sterling.freenode.net irc.freenode.net).
13:49:43 -!- kipple has joined.
14:03:31 -!- puzzlet has joined.
14:07:53 -!- kipple has left (?).
14:35:19 <{^Raven^}> cpressey: minor revison to stream IDs
14:35:56 <{^Raven^}> cpressey: updated version online, Draft Easel API is at http://jonripley.com/easel/api.txt
14:43:37 -!- kipple has joined.
16:30:04 <{^Raven^}> does any one know of any references to use of floating point numbers in esoteric languages?
17:20:52 -!- Keymaker has joined.
17:21:25 <Keymaker> {^Raven^}: fl0at is evlil!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
17:22:10 <Keymaker> by the way, didn't realize your project "completely" until seeing that api list.. sounds great'
17:22:20 <Keymaker> what about using pc-speaker? :)
17:22:34 <{^Raven^}> you can;t tell me that you wouldn't want to floating point arithmetic in, lets say, malbolge :)
17:22:46 <Keymaker> hehe
17:23:02 <{^Raven^}> any thing that I can work out portable C code for is possible
17:23:13 <Keymaker> :)
17:23:18 <{^Raven^}> Beep! is the current limit
17:23:23 <Keymaker> ok
17:24:03 <Keymaker> is beep just "printing" byte 7 (?)?
17:24:06 <{^Raven^}> yup
17:24:09 <Keymaker> ok
17:24:26 <Keymaker> i've seen that as brainfuck program as well :)
17:24:34 <Keymaker> not hard to program :p
17:24:45 <{^Raven^}> :) i've just put the latest version of the API on my site
17:25:06 <Keymaker> ok
17:25:09 <Keymaker> i'll take a look
17:25:43 <{^Raven^}> any comments, suggestions are appreciated
17:26:11 <Keymaker> "cool!"
17:26:32 <{^Raven^}> thx :D
17:27:29 <Keymaker> :) i'm concerned about one thing though
17:27:45 <Keymaker> this far running any esoteric program has been safe
17:27:54 <Keymaker> now, without deep understanding of some program
17:28:05 <Keymaker> one can accidentally open a program that deletes all his files
17:28:18 <Keymaker> or does something not so good..
17:28:23 <Keymaker> :\
17:29:03 <{^Raven^}> i know, it also opens up the possibilities of writing a virus or some other malware :(
17:30:11 <{^Raven^}> i am wondering about making the API request user confirmation of file deletion and system calls
17:30:17 <Keymaker> yeah
17:30:21 <Keymaker> that should be
17:30:43 <Keymaker> in my humble opinion the user should get informed about things that might be harmful
17:30:46 <Keymaker> good idea
17:32:11 <{^Raven^}> question is, should it ask by default or only if an -requestconfirmation (type) switch is given on the command line?
17:32:35 <Keymaker> always
17:32:43 <Keymaker> unless NOT toggled off :)
17:32:55 <Keymaker> that i suggest
17:33:27 <Keymaker> since there are always people who don't read any documents and just assuming the program is safe and people who can't remember to set that kind of stuff on (like me :))
17:34:22 <{^Raven^}> sounds like a very good idea, i will add a -noconfirmation (type) switch to turn off this for known safe programs. It will come in handy for shell scripts where user can specify #!/usr/bin/whatever -safe on the first line
17:35:13 <Keymaker> ok
17:36:19 <Keymaker> -bugmenot :)
17:37:20 <{^Raven^}> lol, how about opening a file for writing/update also being considered unsafe?
17:37:51 <Keymaker> i think so
17:37:59 <Keymaker> at least if it's in the different directory
17:38:39 <Keymaker> although in linux all the problems are smaller, but in windows environment it could mess all :)
17:38:48 <Keymaker> what i am talking.. :D
17:39:12 <Keymaker> i meant "in linux all the problems can't do that much harm by their own"
17:39:18 <Keymaker> or that i guess, at least
17:39:24 <Keymaker> and hope :)
17:39:39 <Keymaker> at least i haven't managed to mess anything yet
17:41:42 <{^Raven^}> same thing about dangerous stuff being possible goes for all mainstream programming/script languages
17:42:04 <Keymaker> sure
17:42:06 <Keymaker> i know that
17:42:14 <Keymaker> that's why i prefer esoteric ones ;)
17:42:37 <{^Raven^}> I wonder if Norton|M'Coffee will ever need to add a detction code for an esoteric nasty !
17:42:44 <Keymaker> :D
17:43:02 <Keymaker> then the cops would be behind your door soon :) or then not..
17:43:08 <{^Raven^}> lol
17:47:51 <Keymaker> anywas, what i was about to say, was this: even there are stuff in other programming languages about file i/o and stuff, and they aren't asked for user to confirm, i still suggest you have there that "ask for confirmation" by default, that can be set off if wanted to..
17:48:31 <{^Raven^}> that's the plan now
17:48:55 <Keymaker> o-k
17:49:57 <Keymaker> by the way, how i would use the stuff in brainfuck program? like for example printing some cell's value in decimal?
17:50:44 <{^Raven^}> PESOIX does not support memory cells, but it's simple to do
17:51:13 <Keymaker> so how it would work in brainfuck then?
17:51:37 <{^Raven^}> (set value)>[-].+.-..<.
17:51:57 <Keymaker> i see
17:52:19 <Keymaker> just like i assumed :)
17:59:15 -!- elysium has joined.
18:03:34 <Keymaker> gotta go. bye
18:03:36 -!- Keymaker has quit.
19:06:20 -!- elysium has quit (Client Quit).
20:15:43 -!- calamari has joined.
20:58:24 <{^Raven^}> hi
22:14:28 -!- calamari has quit (Read error: 110 (Connection timed out)).
23:17:25 -!- cmeme has quit (Read error: 104 (Connection reset by peer)).
23:19:40 -!- cmeme has joined.
23:19:58 -!- cmeme has quit (Read error: 54 (Connection reset by peer)).
23:20:48 -!- cmeme has joined.