# HG changeset patch # User HackBot # Date 1379600526 0 # Node ID 4f4a5d5b5fdabde694245d3fb3ad8fb563ce59dc # Parent 65bc17a60b02cfd031d0685bfdb2ab4f86b3ceb1 pastelogs updog diff -r 65bc17a60b02 -r 4f4a5d5b5fda paste/paste.3990 --- /dev/null Thu Jan 01 00:00:00 1970 +0000 +++ b/paste/paste.3990 Thu Sep 19 14:22:06 2013 +0000 @@ -0,0 +1,301 @@ +2007-01-17.txt:00:48:32: http://esolangs.org/wiki/Dupdog +2007-01-17.txt:00:55:23: http://esolangs.org/wiki/Dupdog +2007-01-17.txt:00:55:46: http://esolangs.org/wiki/Dupdog +2007-01-21.txt:08:18:49: time to implement dupdog +2007-01-24.txt:03:10:33: it needs dupdog! +2007-03-16.txt:17:00:19: * ais523 has just written a Dupdog interpreter +2007-03-16.txt:17:01:39: I don't have any Dupdog programs to test it on, though +2007-03-16.txt:17:15:59: "...Because dupdog is only capable of storing a single value (the source code itself) in memory at a time, which may correspond to a finite set of 256 states..." +2007-03-16.txt:17:56:08: (i.e. a program in another language that generates Hello World in Dupdog) +2007-03-16.txt:18:09:34: ais523 and I have been figuring out how to do something vaguely useful in dupdog (http://www.esolangs.org/wiki/Dupdog) +2007-03-16.txt:18:54:36: wait, most Dupdog programs don't care if they're duplicated, as long as they end up with the right length +2007-03-16.txt:18:58:01: lament: the esolang page is here: http://www.esolangs.org/wiki/Dupdog +2007-03-16.txt:19:08:15: Actually... the best way to think about a half-finished Dupdog program is as a sequence of commands at the start, commands at the end, and a /length/ for the whole thing +2007-03-16.txt:19:39:20: all i can see so far is that dupdog really likes printing the fourth character. +2007-03-16.txt:19:59:52: -!- ais523 has quit ("Sorry I couldn't get that Dupdog Hello, World! to work"). +2007-03-16.txt:21:27:09: RodgerTheGreat: http://www.esolangs.org/w/index.php?title=Dupdog&diff=6607&oldid=6606 +2007-03-16.txt:22:25:14: writing a dupdog interpreter directly in perl should be trivial. +2007-03-16.txt:23:45:20: apropos haskell, the Data.Sequence module seems eminently suited for optimizing Dupdog, since it can concatenate in logarithmic time +2007-03-16.txt:23:45:37: and what's dupdog? +2007-03-16.txt:23:47:01: dupdog: it's hip and trendy! +2007-03-17.txt:00:40:50: i fast-forwarded the whole conversation as pointless... then at some point found out dupdog does a modulo when outputting making it sensible... but decided not to read again :P +2007-03-17.txt:00:46:25: * oerjan throws his beginning Dupdog implementation in the garbage bin. +2007-03-17.txt:20:39:44: shut up with your proposals and explain dupdog +2007-03-17.txt:20:40:12: dupdog is completely useless.... I can't even figure out how to do Hello, World! with it. +2007-03-17.txt:21:12:52: ...so..... what's the idea behind the dupdog program? Found any properties that can be exploited? +2007-03-17.txt:21:17:40: dupdog was a strange attempt at playing with the semtantic interpretation of syntax. +2007-03-17.txt:21:21:36: dupdog isn't very conceptually awesome... so I think my next attempt in that area will involving concurrently running interpreters on the same characters. +2007-03-17.txt:22:18:08: i don't see why dupdog with even wrapping cannot work, you can use duplication to turn odd into even and both Mfit and Shanty can do that. +2007-03-18.txt:02:13:40: I dunno, it seems somehow less elegant than dupdog +2007-03-18.txt:02:56:00: ....I could take a dupdog-ian approach that doesn't use tokens. +2007-03-18.txt:02:59:50: the more this new language becomes like dupdog, the more fun I predict programming with it shall become +2007-03-18.txt:03:00:05: I still think Dupdog *might* be tc +2007-03-18.txt:03:03:35: (Dupdog interpreter) +2007-03-18.txt:03:05:53: heh, funny that dupdog remained unnoticed for a couple of months... :) +2007-03-18.txt:03:21:31: ...dupdog is like, the laziest invention ever. +2007-03-18.txt:03:45:43: RodgerTheGreat, where is the Haskell interpreter for dupdog at? +2007-03-18.txt:03:46:25: * SevenInchBread lost interest in dupdog... so never got around to fully fixing his implementation. +2007-03-19.txt:11:56:32: * ais523 apologises for not providing the source code to their Dupdog interpreter +2007-03-19.txt:11:57:25: But now, it's in the pastebin: http://pastebin.ca/raw/401416 (Dupdog interpreter), http://pastebin.ca/raw/401410 (Thutu2 wimpmode; work in progress) +2007-03-22.txt:18:45:53: SevenInchBread: Your new Dupdog-like language with a name I can't remember or type: do you think Wiki Cyclic Tag would be suitable as a language in it? Your new language provides the framework needed to make it Turing-complete by itself +2007-03-22.txt:19:00:54: The basic idea was to create dupdog with a huge number of interpreters instead of two... but I'm too lazy to do that - thus I turned it into a collaboration. :) +2007-03-26.txt:22:56:55: crashmatrix: BF, ///, SevenInchBread's earlier project dupdog, OISC, etc +2007-03-26.txt:22:59:25: Idea: promote dupdog to make engineers go wow instead of Vista :) +2007-03-26.txt:23:04:29: not completely impossible, you wrote hello world in dupdog, didn't you? +2007-03-26.txt:23:11:08: anybody got the dupdog interpreter? +2007-03-26.txt:23:17:35: dupdog was spawned in about a minute... I put no thought whatsoever on how it could be used. +2007-03-26.txt:23:24:30: -nod- that sounds right... that part of the spec was invented as I was writing the interpreter... so it's not actually a requirement to be "pure dupdog" - or whatever. +2007-03-26.txt:23:41:43: i also have my own dupdog interpreter in python +2007-03-26.txt:23:42:24: The files are oerjan.nvg.org/esoteric/Dupdog.hs and oerjan.nvg.org/esoteric/FingerTree.hs (third party module) +2007-03-26.txt:23:45:01: my interpreter: z3.ca/~lament/dupdog.py +2007-03-26.txt:23:55:07: heh.... since dupdog reverses its source code often... does that make it reversible? +2007-03-26.txt:23:59:41: FWIW, the command to actually run a dupdog program is like: runStateT (runErrorT (runLoop (tracer 30 []) 0)) (initPState (DS "" "?~" 257 0 0 30 [] False True)) +2007-03-27.txt:00:25:21: if dupdog were Turing complete... I'm sure it's very likely that mfit or shanty alone isn't +2007-04-22.txt:00:40:31: and the only one I can find of Dupdog is in some illegible compiled Perl stuff. +2007-04-22.txt:00:47:15: http://oerjan.nvg.org/esoteric/Dupdog.hs + FingerTree.hs. You can in theory use it if you can put the right functions together... +2007-04-22.txt:01:04:29: actually you don't need push for Dupdog... +2007-04-22.txt:02:16:25: (untested dupdog interpreter) +2007-06-11.txt:19:57:49: I'm also a big fan of dupdog and /// for essentially that reason +2007-06-22.txt:18:27:21: It was around the time we were playing around with dupdog, if you feel like searching the logs +2007-06-23.txt:03:48:54: (and I've conquered Dupdog, damnit!) +2007-07-12.txt:15:19:37: this reminds me of the Dupdog hello world project +2007-07-12.txt:19:10:48: fine then, check out Dupdog. +2008-01-10.txt:21:54:09: CakeProphet: you made dupdog? you might like this then, it's self-rewriting +2008-01-10.txt:21:55:10: CakeProphet: dupdog isn't turing complete, though +2008-01-10.txt:21:59:17: I actually have no clue what dupdog is. +2008-01-10.txt:22:00:07: dupdog is interesting in that it's not interesting in anyway, but somehow seems cool :D +2008-01-10.txt:22:05:22: the state of a dupdog program is... the source code itself. +2008-01-11.txt:01:02:38: btw: a good excersize would be a dupdog interpreter. +2008-01-12.txt:03:01:35: I think I shall make another language like dupdog +2008-01-28.txt:20:43:47: nobody's figured out how to code in Xigxag, nor do anything but constant-string output in Dupdog, but neither is known to be programmable in at all +2008-07-21.txt:01:05:10: ...dupdog is a very bad example. +2008-07-21.txt:01:06:29: dupdog literally just used the entire source code +2008-07-21.txt:01:11:40: ...ahahaha... functional dupdog. +2008-09-18.txt:21:56:26: that's from the dupdog times +2008-09-18.txt:21:58:05: that's where dupdog comes from +2008-09-18.txt:21:58:22: dupdog is great though +2008-09-18.txt:21:59:02: i think dupdog is tc +2008-10-17.txt:23:22:32: was it the dupdog hello world maybe +2008-10-17.txt:23:22:37: dupdog? +2008-10-17.txt:23:22:56: Dupdog, yes. +2008-11-03.txt:19:34:57: BF interp? dupdog interp? +2009-07-23.txt:00:56:51: excepting maybe Dupdog and Xigxag +2009-12-23.txt:11:59:05: it's sort-of, dupdog range in our analogy +2009-12-23.txt:11:59:14: dupdog? +2009-12-23.txt:11:59:22: http://esolangs.org/wiki/Dupdog +2009-12-23.txt:12:00:36: ais523, it says unknown computational class for dupdog +2009-12-23.txt:12:01:11: dupdog's much nastier than slashes +2009-12-23.txt:13:29:56: i'm pretty sure i've pondered dupdog +2009-12-26.txt:10:39:02: Dupdog? +2009-12-26.txt:10:42:12: and it's hard to see how to do that for dupdog +2009-12-26.txt:11:03:48: ais523, so what about implementing dupdog in that PDA language and then using the PDA->splinter compiler? would that be easier or harder than splinter directly do you think? +2009-12-26.txt:11:15:02: I suspect dupdog can't be done by a PDA +2009-12-26.txt:11:17:41: ais523, but dupdog doesn't have stdin? +2009-12-26.txt:11:18:03: AnMaster: exactly, which is why LBA doesn't even make any sense wrt dupdog +2009-12-27.txt:10:17:06: Btw, anyone trying to prove dupdog sub TC could try to implement it in Total FP. +2009-12-27.txt:10:21:14: ehirdiphone: dupdog in Total FP seems unlikely. after all iirc it is pretty clear that some dupdog programs don't terminate +2009-12-27.txt:11:06:16: Btw, anyone trying to prove dupdog sub TC could try to implement it in Total FP. <--- I have been thinking about various sub-TC languages, and I can't think of a way. Plus what oerjan said later. +2010-04-13.txt:23:09:57: or dupdog +2010-04-13.txt:23:10:08: hardly anyone's heard of dupdog +2010-04-13.txt:23:10:24: which one was dupdog now again? +2010-04-13.txt:23:10:42: http://esolangs.org/wiki/Dupdog if you need a link +2010-07-28.txt:16:39:40: like the whole TCness of Xigxag/Dupdog? +2010-07-28.txt:16:40:13: Had not heard of Dupdog before. +2011-01-01.txt:19:26:24: -!- updog has joined #esoteric. +2011-01-01.txt:19:26:31: Boy, I've got a massive plate of updog right here. +2011-01-01.txt:19:26:31: What's updog? +2011-01-01.txt:19:26:40: I don't know, updog. What *is* updog? +2011-01-01.txt:19:26:40: What's updog? +2011-01-01.txt:19:26:47: updog is edible? +2011-01-01.txt:19:26:47: What's updog? +2011-01-01.txt:19:27:57: i have some suspicions about updog +2011-01-01.txt:19:27:58: What's updog? +2011-01-01.txt:19:29:52: In Newspeak updog is doubleplusgood. +2011-01-01.txt:19:29:52: What's updog? +2011-01-01.txt:19:30:55: hmm updog's got broken +2011-01-01.txt:19:30:55: What's updog? +2011-01-01.txt:19:31:10: -!- updog has quit (Remote host closed the connection). +2011-01-01.txt:19:32:11: -!- updog has joined #esoteric. +2011-01-01.txt:19:33:01: AW DAMMIT UPDOG WHY DO YOU HAVE TO BE SO UPDOG +2011-01-01.txt:19:38:57: -!- updog has quit (Remote host closed the connection). +2011-01-01.txt:19:39:27: -!- updog has joined #esoteric. +2011-01-01.txt:19:39:56: Updog! +2011-01-01.txt:19:39:56: What's updog? +2011-01-01.txt:19:41:44: -!- updog has quit (Remote host closed the connection). +2011-01-01.txt:19:41:54: -!- updog has joined #esoteric. +2011-01-01.txt:19:42:23: Updog +2011-01-01.txt:19:42:24: What's updog? +2011-01-01.txt:19:43:13: -!- updog has quit (Remote host closed the connection). +2011-01-01.txt:19:43:56: -!- updog has joined #esoteric. +2011-01-01.txt:19:43:59: -!- updog has quit (Remote host closed the connection). +2011-01-01.txt:19:44:19: -!- updog has joined #esoteric. +2011-01-01.txt:19:44:36: updog is in Ruby. +2011-01-01.txt:19:44:36: What's updog? +2011-01-01.txt:20:02:29: ais523: i have a lot of updog lying around, can you take care of it? +2011-01-01.txt:20:02:29: What's updog? +2011-01-02.txt:17:07:30: What's updog? +2011-01-02.txt:17:07:30: What's updog? +2011-01-03.txt:00:02:00: * Sgeo glares at updog suspiciously +2011-01-03.txt:00:02:01: What's updog? +2011-01-03.txt:00:02:12: I wrote updog in like five minutes Sgeo :P +2011-01-03.txt:00:02:13: What's updog? +2011-01-03.txt:00:02:49: elliott, updog, or the updog part of the script? +2011-01-03.txt:00:02:49: What's updog? +2011-01-06.txt:07:37:09: And updog's presense here disproves my theory +2011-01-06.txt:07:37:09: What's updog? +2011-01-06.txt:07:37:34: hm i thought it could be updog too... +2011-01-06.txt:07:37:34: What's updog? +2011-01-06.txt:07:39:36: * Sgeo glares at the kicked updog menacingly +2011-01-06.txt:07:40:32: So yeah, updog feeds shutup +2011-01-06.txt:17:18:59: hm did updog crash? +2011-01-06.txt:17:20:03: ok, looks like updog being kicked broke shutup since they run on the same service supervisor +2011-01-06.txt:17:20:40: elliott, you're still trying to hide shutup being fed by updog? +2011-01-06.txt:17:20:42: shutupdog +2011-01-06.txt:17:21:41: oerjan: you realise that updog is a0 +2011-01-06.txt:17:21:59: and since it didn't shut up when _you_ were away, updog was the main suspect +2011-01-06.txt:17:23:25: Prove it. Run shutup without running updog +2011-01-06.txt:17:24:17: ok, clearly updog isn't _banned_ +2011-01-06.txt:17:24:40: of course not, poor updog never did anything wrong +2011-01-06.txt:17:27:02: -!- updog has joined #esoteric. +2011-01-06.txt:17:28:53: but i won't bother if you're going to kick updog +2011-01-06.txt:17:28:54: What's updog? +2011-01-06.txt:17:29:43: oerjan: so are you going to ban updog if i restart the instance so that shutup unbreaks? +2011-01-06.txt:17:29:44: What's updog? +2011-01-06.txt:17:30:22: -!- updog has quit (Remote host closed the connection). +2011-01-06.txt:17:32:07: -!- updog has joined #esoteric. +2011-01-06.txt:17:33:13: Vorpal, updog was kicked for an experiment to see if shutup would stop reacting to my Newspeak and Active Worlds obsessions +2011-01-06.txt:17:33:13: What's updog? +2011-01-06.txt:17:36:31: Vorpal: i can even imagine him being honest about what code updog is running, as long as he has something listening in between :) +2011-01-06.txt:17:36:31: What's updog? +2011-01-06.txt:17:38:59: of course it doesn't have to be updog. +2011-01-06.txt:17:39:00: What's updog? +2011-01-06.txt:17:39:20: but it _is_ suspicious that it stopped when i kicked updog. +2011-01-06.txt:17:39:21: What's updog? +2011-01-06.txt:17:40:03: Of course, if elliott wanted, he could switch it over to him then remove updog, as a "demonstration" that it wasn't updog +2011-01-06.txt:17:40:04: What's updog? +2011-01-06.txt:17:41:25: Sgeo: and now you are applying your learnings to updog +2011-01-06.txt:17:41:26: What's updog? +2011-01-06.txt:17:43:27: >updog< Factor +2011-01-06.txt:17:43:27: What's updog? +2011-01-06.txt:17:45:25: elliott, I'd ask you how that even makes sense in any way whatsoever other than updog being the source, but +2011-01-06.txt:17:45:26: What's updog? +2011-01-06.txt:17:48:38: oklopol, well, given the evidence, there's a LOT pointing to updog currently being the accomplice +2011-01-06.txt:17:48:38: What's updog? +2011-01-06.txt:17:58:33: Phantom_Hoover, feel free to test shutup by msg'ing updog +2011-01-06.txt:17:58:34: What's updog? +2011-01-06.txt:18:06:45: cheater99, if elliott's telling the truth, AND updog and shutup are running on it... he's failing miserably +2011-01-06.txt:18:06:45: What's updog? +2011-01-06.txt:18:07:40: In order for you to be telling the truth about updog not being shutup's source, shutup must be confusing updog's input with its own +2011-01-06.txt:18:07:40: What's updog? +2011-01-07.txt:20:10:47: updog +2011-01-07.txt:20:10:47: What's updog? +2011-01-13.txt:02:06:43: elliott, we all know that shutup's source is updog +2011-01-13.txt:02:06:43: What's updog? +2011-01-13.txt:02:07:40: I think the bug where updog doesn't distinguish between msgs to the channel and to it hurts you even more +2011-01-13.txt:02:07:40: What's updog? +2011-01-13.txt:02:09:24: I think the bug where updog doesn't distinguish between msgs to the channel and to it hurts you even more <-- hah +2011-01-13.txt:02:09:24: What's updog? +2011-01-17.txt:22:30:53: updog +2011-01-17.txt:22:30:53: What's updog? +2011-01-17.txt:22:30:59: what is updog +2011-01-17.txt:22:30:59: What's updog? +2011-01-17.txt:22:32:01: What's updog? +2011-01-17.txt:22:32:01: What's updog? +2011-01-18.txt:01:22:10: -!- updog has quit (Remote host closed the connection). +2011-01-18.txt:14:59:49: ais523: well, I wiped it to run updog before, so "no", but yes, you could get it trivially +2011-01-18.txt:15:00:10: hmm, is updog like dupdog? +2011-01-18.txt:15:00:22: ohey. where did updog go and what did it do while it was here? +2011-01-18.txt:15:00:34: I took it down, and it replied to messages containing updog with "What's updog?" +2011-01-18.txt:15:14:23: ohey. where did updog go and what did it do while it was here? <-- we also suspect it of doing some secret message passing, thereby annoying elliott :D +2011-01-22.txt:22:37:50: updog +2011-02-04.txt:23:26:22: So is updog. +2011-03-14.txt:14:03:03: I still don't know whether Dupdog is turing complete or not +2011-03-14.txt:16:04:09: i certainly cannot recall proving dupdog definitely non-TC +2011-03-14.txt:16:09:23: Gregor: Quick, add !dupdog so that oerjan can start proving. +2011-03-14.txt:16:11:27: ais523, so is it a CA or TM what? I think I need to read up on dupdog +2011-03-14.txt:16:11:39: what, dupdog? +2011-03-14.txt:16:12:29: what, dupdog? <-- I thought you were talking about dupdog above +2011-03-14.txt:16:13:11: dupdog was one mentioned, but so were Xigxag and the 2,3 machine +2011-04-27.txt:20:14:22: Vorpal: dupdog +2011-05-16.txt:04:32:55: updog? +2011-07-04.txt:00:38:48: i think i briefly considered if they were useful for implementing dupdog +2011-09-05.txt:08:58:55: so you have the same code being evaluated by possibly different interpreters. Like dupdog but not as a stupid. +2011-09-12.txt:09:27:27: help make dupdog TC +2011-10-13.txt:21:35:59: i recall i tried genuine Data.FingerTree for http://oerjan.nvg.org/esoteric/Dupdog.hs +2011-10-13.txt:21:36:46: oerjan: lol dupdog. +2011-10-13.txt:21:37:07: I've considered creating a new language based on dupdog, but I have absolutely no idea how to make it interesting. +2011-10-13.txt:21:45:35: okay so... the question for improving upon the concept of dupdog is. +2011-10-13.txt:21:52:32: in dupdog +2011-10-13.txt:21:54:18: I would think that an efficient dupdog interpreter is actually somewhat difficult. +2011-10-13.txt:21:59:39: elliott: i am wondering if Data.FingerTree is lazy enough for my Dupdog.hs to actually work efficiently on huge duplications +2011-10-13.txt:22:02:45: incidentally, i don't think anyone has proved dupdog conclusively non-tc +2011-10-13.txt:22:06:28: CakeProphet: Anyway, Dupdog has a way to make the program "larger", which is a kind of control structure, and it has a conditional. +2011-11-08.txt:17:09:14: atehwa: no dupdog assignments? :P +2011-11-08.txt:17:09:34: "prove that dupdog is not Turing complete" would be a good assignment +2011-11-08.txt:17:13:05: actually I suppose the problem would be "prove that dupdog is or is not Turing complete" +2011-11-11.txt:17:20:50: * CakeProphet is the esteemed creator the dupdog programming language. +2011-11-13.txt:01:09:19: this is essentially what I did with dupdog. +2011-11-29.txt:19:18:01: kallisti: dupdog +2011-11-29.txt:19:20:30: 14:17 < elliott> kallisti: dupdog +2011-12-21.txt:21:52:04: * kallisti holds claim to the glorious language known as dupdog. +2011-12-29.txt:07:59:40: Ngevd: while you're at it prove dupdog is or isn't Turing complete. kth +2011-12-29.txt:07:59:59: dupdog? +2011-12-29.txt:08:02:14: for example the dupdog category, where objects are character interpreters and composition of interpreters forms a new interpreter. +2011-12-29.txt:08:02:26: for example the dupdog language itself is mfit composed with shanty +2012-01-16.txt:17:44:00: is dupdog +2012-02-01.txt:20:52:31: Just written a quick Dupdog interpreter in Haskell +2012-02-01.txt:21:12:59: _not_ the dupdog program, but the interpreter +2012-02-01.txt:21:14:59: dupdog hello.dupdog wrap=157 +2012-02-01.txt:21:15:39: Ngevd: hm ok. dupdog hello.dupdog --wrap 157 would be easier to convinve getOpt to do, i think. +2012-02-01.txt:21:17:23: Plain getArgs would give you ["hello.dupdog", "wrap=157"], which isn't too hard to parsemate, while I suppose getEnvironment would give you something like [("PATH", "/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games"), ("HOSTNAME", "something"), ("HOME", "/home/something"), ...]. +2012-02-01.txt:21:18:10: ["hello.dupdog", "--wrap", "157"] is even easier to parse +2012-02-01.txt:22:44:40: @tell Taneb er... Dupdog is not supposed to have a program pointer, you always take the first character. Also your eval' is an infinite recursion (hint: unless you are writing generic combinators, a function argument with IO type is usually a mistake.) +2012-02-01.txt:22:58:01: @tell Taneb I can see how "The next character is read" might give you that impression though - but note that (I clearly recall) the initial inspiration for dupdog was the idea of two irc bots reacting to each other's lines as entirely new commands, for which such a remembering of position doesn't make sense. +2012-02-02.txt:01:54:09: lolwat someone made a dupdog thing? +2012-02-02.txt:01:56:53: i've thought for a while that dupdog is like made for using ropes +2012-02-02.txt:02:06:38: * kallisti would like to expand on the idea of dupdog but isn't sure which direction to go. +2012-02-02.txt:02:14:36: I think this would make dupdog quite a bit more powerful, though I'm not sure how to quantify how. +2012-02-02.txt:02:15:30: it's not dupdog anymore +2012-02-06.txt:00:14:19: * kallisti has a plan to make a really simple revision to dupdog. +2012-02-06.txt:00:15:37: ColonelJ: http://esoteric.voxelperfect.net/wiki/Dupdog by all means go ahead +2012-02-06.txt:00:37:41: kallisti: dupdog isn't turing complete +2012-02-18.txt:14:45:33: You know [[Dupdog]]? +2012-02-18.txt:14:46:19: also I've got BRAND NEW IDEAS REGARDING DUPDOGOIDS (yes that's what they're called now) +2012-02-18.txt:14:47:02: I think a Dupdog proof of TCness/TinCness would be theoretically interesting. +2012-02-18.txt:14:49:47: ~!~ --infinite loop in dupdog? +2012-02-18.txt:14:49:56: @tell oerjan You could try and figure out whether Dupdog is TC or not. You know, if you wanted to. +2012-02-18.txt:14:52:22: What other dupdog programs have been written apart from that hello world? +2012-02-18.txt:15:04:25: The only thing that needs changing about dupdog is the output system. +2012-02-18.txt:15:04:50: I'm just exploring different ideas. I'm not trying to "fix" dupdog at the moment. +2012-02-18.txt:15:06:10: And it's not like dupdog programs that do coherent ASCII output are going to be written anyway. +2012-02-18.txt:15:07:39: I think counting a particular character in the source string and outputting that as a byte would be a bit less impossible for output. but as far as I can tell making dupdog sensible is out of the question. +2012-02-21.txt:01:45:31: @tell kallisti hm, due to a cutoff edit in 2007 the specification for dupdog seems to have lost the halting on shanty output - and i only noticed it now, despite correcting the rest of the cutoff at the time +2012-02-21.txt:22:09:39: oh right dupdog stuff +2012-02-21.txt:22:09:54: also I'm probably going to revise dupdog in the near future +2012-02-21.txt:22:10:22: because existing-dupdog's TCness is an interesting unsolved problem +2012-02-21.txt:22:26:48: i was thinking, has anyone even constructed a dupdog program which we're _sure_ doesn't halt? +2012-02-21.txt:22:42:32: `pastelogs taneb.*dupdog +2012-02-24.txt:05:21:02: give me a reason I shouldn't moderately improve the semantics of Dupdog, and then name the result "Dupdog" +2012-02-24.txt:05:22:07: Call the result Dupdog++ or something. +2012-02-24.txt:05:22:25: ZUPDOG +2012-03-06.txt:18:45:07: FOR EXAMPLE DUPDOG +2012-03-06.txt:18:47:33: so for example in a language that's a superset of dupdog, a [ could ignore all source up to ] +2012-03-06.txt:19:28:36: advacing the study of dupdogoids. +2012-03-07.txt:03:13:34: elliott: i think i may have discovered that later. i assume this is about dupdog, and i've been thinking something simpler rope-like might work better. +2012-03-07.txt:03:14:07: oerjan: yeah, it was dupdog +2012-03-13.txt:22:17:48: although don't mention something like Dupdog or Xigxag, I don't have a clue with those +2012-03-30.txt:16:59:34: The Dupdog model is interesting +2012-03-30.txt:17:03:59: Perhaps with an accumulator that can be incremented or reset, and a method for duplicating its own source a la Dupdog +2012-03-30.txt:17:07:19: I've decided to think about Dupdog differently +2012-07-18.txt:07:06:24: it's based off of dupdog, in some ways. +2012-07-18.txt:07:08:01: in dupdog, the first character in the source is interpreted as a command. in dogless, it's the character after the first ] +2012-07-18.txt:20:36:14: ais523: btw I made a spiritual successor to dupdog +2012-07-23.txt:05:07:47: zzo38: it's the dupdog-based language I described earlier. +2012-07-25.txt:09:33:02: I may or may not have taken the concept of dupdog and modified it to the point that it's turing complete, without feeling really cheap. +2012-07-25.txt:10:07:58: <-- possibly over excited about dupdog? +2012-07-28.txt:00:32:01: what's a good name for a language that's based very roughly off of dupdog but kind of more like /// +2012-07-28.txt:00:33:34: updog, to reference channel history. +2012-07-28.txt:00:35:03: but I don't remember anything named updog. +2012-07-28.txt:00:35:33: And then elliott brought in another totally unrelated bot named updog which did nothing but say "what's updog" whenever its name was mentioned. +2012-07-28.txt:00:35:48: what's updog +[too many lines; stopping]