--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/paste/paste.26714	Sun Mar 11 20:40:35 2012 +0000
@@ -0,0 +1,301 @@
+2008-04-26.txt:04:15:49: -!- evincarofautumn has joined #esoteric.
+2008-04-26.txt:04:19:09: <evincarofautumn> Hey there.
+2008-04-26.txt:04:19:46: <evincarofautumn> Fairly dead, then, eh?
+2008-04-26.txt:04:20:00: <evincarofautumn> To be expected.
+2008-04-26.txt:04:20:49: <evincarofautumn> Hm.
+2008-04-26.txt:04:21:04: <evincarofautumn> Well, it's been a while for me, so I figured I'd get back in the swing, you know?
+2008-04-26.txt:04:21:32: <evincarofautumn> Last time I implemented an esolang was...
+2008-04-26.txt:04:21:37: <evincarofautumn> maybe a few years ago.
+2008-04-26.txt:04:21:51: <evincarofautumn> Sho' you right.
+2008-04-26.txt:04:22:10: <evincarofautumn> Ha.
+2008-04-26.txt:04:22:14: <evincarofautumn> Happens to the best of us.
+2008-04-26.txt:04:24:00: <evincarofautumn> Heh.  I'm a senior right now.
+2008-04-26.txt:04:24:17: <evincarofautumn> It's a damn shame the way school gets in the way of learning sometimes.
+2008-04-26.txt:04:24:39: <evincarofautumn> So.
+2008-04-26.txt:04:24:41: <evincarofautumn> Esolangs.
+2008-04-26.txt:04:24:56: <evincarofautumn> I have an idea formulating.
+2008-04-26.txt:04:25:41: <evincarofautumn> Let's see... it's 2d.  There's an execution pointer as a vector offset into the space.  Some standard-issue commands, whatever.
+2008-04-26.txt:04:25:48: <evincarofautumn> But.
+2008-04-26.txt:04:25:58: <evincarofautumn> Execution can be branched.
+2008-04-26.txt:04:26:21: <evincarofautumn> You can have multiple execution pointers running at once.
+2008-04-26.txt:04:26:27: <evincarofautumn> They're guaranteed to run concurrently.
+2008-04-26.txt:04:26:36: <evincarofautumn> If they crash together, they unify into one thread.
+2008-04-26.txt:04:27:01: <evincarofautumn> Hm.
+2008-04-26.txt:04:27:03: <evincarofautumn> Oh, man.
+2008-04-26.txt:04:27:05: <evincarofautumn> Best idea ever.
+2008-04-26.txt:04:27:10: <evincarofautumn> Attractors.
+2008-04-26.txt:04:27:25: <evincarofautumn> There are attractors, toward which a thread moves.
+2008-04-26.txt:04:27:38: <evincarofautumn> The attractor can be moved when the thread reaches a certain position.
+2008-04-26.txt:04:27:43: <evincarofautumn> There's your event-handling code, right there.
+2008-04-26.txt:04:28:02: <evincarofautumn> I think maybe one attractor for each thread?
+2008-04-26.txt:04:28:24: <evincarofautumn> And moving two attractors to the same position guarantees that the threads will crash and unify.
+2008-04-26.txt:04:28:37: <evincarofautumn> I'm on a roll!
+2008-04-26.txt:04:28:52: <evincarofautumn> But to think of syntax...
+2008-04-26.txt:04:28:54: <evincarofautumn> Um.
+2008-04-26.txt:04:28:56: <evincarofautumn> Help.
+2008-04-26.txt:04:29:05: <evincarofautumn> Ack!
+2008-04-26.txt:04:29:08: <evincarofautumn> Help!
+2008-04-26.txt:04:29:13: <evincarofautumn> Yeah...
+2008-04-26.txt:04:29:23: <evincarofautumn> Wait, what am I saying.
+2008-04-26.txt:04:29:30: <evincarofautumn> Basic instruction set before syntax.
+2008-04-26.txt:04:29:38: <evincarofautumn> (It _has_ been a while)
+2008-04-26.txt:04:30:21: <evincarofautumn> Um.  Well, we can assume one thread that starts at (0, 0), attracted to the bottom right of the program.
+2008-04-26.txt:04:30:48: <evincarofautumn> Should vertical and horizontal movement be independent?
+2008-04-26.txt:04:30:55: <evincarofautumn> Otherwise you'd have the problem of rounding.
+2008-04-26.txt:04:35:47: <evincarofautumn> Well, whatever.  This one kind of crapped out on me.
+2008-04-26.txt:04:35:53: <evincarofautumn> I'll sleep on it later.
+2008-04-26.txt:05:11:03: <evincarofautumn> Hello.
+2008-04-26.txt:05:11:23: <evincarofautumn> Too late, must sleep.
+2008-04-26.txt:05:11:29: <evincarofautumn> I'm outta here.
+2008-04-26.txt:05:11:31: -!- evincarofautumn has quit ("ChatZilla 0.9.81 [Firefox 2.0.0.14/2008040413]").
+2008-04-26.txt:23:47:54: -!- evincarofautumn has joined #esoteric.
+2008-04-26.txt:23:48:24: <oklopol> evincarofautumn: i hate you! (but don't worry, it's not real hate)
+2008-04-26.txt:23:48:25: <evincarofautumn> Hello all.
+2008-04-26.txt:23:48:31: <evincarofautumn> Dang.
+2008-04-26.txt:23:48:40: <evincarofautumn> Best.  Greeting.  Ever.
+2008-04-26.txt:23:48:43: <evincarofautumn> Ha!
+2008-04-26.txt:23:48:45: <evincarofautumn> No way.
+2008-04-26.txt:23:48:50: <evincarofautumn> I've already started a spec.
+2008-04-26.txt:23:49:01: <evincarofautumn> And I'm doing a reference interpreter in--
+2008-04-26.txt:23:49:03: <evincarofautumn> get this
+2008-04-26.txt:23:49:07: <evincarofautumn> --QuickBASIC.
+2008-04-26.txt:23:49:09: <evincarofautumn> Yes sir.
+2008-04-26.txt:23:49:14: <evincarofautumn> I feel like abusing myself.
+2008-04-26.txt:23:49:18: <evincarofautumn> And others, matter of fact.
+2008-04-26.txt:23:49:30: <ehird> evincarofautumn: Wow -- you split sentences up MORE THAN ME!
+2008-04-26.txt:23:50:06: <evincarofautumn> ehird--We make eso langs.  We should have eso speech.
+2008-04-26.txt:23:50:34: <ehird> evincarofautumn: I quite like the Queen's English, thanks.
+2008-04-26.txt:23:51:58: <evincarofautumn> Conlangs are great.
+2008-04-26.txt:23:52:09: <evincarofautumn> I was working on an ideographic system for English recently.
+2008-04-26.txt:23:52:14: <evincarofautumn> Worst idea ever, I might add.
+2008-04-26.txt:23:52:18: <evincarofautumn> It's just not built for it.
+2008-04-26.txt:23:54:10: <evincarofautumn> each character represents an idea, carrying with it one or more pronunciations.
+2008-04-26.txt:23:54:15: <evincarofautumn> Like...japanese kanji.
+2008-04-26.txt:23:54:30: <evincarofautumn> oklopol--Oh, it just increments the x and y each execution frame.
+2008-04-26.txt:23:55:01: <evincarofautumn> ...Or decrements, as the case may be.
+2008-04-26.txt:23:56:03: <evincarofautumn> Um...no?
+2008-04-26.txt:23:56:29: <evincarofautumn> x and y movement are independent...
+2008-04-26.txt:23:57:16: <evincarofautumn> if attractor-x > thread-x then thread-x++
+2008-04-26.txt:23:57:21: <evincarofautumn> That kind of thing.
+2008-04-26.txt:23:57:21: <evincarofautumn> Yessir.
+2008-04-26.txt:23:58:11: <evincarofautumn> Yep.  When a turtle walks over a command character, it executes it.
+2008-04-27.txt:00:04:37: <evincarofautumn> No, I get it.
+2008-04-27.txt:00:04:52: <evincarofautumn> The x and y are both changed each frame.
+2008-04-27.txt:00:05:11: <evincarofautumn> So it would go (0, 0), (1, 1), (2, 2), ... (5, 6), (5, 7), (5, 8)
+2008-04-27.txt:00:05:14: <evincarofautumn> etc.
+2008-04-27.txt:00:09:45: <evincarofautumn> Yes, I was just misunderstanding you.
+2008-04-27.txt:00:09:48: <evincarofautumn> Heh.
+2008-04-27.txt:00:10:49: <evincarofautumn> Just a moment, please.  I'm reviewing some college stuff.  ^_^
+2008-04-27.txt:00:13:35: <ehird> evincarofautumn: there's something wrong with your eyes and mouth
+2008-04-27.txt:00:17:39: <evincarofautumn> Pseudo-so.
+2008-04-27.txt:00:17:45: <evincarofautumn> I'm distracted.
+2008-04-27.txt:00:17:47: <evincarofautumn> Just a moment.
+2008-04-27.txt:00:26:47: <evincarofautumn> Okay.
+2008-04-27.txt:00:26:51: <evincarofautumn> Let's do this, yo.
+2008-04-27.txt:00:27:06: <evincarofautumn> And yes, my eyes and mouth have become suspiciously Japanese all o' sudden.
+2008-04-27.txt:00:27:14: <evincarofautumn> Anyhow.
+2008-04-27.txt:00:27:15: <evincarofautumn> Commands!
+2008-04-27.txt:00:28:28: <evincarofautumn> Each thread has only one associated attractor.  I think I may not have made that clear.
+2008-04-27.txt:00:28:57: <evincarofautumn> So I'm thinking something along the lines of...
+2008-04-27.txt:00:29:17: <evincarofautumn> increase attractor jump size, jump attractor up/down/left/right,
+2008-04-27.txt:00:30:22: <evincarofautumn> fork thread (forking creates a new attractor for the new thread at the opposite position on the graph)
+2008-04-27.txt:00:30:45: <evincarofautumn> ?
+2008-04-27.txt:00:31:33: <evincarofautumn> I don't quite follow...
+2008-04-27.txt:00:32:01: <evincarofautumn> Yes...
+2008-04-27.txt:00:32:12: <evincarofautumn> I'm getting there.
+2008-04-27.txt:00:32:45: <evincarofautumn> No, toroidal, with the initial size determined by the maximum line width of the source / number of lines of source.
+2008-04-27.txt:00:33:52: <evincarofautumn> Yeah.  But unlimited in terms of what the programmer can request.
+2008-04-27.txt:00:33:58: <evincarofautumn> Program space is data space.
+2008-04-27.txt:00:34:15: <evincarofautumn> I was thinking of having a stack for inter-thread communication.
+2008-04-27.txt:00:34:26: <evincarofautumn> Nah.  That makes it too easy.
+2008-04-27.txt:00:36:20: <evincarofautumn> The limit _is_ arbitrary.  It's programmer-defined.
+2008-04-27.txt:00:37:58: <evincarofautumn> But then you can't have it wrap around.
+2008-04-27.txt:00:38:06: <ehird> evincarofautumn: yes you can
+2008-04-27.txt:00:38:10: <evincarofautumn> I like the idea of tangly loopy crazy thread interaction.
+2008-04-27.txt:00:38:39: <oklopol> evincarofautumn: have n dimensions, where m of them wrap
+2008-04-27.txt:00:41:21: <evincarofautumn> Hm.  I like my graph quantized.
+2008-04-27.txt:00:41:43: <evincarofautumn> I like 2 dimensions, 2 wrapping.  Then it's standard-issue fungery.
+2008-04-27.txt:00:42:15: <evincarofautumn> Argh.
+2008-04-27.txt:00:42:20: <evincarofautumn> I really don't get how that's useful.
+2008-04-27.txt:00:43:32: <evincarofautumn> Yeah, but I want the finite restriction to be a mark of the program's elegance, of how tiny it can be made to work.
+2008-04-27.txt:00:44:15: <evincarofautumn> If you can get a hello world or a cat working in 2 lines of 5 chars instead of 25 lines of 80, then there's something to be said for the beauty of your code.
+2008-04-27.txt:00:44:43: <evincarofautumn> Besides, we haven't even talked about how this is supposed to be a threaded language.
+2008-04-27.txt:00:45:20: <revcompgeek> evincarofautumn said that he doesn't get how that is useful and i was saying that it wasn't supposed to be useful
+2008-04-27.txt:00:45:20: <oklopol> evincarofautumn: don't be like that, if it can trivially be extended to infinity, please do it, if it can't, it's probably not interesting.
+2008-04-27.txt:00:45:38: <evincarofautumn> Hm.
+2008-04-27.txt:00:45:41: <evincarofautumn> Well.
+2008-04-27.txt:00:46:38: <evincarofautumn> I suppose you could dynamically alter execution *speed* instead of direction, and repeat blocks of code by having unbounded memory to which you copy previously executed code.
+2008-04-27.txt:00:46:39: <oklopol> evincarofautumn: i'm just saying... why not have it infinite, unless you have something like pointer size to stop ya
+2008-04-27.txt:00:47:12: <evincarofautumn> Why not have it finite, when it begins to demand more elegant coding practices?
+2008-04-27.txt:00:47:27: <evincarofautumn> The rate at which the instruction pointer moves through space.
+2008-04-27.txt:00:47:41: <evincarofautumn> Then we're not in funges so much.
+2008-04-27.txt:00:48:15: <evincarofautumn> Well, you could have a position vector coupled with velocity and acceleration, and model the thread's journey through space using gravity.
+2008-04-27.txt:00:48:29: <evincarofautumn> You could have missiles fired from a home base (say (0, 0))
+2008-04-27.txt:00:48:42: <evincarofautumn> And they must reach planets to execute instructions.
+2008-04-27.txt:00:48:46: <evincarofautumn> Whatever.
+2008-04-27.txt:00:50:15: <evincarofautumn> It could, if you're working with reals.  It could just as easily go (0, 0), (2, 2), (4, 4), (5, 5), etc.
+2008-04-27.txt:00:50:25: <evincarofautumn> (5, 6) I mean.
+2008-04-27.txt:00:50:44: <evincarofautumn> I think this isn't really in the spirit of my original concept.
+2008-04-27.txt:00:50:54: <evincarofautumn> Which somebody called forkfunge.
+2008-04-27.txt:00:51:00: <evincarofautumn> I want to keep that feeling.
+2008-04-27.txt:00:52:30: <evincarofautumn> Kind of.
+2008-04-27.txt:00:52:52: <evincarofautumn> The only numbers you get are your location vector and the data pointed to by your parent's location vector.
+2008-04-27.txt:00:53:05: <evincarofautumn> Plus I/O and stack.
+2008-04-27.txt:00:53:18: <evincarofautumn> Stack is just for IPC.
+2008-04-27.txt:00:54:14: <evincarofautumn> I think we're starting to come together on this.
+2008-04-27.txt:00:54:36: <evincarofautumn> I like the devilish idea of attractors.
+2008-04-27.txt:00:54:42: <evincarofautumn> Then you can't control how you get somewhere.
+2008-04-27.txt:00:54:49: <evincarofautumn> You only control where you're going.
+2008-04-27.txt:00:54:56: <evincarofautumn> ...in a manner of speaking.
+2008-04-27.txt:00:55:09: <evincarofautumn> It's not as intuitive as setting a direction, anyway.
+2008-04-27.txt:00:57:17: <evincarofautumn> Bingo, revcompgeek.
+2008-04-27.txt:00:58:03: <evincarofautumn> You know, this idea doesn't seem hard enough, come to think of.
+2008-04-27.txt:00:58:28: <evincarofautumn> s/of/of it/
+2008-04-27.txt:00:59:08: <evincarofautumn> What time zone are you?
+2008-04-27.txt:00:59:31: <evincarofautumn> Ah.
+2008-04-27.txt:00:59:39: <evincarofautumn> I'm -5.
+2008-04-27.txt:01:00:28: <evincarofautumn> Okay.
+2008-04-27.txt:01:00:30: <evincarofautumn> Later.
+2008-04-27.txt:01:01:29: <evincarofautumn> Looking it up right now.
+2008-04-27.txt:01:03:01: <evincarofautumn> Can't find it...
+2008-04-27.txt:01:04:27: <evincarofautumn> Dang.  Should have looked on the wiki.
+2008-04-27.txt:01:04:32: <evincarofautumn> :P
+2008-04-27.txt:01:07:26: <evincarofautumn> Okay.
+2008-04-27.txt:01:07:34: <evincarofautumn> It's interesting.
+2008-04-27.txt:01:08:03: <evincarofautumn> http://esoteric.voxelperfect.net/forum/
+2008-04-27.txt:01:13:29: <evincarofautumn> Hm.
+2008-04-27.txt:01:14:49: <evincarofautumn> Like I said, it's interesting.
+2008-04-27.txt:01:14:55: <evincarofautumn> I tend to prefer more obfuscated things.
+2008-04-27.txt:01:15:29: <evincarofautumn> This seems more...high-level specialisation in lieu of outright obfuscation.
+2008-04-27.txt:01:16:57: <evincarofautumn> I think that's a fine goal.
+2008-04-27.txt:01:17:05: <evincarofautumn> And it certainly is obfuscated to some extent.
+2008-04-27.txt:01:17:07: <evincarofautumn> Yeah.
+2008-04-27.txt:01:17:22: <evincarofautumn> I like the way your cat looks.
+2008-04-27.txt:01:17:46: <evincarofautumn> It's almost understandable...
+2008-04-27.txt:01:17:51: <evincarofautumn> I like that, actually.
+2008-04-27.txt:01:18:13: <evincarofautumn> I think you should be able to figure out how a language works but have a hard time using it nonetheless.
+2008-04-27.txt:01:18:22: <evincarofautumn> esolang, of course.
+2008-04-27.txt:01:18:31: <evincarofautumn> Heh, I know the feeling.
+2008-04-27.txt:01:19:00: <evincarofautumn> The closest I ever came was something called "symbol", which I never released.
+2008-04-27.txt:01:19:19: <evincarofautumn> Yuck in a really cool way, though.
+2008-04-27.txt:01:19:54: <evincarofautumn> None has written anything useful in it by hand.
+2008-04-27.txt:01:20:17: <evincarofautumn> No human, anyway.
+2008-04-27.txt:01:20:21: <evincarofautumn> Heh.
+2008-04-27.txt:01:20:25: <evincarofautumn> Nice.
+2008-04-27.txt:01:20:30: <evincarofautumn> What functionality?
+2008-04-27.txt:01:21:08: <evincarofautumn> What features does your library include?
+2008-04-27.txt:01:21:38: <evincarofautumn> 500:  Project AID does not exist.
+2008-04-27.txt:01:22:38: <ehird> <evincarofautumn> None has written anything useful in it by hand.
+2008-04-27.txt:01:23:07: <evincarofautumn> ehird:Has the news broken and I missed it?
+2008-04-27.txt:01:23:09: <evincarofautumn> Crap!
+2008-04-27.txt:01:23:14: <ehird> evincarofautumn: It was ages ago!
+2008-04-27.txt:01:23:18: <evincarofautumn> Crap!
+2008-04-27.txt:01:23:22: <evincarofautumn> Oh.
+2008-04-27.txt:01:23:24: <evincarofautumn> Of course.
+2008-04-27.txt:01:24:06: <ehird> evincarofautumn: Also - http://esoteric.voxelperfect.net/wiki/Malbolge_programming
+2008-04-27.txt:01:24:41: <ehird> evincarofautumn: There's also a real-loop 99bob in Malbolge.
+2008-04-27.txt:01:25:07: <evincarofautumn> I've seen that one.
+2008-04-27.txt:01:25:17: <evincarofautumn> Nearly crapped my pants.
+2008-04-27.txt:01:25:35: <evincarofautumn> Most loops like to terminate like crazy.
+2008-04-27.txt:01:27:15: <evincarofautumn> Odd.
+2008-04-27.txt:01:27:21: <evincarofautumn> Has it been proven tc?
+2008-04-27.txt:01:28:54: <evincarofautumn> Nice.
+2008-04-27.txt:01:29:11: <evincarofautumn> I was just about to say, I'd like a symbol for the commonly-used loops.
+2008-04-27.txt:01:29:28: <evincarofautumn> Maybe you could eliminate for?
+2008-04-27.txt:01:29:34: <evincarofautumn> That's just me.
+2008-04-27.txt:01:29:36: <evincarofautumn> I never like for loops.
+2008-04-27.txt:01:30:10: <evincarofautumn> It is kind of cute, sitting there all alone, surrounded by line noise...
+2008-04-27.txt:01:33:53: <revcompgeek> or evincarofautumn
+2008-04-27.txt:01:34:07: <evincarofautumn> Ha.
+2008-04-27.txt:01:34:19: <evincarofautumn> I have no opinion, I guess.
+2008-04-27.txt:01:34:26: <evincarofautumn> Or a neutral opinion.
+2008-04-27.txt:01:36:44: <evincarofautumn> Maybe you could offer both, if you can't decide.
+2008-04-27.txt:01:38:15: <evincarofautumn> Call them "Traditional" and "Simplified" after Chinese.
+2008-04-27.txt:01:38:34: <evincarofautumn> Then write a converter in the language ^_^
+2008-04-27.txt:01:40:47: <evincarofautumn> Yes!
+2008-04-27.txt:01:40:50: <evincarofautumn> Yes yes yes!
+2008-04-27.txt:01:40:59: <evincarofautumn> Beautiful!
+2008-04-27.txt:01:42:40: <evincarofautumn> And since the syntax is punctuation-based, you can inline it as much as you want, making it look like normal text.
+2008-04-27.txt:01:42:47: <evincarofautumn> Steganography right there.
+2008-04-27.txt:01:42:59: <evincarofautumn> Heh.
+2008-04-27.txt:01:46:45: <evincarofautumn> Oh wow.  I just found one of my old eso specs.
+2008-04-27.txt:01:48:06: <evincarofautumn> You get...sponges.  Sponges are like variables, but they can absorb an unlimited number of values, string or integer, and you don't know which stored value you'll receive when you 'squeeze' it.
+2008-04-27.txt:01:48:14: <evincarofautumn> Nice.
+2008-04-27.txt:01:48:40: <evincarofautumn> Apart from that, math operations are fairly deterministic...provided you only use single-valued sponges.
+2008-04-27.txt:01:50:02: <evincarofautumn> Sponge Spongey
+2008-04-27.txt:01:50:04: <evincarofautumn> Spongey Absorb Hello World
+2008-04-27.txt:01:50:05: <evincarofautumn> Squeeze Spongey
+2008-04-27.txt:01:50:07: <evincarofautumn> Squish Spongey
+2008-04-27.txt:01:50:08: <evincarofautumn> Splat
+2008-04-27.txt:01:53:10: <evincarofautumn> That's nice.
+2008-04-27.txt:01:53:19: <evincarofautumn> Then they stick out like they're not supposed to be there.
+2008-04-27.txt:01:53:30: <evincarofautumn> Plus you can include any non-} character.
+2008-04-27.txt:01:54:08: <evincarofautumn> ihope:  squeeze outputs a value of a sponge, apparently, and squish undefines it.
+2008-04-27.txt:01:54:50: <evincarofautumn> Well, you don't _have_to obfuscate.
+2008-04-27.txt:01:54:53: <evincarofautumn> It's just fun.
+2008-04-27.txt:01:58:31: <evincarofautumn> Why no?
+2008-04-27.txt:01:58:44: <evincarofautumn> What else do you use {} to do if they were comment chars before?
+2008-04-27.txt:01:58:58: <evincarofautumn> Or are you looking to be able to include uppercase characters in comments.
+2008-04-27.txt:01:59:11: <evincarofautumn> s/\./\?/
+2008-04-27.txt:02:08:19: <evincarofautumn> Barglemash.
+2008-04-27.txt:02:08:25: <evincarofautumn> Oh, wait.
+2008-04-27.txt:02:08:27: <evincarofautumn> You said talk.
+2008-04-27.txt:02:08:31: <evincarofautumn> Hello.
+2008-04-27.txt:02:09:04: <evincarofautumn> I have some bad memories of that I have to deal with.
+2008-04-27.txt:02:09:08: <evincarofautumn> It happened a few lines ago.
+2008-04-27.txt:02:09:12: <evincarofautumn> I don't want to talk about it.
+2008-04-27.txt:02:09:16: <evincarofautumn> ^_^
+2008-04-27.txt:02:13:24: <evincarofautumn> No.
+2008-04-27.txt:02:13:29: <evincarofautumn> Well, maybe.
+2008-04-27.txt:02:13:40: <evincarofautumn> I didn't even ask, and got crazy suggestions.
+2008-04-27.txt:02:14:08: <evincarofautumn> Which, like yours, were unfitting with my original idea.
+2008-04-27.txt:02:14:15: <evincarofautumn> You have to forgive people for being eager.
+2008-04-27.txt:02:15:09: <evincarofautumn> Heh.
+2008-04-27.txt:02:15:21: <evincarofautumn> There are LISP programmers out there who would kill you for saying that.
+2008-04-27.txt:02:16:05: <evincarofautumn> Sho' you right.
+2008-04-27.txt:02:19:27: <evincarofautumn> Bah.
+2008-04-27.txt:02:19:43: <evincarofautumn> I just got into writing a new one of my own.
+2008-04-27.txt:02:20:39: <evincarofautumn> All right.
+2008-04-27.txt:02:21:02: <evincarofautumn> Limited number of variables, unlimited stack.
+2008-04-27.txt:02:21:11: <evincarofautumn> You have to select a variable to perform an operation on it.
+2008-04-27.txt:02:21:35: <evincarofautumn> Otherwise it's locked, and accessing it raises an exception.
+2008-04-27.txt:02:22:23: <evincarofautumn> Yeah.
+2008-04-27.txt:02:22:30: <evincarofautumn> I'm thinking of taking the locking concept to the extreme.
+2008-04-27.txt:02:22:50: <evincarofautumn> Basically there's one unlocked block of program code at startup
+2008-04-27.txt:02:23:05: <evincarofautumn> and the interpreter loops through the entire source until all of the blocks are locked.
+2008-04-27.txt:02:23:17: <evincarofautumn> Blocks are named, and can be locked/unlocked arbitrarily.
+2008-04-27.txt:02:23:36: <evincarofautumn> Yep.
+2008-04-27.txt:02:23:52: <evincarofautumn> I could call it mutex.
+2008-04-27.txt:02:24:14: <evincarofautumn> Come to think of it, that's just what I'll do.
+2008-04-27.txt:02:24:17: <evincarofautumn> Yeah.
+2008-04-27.txt:02:24:35: <evincarofautumn> Hm.
+2008-04-27.txt:02:24:47: <evincarofautumn> I have to get working on this.
+2008-04-27.txt:02:25:11: <evincarofautumn> I'll toss it on the wiki today or tomorrow.
+2008-04-27.txt:02:25:50: <evincarofautumn> All right.
+2008-04-27.txt:02:25:54: <evincarofautumn> Guess I'm outta here then.
+2008-04-27.txt:02:26:07: <evincarofautumn> It's been nice talking.
+2008-04-27.txt:02:26:13: -!- evincarofautumn has quit ("ChatZilla 0.9.81 [Firefox 2.0.0.14/2008040413]").
+2008-04-27.txt:16:07:13: -!- evincarofautumn has joined #esoteric.
+2008-04-27.txt:16:07:35: <evincarofautumn> Word, folk.
+2008-04-27.txt:16:14:31: <ehird> hello evincarofautumn
+2008-04-27.txt:16:14:39: <ehird> evincar
+2008-04-27.txt:16:16:57: <ehird> evincarofautumn: no?
+2008-04-27.txt:16:31:46: -!- evincarofautumn has quit (Read error: 110 (Connection timed out)).
+2008-04-27.txt:16:43:52: -!- evincarofautumn has joined #esoteric.
+2008-04-27.txt:16:46:03: <evincarofautumn> Okay.
+2008-04-27.txt:16:46:13: <evincarofautumn> Now that my internet has stopped dying.
+2008-04-27.txt:16:47:28: <ehird> evincarofautumn: /nick evincar
+2008-04-27.txt:16:47:41: -!- evincarofautumn is now known as eoa.
+2008-04-27.txt:16:49:41: <ehird> eoa: evincar is easier to type
+2008-04-27.txt:16:51:35: <ais523> eoa is easier to type than evincar
+2008-04-27.txt:16:51:56: -!- eoa is now known as evincar.
+2008-04-27.txt:16:52:09: <ehird> evincar: you'll probably want to register that
+2008-04-27.txt:16:53:53: <evincar> Heh.  Thanks.
+2008-04-27.txt:16:54:16: <evincar> How should I cat this?
+2008-04-27.txt:16:55:11: <evincar> I'm thinking Languages, Low-level, Unimplemented, 2008?
+2008-04-27.txt:16:56:04: <ais523> evincar: I think that lang's a push-down automaton
+2008-04-27.txt:16:56:41: <evincar> Numbers are unbounded.
+2008-04-27.txt:16:57:02: <evincar> Cools.
+2008-04-27.txt:16:57:09: <evincar> Not quite a tarpit, though.
+2008-04-27.txt:16:59:08: <evincar> Ha!
+[too many lines; stopping]