←2005-05-09 2005-05-10 2005-05-11β†’ ↑2005 ↑all
00:24:43 <kipple> I fired up my webserver again, and now it actually seems to work fine...
00:24:54 <GregorR-L> lol
00:25:01 <GregorR-L> Isn't it nice how that goe?
00:25:02 <GregorR-L> *goes
00:25:06 <kipple> maybe it was a one time glitch...
00:25:18 <kipple> or maybe it will go down in a moment....
00:25:25 <GregorR-L> Heheh
00:58:30 <GregorR-L> Well, off to home now.
00:58:52 <GregorR-L> I'll start working on that Kipple interpreter when I get home.
00:58:56 <kipple> bye. i'm off to bed myself
00:59:01 <kipple> cool!
00:59:02 -!- GregorR-L has quit ("Leaving").
03:16:01 -!- GregorR-L has joined.
03:16:12 <GregorR-L> Crapsicles ... Kipple doesn't need to be space-delimited?
03:24:18 -!- kipple has quit (Read error: 145 (Connection timed out)).
04:34:34 -!- Keymaker has joined.
04:34:53 <Keymaker> GregorG: by its stacks?
04:35:06 <Keymaker> well, there isn't said any size for them
04:35:17 <Keymaker> but there is naturally limit
04:35:26 <Keymaker> in the interpreter as well
04:39:51 <GregorR-L> Err, I meant that you can do stuff like:
04:39:56 <GregorR-L> 44>a24>b32>c
04:40:01 <GregorR-L> Rather than:
04:40:04 <GregorR-L> 44>a 24>b 32>c
04:40:21 <Keymaker> yeah the first one is valid
04:40:28 <GregorR-L> blee
04:41:28 <Keymaker> as is the second
04:41:34 <GregorR-L> Well, I knew that.
04:41:36 <GregorR-L> Makes it a bit harder to parse ;)
04:41:38 <Keymaker> :)
04:41:39 <Keymaker> yeah
04:42:35 <Keymaker> but not that much, just remember that stack names are one character (a..z or @)
04:42:44 <Keymaker> and input is digits 0..9
04:43:43 <Keymaker> so if there is for example a<99b>c you can 'easily' detect where the input stuff (99) ends, because there comes alphabet (b)
04:46:11 <GregorR-L> Mmm
04:47:33 <Keymaker> as well remember that a stack can be "connected" with two stuff like a>b<499
04:47:41 <GregorR-L> AHHHHHHHHHHHHHHHHHHHHHHHHHHHH
04:47:43 <GregorR-L> >_O
04:47:49 <Keymaker> :)
04:48:00 <GregorR-L> ORK is not a good language to do this in.
04:48:03 <GregorR-L> Or anything in, for that matter.
04:48:06 <Keymaker> nope
04:48:07 <Keymaker> lol
04:48:15 <GregorR-L> Which is not to suggest that it can't be done.
04:48:18 <GregorR-L> It can.
04:48:21 <Keymaker> yeah
04:48:32 <Keymaker> kipple interpreter in brainfuck would be neat
04:48:34 <Keymaker> but
04:48:40 <Keymaker> the memory size is my problem
04:48:46 <Keymaker> i mean the cell range
04:48:48 <GregorR-L> Yih
04:49:01 <Keymaker> since i like the 8-bit environment
04:49:07 <GregorR-L> :)
04:49:09 <GregorR-L> The original
04:49:11 <GregorR-L> The classic
04:49:12 <Keymaker> it'd be hard to have 32bit cells in that
04:49:13 <Keymaker> yes
04:49:31 <GregorR-L> I prefer 4 trinary bits myself
04:49:34 <Keymaker> to make interpreter for language using 32bit cells would be hard
04:49:40 <Keymaker> :)
04:50:16 <GregorR-L> Actually, 5 trinary bits.
04:50:22 <Keymaker> ok
04:50:23 <GregorR-L> That's 243 possibilities
04:50:29 <GregorR-L> Pretty close to 255
04:50:37 <Keymaker> and.. what's trinary?
04:50:48 <GregorR-L> Binary is 0 and 1, trinary is 0 1 and 2.
04:50:55 <Keymaker> ah yes
04:50:56 <GregorR-L> 0 is false, 2 is true, 1 is undetermined.
04:51:00 <Keymaker> lol
04:51:31 <GregorR-L> Or better yet, 1 is "Uuuhhhhhhhhhhhhhhhhh......"
04:51:41 <Keymaker> :)
04:53:00 <Keymaker> well, good luck with the interpreter
04:53:05 <Keymaker> i must go now
04:53:12 <GregorR-L> Bye
04:53:15 <Keymaker> stupid other-than-computer-time :)
04:53:19 <Keymaker> bye
04:53:19 <GregorR-L> Heheh
04:53:23 -!- Keymaker has quit ("Freedom!").
05:46:06 -!- calamari has joined.
05:51:32 <GregorR-L> hOI
05:51:33 <GregorR-L> Hoi
05:51:39 <GregorR-L> (Good ol' caps lock)
05:53:46 <calamari> how's it going?
06:03:00 <GregorR-L> (ten minutes later, Gregor reappears :-P )
06:03:06 <GregorR-L> Goin' good.
06:03:13 <GregorR-L> I'm busy failing to make a Kipple interpreter in ORK.
06:03:37 <calamari> hehe
06:03:51 <calamari> I haven't been keeping track of what's new in here
06:04:06 <GregorR-L> I'm new 8-D
06:04:37 <calamari> been trying to simplify a roguelike game to its essestials.. not an easy task
06:04:53 <calamari> essentials, even
06:05:06 <GregorR-L> I've been vaguely considering making a Roguelike probabilistic programming language.
06:05:15 <calamari> GregorR-L: did you create a new language?
06:05:16 <GregorR-L> Merely because it would be so unbelievably stupid.
06:05:25 <GregorR-L> Well, lesse ...
06:05:29 <GregorR-L> Last year I made 2L ...
06:05:33 <GregorR-L> I made FYB (see the topic)
06:05:37 <GregorR-L> And I recently made ORK.
06:05:46 <calamari> oh thats right.. you did the corewars thing :)
06:05:50 <GregorR-L> Yup
06:06:08 <calamari> I knew you did something cool recently, I just couldn't remember what it was
06:06:15 <GregorR-L> Heheh
06:07:40 <GregorR-L> Only one person has actually written a program to challenge mine in FYB.
06:07:44 <GregorR-L> Was that you?
06:07:47 <GregorR-L> I can't remember who it was...
06:08:26 <calamari> nope.. I was never good at corewars. I meant to play it, but ended up playing C-Robots instead (they were on the same shareware floppy)
06:08:33 <GregorR-L> Heheh
06:12:27 <calamari> have you written a roguelike game before? Having trouble with dungeon generation. I need something VERY simple, but simple doesn't seem to be giving good results.
06:13:30 <calamari> I'm probably crazy tho.. the entire game will have to fit in 32k, and I have 16k of memory to work with :)
06:13:40 <GregorR-L> DOS?
06:14:00 <GregorR-L> No, I haven't written a Roguelike - my consideration of creating a Roguelike programming language isn't quite the same as making a Roguelike game.
06:14:32 <calamari> not DOS.. Atari
06:14:38 <GregorR-L> Ahh :)
06:14:43 <calamari> how would it differ?
06:15:02 <calamari> are you thinking more of a defined dungeon where the creatures just fight each other to the death?
06:15:04 <GregorR-L> No actual generation of maps - the maps are the programs, so they would be human-made.
06:15:17 <GregorR-L> I don't know how to explain this bizarre idea properly X-D
06:16:06 <calamari> what would memory be?
06:16:24 <calamari> a creature?
06:16:39 <GregorR-L> I haven't quite figured that part out.
06:16:44 <GregorR-L> The creatures would be ops
06:16:54 <calamari> well, it can't be the map, because that wouldn't grow
06:17:03 <GregorR-L> Yeah.
06:17:05 <calamari> the map would probably be the program
06:17:13 <GregorR-L> Like I said ;)
06:17:36 <calamari> rogue has staircases.. so you can have multiple levels (for loops, etc)
06:17:46 <GregorR-L> Yeah, I had already thought about that part.
06:18:01 <GregorR-L> Mainly I'd like to figure out memory before I implement.
06:18:15 <calamari> creatures being memory would be interesting
06:18:30 <calamari> because you can create or destroy them
06:18:43 <calamari> and do operations on them (attack)
06:19:06 <calamari> operators could be their stats
06:19:09 <GregorR-L> I was thinking that the "hero" would be the program pointer. It wouldn't be human controlled, it would wander randomly.
06:21:01 <calamari> it doesn't have to be random
06:21:13 <GregorR-L> No, but that would make it more interesting 8-D
06:21:22 <calamari> you could have a sort of simple AI that decides which creature to attack
06:21:35 <GregorR-L> So it would be predictable, but difficult to predict.
06:21:45 <calamari> I'd image the maps would be more like mazes with intersections where a decision would need to be made
06:23:27 <calamari> I've been wanting to write a fractal programming language (Star Trek).. but can't figure out how it'd work.. can't be a superficial BF model tacked on :)
06:23:36 <GregorR-L> X-D
06:25:29 <calamari> the program instead would have to be a fractal.. but memory would also
06:25:39 <calamari> instead->itself .. bad typos tonight
06:34:37 <GregorR-L> Heheh
06:36:51 * GregorR-L is trying to determine how that works...
06:41:01 <calamari> if you figure it out, let me know.. or better yet, write it :)
06:41:48 <GregorR-L> X-D
07:10:18 <GregorR-L> Yeah, I have no clue how that would work :-P
07:59:59 -!- clog has quit (ended).
08:00:00 -!- clog has joined.
08:42:35 -!- calamari has quit ("Leaving").
08:51:07 -!- GregorR-L has quit (Read error: 60 (Operation timed out)).
13:36:34 -!- kipple has joined.
13:53:06 -!- Keymaker has joined.
13:53:19 * Keymaker reads the log first before writes anything :)
13:53:59 <Keymaker> hmmm
13:54:05 <Keymaker> interesting ideas there (again)
13:54:33 <Keymaker> i have had kinda same idea, although not including any violent fighting..
13:54:56 <Keymaker> like some maze "game" language featuring program pointer travelling in some maze
13:55:02 <Keymaker> and doing stuff
13:55:11 <Keymaker> depending on stuff there is
13:55:17 <Keymaker> but not any rpg crap
13:55:28 <Keymaker> i hate those
13:55:44 <KnX> befunge+tron , everywhere you go, you make a wall , the IP reverse when she meet a wall
13:57:01 <KnX> ( in fact, it'd do hard to loop with such a language :/ )
14:00:22 <Keymaker> hehe
14:01:33 <KnX> the loop should rewrite herself while doing her "usefull" job
14:02:41 <Keymaker> yeah
14:03:02 <Keymaker> but would be pretty hard if every single character/place/whatever would be replaced with a wall
14:03:46 <Keymaker> it'd be pretty hard to fit some replace(x,y,with_this_character) into one character
14:03:56 <Keymaker> unless the area is small
14:04:32 <Keymaker> if there would be for example 20 instructions, it could work the way that the character would be char-20
14:04:50 <Keymaker> then mod 10 to get x coordinate
14:04:58 <Keymaker> hey wait..
14:05:19 <Keymaker> the instruction should be checked first
14:05:47 <Keymaker> with some 255-char
14:06:37 <Keymaker> ..and finally the remaining stuff (after 10 or whatever) would be the y
14:07:10 <Keymaker> if the area is small this kind of thing would work
14:07:46 <Keymaker> and if the instruction would for example just need to move the pointer right then its x and y stuff would be ignored
14:09:05 <Keymaker> 15x15 area (225) and 30 instructions could work :)
14:09:35 <Keymaker> or maybe 15x16 (240) and 15 instructions
14:10:15 <Keymaker> but making the programs do any useful stuff,
14:10:27 <Keymaker> or making a infinite loop
14:11:06 <Keymaker> the instructions would just always need to build the maze back as it were, and the wouldn't get a change to execute any other instructions
14:11:48 <Keymaker> or well
14:12:53 <Keymaker> maybe having 15x15 area (225) (that includes x and y data), and then two instructions that can have 15 values
14:13:24 <Keymaker> that way could be defined what place to replace with what, and what to execute
14:15:16 <Keymaker> as well, could be used, that those x and y values could be used with the current instruction, for example it could print out 16*x+y as character
14:15:44 <Keymaker> as well, could be that if what-to-replace is 0, nothing would be replaced
14:15:57 <Keymaker> instruction zero could be NOP
14:16:09 <Keymaker> and all the "walls" could be NOPs
14:16:38 <Keymaker> that when program pointer goes on it would make stuff automatically NOP while it goes
14:17:19 <Keymaker> with this kind of language highly random looking code could be also made, since the instructions could be anything between 0 and 255
14:17:26 <Keymaker> maybe i'll think more about this..
14:19:20 <kipple> it would be a bit difficult to write instructions 0-31 in the source code, though
14:22:05 <Keymaker> yes
14:22:43 <Keymaker> but what about using hex editor with width 16? :)
14:23:58 <kipple> yes, that would work :)
14:24:47 <Keymaker> :)
14:24:52 <kipple> hmm. how about making a language which ONLY uses control chars? :)
14:25:03 <Keymaker> wow
14:25:07 <Keymaker> neat idea
14:25:18 <kipple> that would make some really ugly source code
14:25:27 <Keymaker> and the instruction depending from which direction the program pointer comes from?
14:25:33 <Keymaker> yah
14:25:53 <Keymaker> probably space could be the traditional NOP there, like in befunge
14:26:02 <Keymaker> very good idea actually
14:26:26 <Keymaker> haha, two insane program language ideas on this channel the past hour :)
14:26:45 * Keymaker starts thinking about this
14:28:03 <Keymaker> if i counted right it would give 16 instructions to use (if having four directions and four instructions for them)
14:28:15 <kipple> huh? four?
14:28:24 <kipple> there are like 30 control chars
14:28:32 <Keymaker> hmm?
14:28:56 <kipple> 0-31 pluss 127
14:29:35 <Keymaker> ah i see what you mean
14:29:36 <kipple> or are they perhaps called something else than "control" chars?
14:29:50 <Keymaker> i was talking about a funge style langauge
14:30:05 <Keymaker> using space as blank and < > v ^ as direction characters
14:30:26 <kipple> ah.
14:30:48 <kipple> that would be cool too
14:30:57 <Keymaker> yeah
14:31:44 <Keymaker> hmm.. would it be possible with only one character to control the direction?
14:31:51 <Keymaker> i mean it would be
14:31:52 <Keymaker> but
14:32:01 <Keymaker> hmmm
14:32:31 <Keymaker> it would cause executing unwanted instructions
14:32:35 <Keymaker> and therefore not good
14:33:01 <Keymaker> but what about two instructions for moving?
14:33:08 <Keymaker> and one for space
14:33:40 <kipple> what do you mean, for space?
14:33:48 <Keymaker> like this
14:33:50 <Keymaker> +
14:33:51 <Keymaker> +
14:33:53 <Keymaker> +
14:33:54 <Keymaker> +
14:33:56 <Keymaker> +
14:34:19 <Keymaker> if the program is in 2d space the instructions can't be this way:
14:34:21 <Keymaker> +++++
14:34:30 <Keymaker> if you see what i mean
14:34:35 <kipple> yes
14:34:44 <Keymaker> ok
14:35:20 <Keymaker> this kind of thing would allow 8 instructions to be executed
14:35:31 <kipple> wouldn't that be much like wierd (or whatever it's called)
14:35:43 <Keymaker> hmmm
14:35:55 <Keymaker> not quite, iirc
14:36:07 <Keymaker> (or maybe perfectly :P)
14:37:20 <Keymaker> iirc in wierd the instruction was defined by the angles the lines of '*' crossed each other
14:37:40 <Keymaker> well, this would be kinda like that
14:37:47 <Keymaker> although more user-friendly
14:38:56 <Keymaker> (whatever that means :))
14:39:34 <kipple> it's usually not the most important thing in an esolang... :)
14:39:51 <Keymaker> yeah
14:40:38 <Keymaker> hmm. i need food (read: noodles)
14:40:46 <Keymaker> i'll be back. soon.
15:04:48 <Keymaker> hmm
15:06:32 <KnX> for information , i decided to separate my befunge core from the funge-space, making a funge-space-librairy which could be usefull for many langages maybe ...
16:14:08 <Keymaker> aaaaaaaaaaargh
16:29:22 <KnX> ?
16:29:53 <GregorR> Of course it's possible to have only one character to control direction flow.
16:29:56 * GregorR references 2L
16:32:16 <Keymaker> hmm
16:33:05 <Keymaker> yes, but iirc the direction can be change in 2l if the first (?) memory cell is zero or non-zero
16:33:31 <GregorR> It's if the current cell - and you can force a direction, like so:
16:33:34 <GregorR> (Copy/paste)
16:33:52 <Keymaker> ok
16:33:53 <GregorR> +
16:33:53 <GregorR> +
16:33:53 <GregorR> > +
16:34:06 <GregorR> In one case, it will turn right. In the other case, it will turn left-left-left
16:34:32 <Keymaker> but in 2l there is one command to execute the instruction, right?
16:34:38 <GregorR> Yeah
16:34:39 <Keymaker> and other to control the pointer
16:34:43 <Keymaker> i was talking about
16:34:53 <Keymaker> language where those would the same
16:34:57 <GregorR> Ohhhhhhhhhhhhhhhhhhhhhhhhh
16:35:10 <GregorR> Only one command, period.
16:35:11 <GregorR> Hmmm.
16:35:43 <Keymaker> like where program pointer would execute different instructions depending where it comes to the direction-changer
16:36:04 <Keymaker> and as far as i can see there is no way to make that kind of language working without it executing un-wanted instructions
16:36:13 <GregorR> Where as in its x-y location?
16:36:27 <Keymaker> sorry? (i can't understand)
16:37:03 <GregorR> Keymaker like where program pointer would execute different instructions depending where it comes to the direction-changer < do you mean the direction it comes from or the location of the next instruction?
16:37:20 <Keymaker> the direction where it comes from
16:37:24 <GregorR> Ahhhhhh
16:37:26 <Keymaker> if it for example comes from left
16:37:46 <GregorR> Yeah, I can't see how that could work, since you would be forced into a direction that wouldn't necessarily do what you want.
16:38:42 <Keymaker> or more like forced to execute unwanted instruction while trying to get the correct direction
16:38:50 <GregorR> Right
16:39:04 <Keymaker> but if having two guiders
16:39:18 <Keymaker> like for example
16:39:29 <Keymaker> '|' and '-'
16:39:59 <Keymaker> wait.. i try to think what i was about to say
16:40:02 <Keymaker> :)
16:40:08 <GregorR> Heheh
16:41:00 <Keymaker> hmm
16:41:02 <Keymaker> forget :)
16:41:07 <Keymaker> that won't work
16:41:26 <GregorR> I think you would need at least 2.
16:41:30 <GregorR> Hence the beauty of 2L ;)
16:41:34 <Keymaker> :)
16:41:36 <Keymaker> yeah
16:41:43 <Keymaker> that is what i thought
16:43:43 <Keymaker> anyways
16:43:50 <Keymaker> hmmm
16:44:17 <Keymaker> no
16:44:18 <Keymaker> hmm
16:44:27 <Keymaker> i think it still doesn't work that way
16:44:42 <Keymaker> like if the direction-changers execute instruction
16:44:56 <Keymaker> you still get unwanted instructions even if you have two of them
16:45:16 <GregorR> You could have a pure-direction-changer and an op-direction-changer.
16:45:43 <Keymaker> hmm
16:49:51 <Keymaker> anyways; GregorR: did you read the log?
16:49:58 <Keymaker> about that maze language ideas?
16:50:44 <GregorR> Briefly, but I didn't quite get it :-P
16:51:05 <GregorR> Unless you're talking about me yesterday ;)
16:51:20 <GregorR> But that was just an allusion.
16:51:27 <Keymaker> heh :)
16:51:35 <Keymaker> yeah, i was solo-talking
16:51:39 <Keymaker> pretty muchly
16:51:47 <Keymaker> probably just writing what came to my mind :)
16:51:54 <GregorR> Heheh
16:52:01 <Keymaker> esotalk :)
16:52:06 <GregorR> Well, I've got to go to school.
16:52:09 <GregorR> See ya later.
16:52:10 <Keymaker> ok
16:52:12 <Keymaker> yah
17:03:29 <pgimeno> hey
17:03:44 <kipple> hi
17:04:46 <pgimeno> {kipple the human}: could you please tell me if {kipple the language} is imperative and 1D?
17:05:14 <kipple> hmm
17:05:29 <kipple> what's the definition of imperative? I think it is, but not quite sure
17:06:00 * kipple is looking up in wikipedia
17:06:02 <pgimeno> I'm not sure I could make up a definition
17:06:14 <pgimeno> but for example, BF is
17:06:18 <kipple> well, it is definately not functional
17:06:19 <pgimeno> Befunge is as well
17:06:41 <pgimeno> is it deterministic?
17:06:45 <kipple> arg. wikipedia is so incredibly slow
17:06:56 <kipple> yes
17:07:05 <pgimeno> k thanks
17:07:35 * pgimeno files the Kipple bookmark into his imperative 1-D deterministic languages folder
17:07:47 <kipple> the stacks are 1 dimentional, but since there are several stacks one could perhaps argue that it is 2D?
17:08:07 <Keymaker> hi pgimeno
17:08:09 <pgimeno> no, I mean, befunge is a 2D language but (say) pascal, basic, etc. are 1d
17:08:14 <Keymaker> it is 1D
17:08:25 <Keymaker> (in case that isn't answered yet :))
17:08:28 <kipple> are there many langs that are not deterministic? I only know of Java2k I think
17:08:30 <pgimeno> :)
17:08:42 <pgimeno> not many... I can recall of three right now
17:08:48 <kipple> ah, yes you mean dimentions in the source code of course
17:08:56 <pgimeno> yeah
17:08:57 <kipple> that is, the IP
17:09:19 <pgimeno> Java2K, Thue and Whenever are the non-deterministic ones I remember right now
17:09:31 <Keymaker> :D
17:09:51 <pgimeno> well, there's Sartre which I'm not sure about
17:12:19 <pgimeno> regarding the discussion about making a 2D language where direction changes are expressed by just one symbol... ever played KBlackBox?
17:12:39 <Keymaker> nope
17:12:41 <Keymaker> what's that?
17:12:53 <pgimeno> it's a guessing game
17:12:57 <Keymaker> hmm
17:13:19 <Keymaker> well.. what kind of?
17:13:21 <pgimeno> there's a 2D "black box" (grid) and you throw "rays"
17:13:33 <Keymaker> hmm
17:13:38 <pgimeno> there are four marbles within the board
17:14:25 <pgimeno> depending on which position the ray reappears, it gives information on where the marbles are
17:14:39 <Keymaker> hm
17:14:50 <pgimeno> the aim is to guess where the marbles are using the least possible number of rays
17:15:25 <Keymaker> ok
17:15:33 <Keymaker> i can see now
17:15:38 <Keymaker> is it a computer game
17:15:40 <Keymaker> or real world game?
17:15:54 <pgimeno> computer
17:15:58 <Keymaker> 'ok
17:16:06 <Keymaker> (i thought so :))
17:16:28 <kipple> sounds like a KDE game. am I right :)
17:16:43 <pgimeno> you are :)
17:16:46 <Keymaker> yeah
17:16:55 <Keymaker> i guessed something like that as well
17:17:05 <kipple> linux game makers are not too creative when it comes to naming games....
17:17:13 <Keymaker> hehe
17:17:51 <pgimeno> the relevant part is this:
17:18:06 <Keymaker> ..?
17:18:09 <Keymaker> :p
17:18:35 <pgimeno> if you throw a ray from the left side of the box, it bounces in a straight angle when the marble is at the northeast of the cell
17:18:54 <pgimeno> it's hard to explain
17:19:47 <pgimeno> anyway it would be a way to make a program pointer bounce in any arbitrary direction, if the positions to its relative left or right can be examined
17:19:53 <pgimeno> like this:
17:19:59 <pgimeno> +
17:20:13 <pgimeno> *********
17:20:18 <pgimeno> *
17:20:20 <pgimeno> *
17:20:30 <pgimeno> got it?
17:20:34 <Keymaker> no
17:20:38 <Keymaker> wait a sec :)
17:20:55 <Keymaker> no
17:21:04 <pgimeno> heh, well
17:21:07 <Keymaker> :)
17:21:10 <pgimeno> the *'s are program flow
17:21:13 <Keymaker> ok
17:21:15 <pgimeno> the + is the direction changer
17:21:23 <Keymaker> ok
17:21:35 <pgimeno> the straight angle turn is due to the presence of the direction changer
17:21:45 <Keymaker> ah
17:22:01 <Keymaker> now i see
17:22:18 <pgimeno> (that's how a ray bounces in KBlackBox too)
17:22:25 <Keymaker> ok
17:23:09 <pgimeno> in KBlackBox, this one makes the ray to return the way it came:
17:23:17 <pgimeno> +
17:23:25 <pgimeno> *********
17:23:30 <pgimeno> +
17:23:45 <pgimeno> as well as this one:
17:23:48 <pgimeno> *********+
17:24:15 <pgimeno> that idea could be used with a 2D esoteric language
17:24:19 <Keymaker> yeah
17:24:24 <Keymaker> pretty cool!
17:24:58 <Keymaker> how about executing instructions?
17:25:11 <Keymaker> should some another character be used to that?
17:25:21 <pgimeno> that's beyond the scpoe of this document ;)
17:25:25 <Keymaker> hehe
17:25:26 <pgimeno> scope
17:25:29 <Keymaker> i have an idea
17:25:36 <Keymaker> oh wait..
17:25:42 <Keymaker> yes
17:25:51 <Keymaker> like the changing of the instruction could happen
17:25:57 <Keymaker> with different turnings
17:26:01 <Keymaker> or whatever
17:26:08 <Keymaker> depending how the program pointer goes
17:26:13 <Keymaker> and instruction would be executed
17:26:25 <Keymaker> when the pointer goes back where it came
17:26:30 <Keymaker> like in this *************+
17:26:56 <Keymaker> this kind of language would take extremely much space but at least beat GregorR's 2L ;)
17:27:32 <pgimeno> hum, a problem with going back in the same way is that the whole way would be undone
17:27:48 <Keymaker> arg
17:27:51 <Keymaker> :D
17:27:56 <pgimeno> unless...
17:28:14 <pgimeno> ugh, that idea looks sooo ugly :)
17:28:20 <Keymaker> :)
17:28:30 <pgimeno> ... the pointer "pushes" the + sign at the time of bouncing
17:28:44 <Keymaker> :D
17:28:54 <pgimeno> so you actually have a self-modifiable program, ΰ la Malbolge
17:29:05 <Keymaker> hehe
17:29:57 * pgimeno eeks away of his own idea
17:33:17 <pgimeno> some day I will take a look at the Alpaca system
17:33:22 <Keymaker> what's that?
17:33:30 <pgimeno> a CA engine
17:33:38 <Keymaker> ?
17:33:42 <pgimeno> CA = Cellular Automaton
17:33:44 <Keymaker> ah
17:33:57 <Keymaker> haven't heard of any Alpace engine
17:34:01 <Keymaker> is it some esolang?
17:34:11 <pgimeno> it's in cpressey's site
17:34:18 <Keymaker> ok
17:34:50 <pgimeno> http://catseye.webhop.net/
17:36:17 <Keymaker> couldn't get there for some reason
17:37:11 <pgimeno> it's a redirector to http://catseye.mine.nu:8080/
17:38:17 <Keymaker> can't get there either :)
17:38:31 <pgimeno> oh
17:38:43 <Keymaker> anyways;
17:38:50 <Keymaker> take a look at this:
17:38:51 <Keymaker> http://koti.mbnet.fi/yiap/preview.png
17:39:05 <Keymaker> i'm trying to make a really simple design for my brainfuck site
17:39:10 <Keymaker> are the colours ok?
17:40:20 <pgimeno> not counting the PREVIEW sign they are :)
17:41:40 <Keymaker> ok :)
17:41:43 <Keymaker> so it's ok?
17:42:28 <pgimeno> I think so
17:43:51 <Keymaker> ok
17:43:53 <Keymaker> :)
17:45:24 <pgimeno> the simplicity of your design can't beat the simplicity of my lack of design ;)
17:45:30 <Keymaker> hehe
17:46:04 <pgimeno> I'm not very aesthetically-oriented, I just care about contents (in case you haven't noted)
17:46:22 <pgimeno> uh, time to go home
17:46:25 <pgimeno> bbiab
17:47:13 <Keymaker> ok
17:47:29 <Keymaker> yeah, i care most about the content as well
17:49:35 -!- GregorR-L has joined.
17:49:43 <GregorR-L> Keymaker: You're living in a dream world ;)
17:50:18 <GregorR-L> (/me was just remembering about the 1-command language)
17:51:09 <Keymaker> NOOOOOOOOOOOOOOOOOOOO
17:51:11 <Keymaker> :D
17:52:02 <GregorR-L> :-P
17:52:26 <GregorR-L> So, does probabalistic count as nondeterministic?
17:52:37 <GregorR-L> Silly question, really.
17:52:39 <Keymaker> i assume so :)
17:52:40 <GregorR-L> Since it is :-P
17:52:55 * GregorR-L is seriously considering making a programming language based on NetHack :-P
17:53:19 <Keymaker> so.. "Tell Me More!!1"
17:54:41 <GregorR-L> lol
17:54:43 <GregorR-L> Basically...
17:54:47 <GregorR-L> Your program pointer is the @...
17:54:53 <Keymaker> i see
17:54:54 <GregorR-L> You build a little array of rooms...
17:54:57 <GregorR-L> And the @ wanders...
17:55:01 <GregorR-L> Every monster is an op...
17:55:13 <GregorR-L> And the doors could be one-way, or only-if-condition, etc, to make loops.
17:55:24 <Keymaker> sounds pretty neat
17:55:40 <GregorR-L> Unfortunately, I haven't quite figured out some of the stranger attributes :-P
17:55:46 <Keymaker> ok
17:56:21 <GregorR-L> Mainly, do I want the data pointer to just be in a stack or tape...
17:56:29 <GregorR-L> Or do I want the data pointer to be your pet >:)
17:56:42 <Keymaker> :)
17:56:47 <Keymaker> pet of course
17:57:28 <GregorR-L> AHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHH
17:57:34 <GregorR-L> NetHackLang = NHL
17:57:39 <GregorR-L> Bad short form :-P
17:57:47 <GregorR-L> I guess that means nothing to a non-north-american.
17:57:50 <Keymaker> hehe
17:57:57 <Keymaker> well i know what it is
17:58:01 <Keymaker> but don't care at all
17:58:18 <GregorR-L> lol
17:58:19 <Keymaker> ice hockey's boring :)
17:58:29 <GregorR-L> Exactly why I don't want that shortform ;)
17:58:35 <Keymaker> :D
17:59:54 <GregorR-L> I'll call it ... The Rogue Language
18:00:05 <GregorR-L> Read with the proper emphasis, that's pretty cool :-P
18:00:13 <Keymaker> :)
18:08:41 <GregorR-L> AHAHAHA
18:08:45 <Keymaker> hm?
18:08:53 <GregorR-L> We're studying turing machines in the class I ought to be paying attention to right now :-P
18:09:00 <GregorR-L> And I can't keep my mind off of brainfuck
18:09:26 <GregorR-L> 2) A TM can be described by: 1) A graph. 2) A brainfuck program
18:09:27 <GregorR-L> :-P
18:09:57 <Keymaker> wow
18:10:04 <Keymaker> did they say that?
18:10:08 <GregorR-L> No ;)
18:10:11 <Keymaker> d'oh
18:10:27 <Keymaker> very cool
18:10:29 <GregorR-L> :-P
18:10:33 <Keymaker> interesting stuff you have there
18:10:43 <Keymaker> is it just a normal university?
18:10:50 <GregorR-L> Yeah
18:11:08 <Keymaker> i hope i can find a good place to get learnin' that stuff the next year
18:11:15 <GregorR-L> Heheh
18:11:23 <Keymaker> or well actually after ~1.5 years
18:11:25 <Keymaker> :)
18:45:25 <Keymaker> well
18:45:33 <Keymaker> must go. see you tomorrow :)
18:45:37 -!- Keymaker has quit ("Freedom!").
19:40:10 -!- puzzlet has joined.
19:47:27 -!- GregorR-L has quit ("Leaving").
20:02:13 -!- puzlet has joined.
20:11:40 -!- Keymaker has joined.
20:11:44 <Keymaker> hi
20:11:50 <Keymaker> managed to get back for a while
20:19:31 <pgimeno> re
20:19:37 -!- puzzlet has quit (Read error: 113 (No route to host)).
20:19:44 * pgimeno is right now working in his own esoteric language
20:20:21 <Keymaker> hmm
20:20:24 <Keymaker> that sounds good
20:20:35 <Keymaker> any break-through yet?
20:20:41 <pgimeno> soon :)
20:20:48 <pgimeno> it'll be Bitxtreme
20:21:16 <Keymaker> neat neame!
20:21:21 <Keymaker> mmh.. extreme..
20:21:24 <pgimeno> it'll be *called* Bitxtreme
20:21:32 <Keymaker> 'ok
20:21:36 <pgimeno> it's actually a company's name but who cares
20:21:40 <Keymaker> hehe
20:54:04 <Keymaker> well.. good nite
20:54:15 -!- Keymaker has quit ("Freedom!").
21:04:54 <pgimeno> done!
21:04:58 <pgimeno> more or less
21:05:02 <pgimeno> a few bits missing
21:06:01 <pgimeno> http://www.formauri.es/personal/pgimeno/prog/esoteric/Bitxtreme.php
21:31:44 <pgimeno> oops, gtg, see you tomorrow
21:39:07 <fizzie> It seems to already have the 0 and 1 bits, what more do you need?
21:41:46 <pgimeno> well, I'm also working in some subtle I/O details... you know, I don't want this spec to be imprecise or incomplete like that of HQ9+ which lacks a specification of the initial accumulator's value
21:42:54 <pgimeno> I think that's worth being mentioned as well
21:50:55 <pgimeno> updated; now I'm really off, bye
23:24:27 -!- puzlet has quit (Read error: 113 (No route to host)).
←2005-05-09 2005-05-10 2005-05-11β†’ ↑2005 ↑all