|
3802
|
1 2007-01-17.txt:00:48:32: <CakeProphet> http://esolangs.org/wiki/Dupdog
|
|
|
2 2007-01-17.txt:00:55:23: <CakeProphet> http://esolangs.org/wiki/Dupdog
|
|
|
3 2007-01-17.txt:00:55:46: <CakeProphet> http://esolangs.org/wiki/Dupdog
|
|
|
4 2007-01-21.txt:08:18:49: <CakeProphet> time to implement dupdog
|
|
|
5 2007-01-24.txt:03:10:33: <CakeProphet> it needs dupdog!
|
|
|
6 2007-03-16.txt:17:00:19: * ais523 has just written a Dupdog interpreter
|
|
|
7 2007-03-16.txt:17:01:39: <ais523> I don't have any Dupdog programs to test it on, though
|
|
|
8 2007-03-16.txt:17:15:59: <RodgerTheGreat> "...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..."
|
|
|
9 2007-03-16.txt:17:56:08: <ais523> (i.e. a program in another language that generates Hello World in Dupdog)
|
|
|
10 2007-03-16.txt:18:09:34: <RodgerTheGreat> ais523 and I have been figuring out how to do something vaguely useful in dupdog (http://www.esolangs.org/wiki/Dupdog)
|
|
|
11 2007-03-16.txt:18:54:36: <ais523> wait, most Dupdog programs don't care if they're duplicated, as long as they end up with the right length
|
|
|
12 2007-03-16.txt:18:58:01: <RodgerTheGreat> lament: the esolang page is here: http://www.esolangs.org/wiki/Dupdog
|
|
|
13 2007-03-16.txt:19:08:15: <ais523> 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
|
|
|
14 2007-03-16.txt:19:39:20: <lament> all i can see so far is that dupdog really likes printing the fourth character.
|
|
|
15 2007-03-16.txt:19:59:52: -!- ais523 has quit ("Sorry I couldn't get that Dupdog Hello, World! to work").
|
|
|
16 2007-03-16.txt:21:27:09: <lament> RodgerTheGreat: http://www.esolangs.org/w/index.php?title=Dupdog&diff=6607&oldid=6606
|
|
|
17 2007-03-16.txt:22:25:14: <oerjan> writing a dupdog interpreter directly in perl should be trivial.
|
|
|
18 2007-03-16.txt:23:45:20: <oerjan> apropos haskell, the Data.Sequence module seems eminently suited for optimizing Dupdog, since it can concatenate in logarithmic time
|
|
|
19 2007-03-16.txt:23:45:37: <bsmntbombdood> and what's dupdog?
|
|
|
20 2007-03-16.txt:23:47:01: <RodgerTheGreat> dupdog: it's hip and trendy!
|
|
|
21 2007-03-17.txt:00:40:50: <oklopol> 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
|
|
|
22 2007-03-17.txt:00:46:25: * oerjan throws his beginning Dupdog implementation in the garbage bin.
|
|
|
23 2007-03-17.txt:20:39:44: <lament> shut up with your proposals and explain dupdog
|
|
|
24 2007-03-17.txt:20:40:12: <SevenInchBread> dupdog is completely useless.... I can't even figure out how to do Hello, World! with it.
|
|
|
25 2007-03-17.txt:21:12:52: <SevenInchBread> ...so..... what's the idea behind the dupdog program? Found any properties that can be exploited?
|
|
|
26 2007-03-17.txt:21:17:40: <SevenInchBread> dupdog was a strange attempt at playing with the semtantic interpretation of syntax.
|
|
|
27 2007-03-17.txt:21:21:36: <SevenInchBread> dupdog isn't very conceptually awesome... so I think my next attempt in that area will involving concurrently running interpreters on the same characters.
|
|
|
28 2007-03-17.txt:22:18:08: <oerjan> 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.
|
|
|
29 2007-03-18.txt:02:13:40: <RodgerTheGreat> I dunno, it seems somehow less elegant than dupdog
|
|
|
30 2007-03-18.txt:02:56:00: <SevenInchBread> ....I could take a dupdog-ian approach that doesn't use tokens.
|
|
|
31 2007-03-18.txt:02:59:50: <RodgerTheGreat> the more this new language becomes like dupdog, the more fun I predict programming with it shall become
|
|
|
32 2007-03-18.txt:03:00:05: <RodgerTheGreat> I still think Dupdog *might* be tc
|
|
|
33 2007-03-18.txt:03:03:35: <oerjan> (Dupdog interpreter)
|
|
|
34 2007-03-18.txt:03:05:53: <SevenInchBread> heh, funny that dupdog remained unnoticed for a couple of months... :)
|
|
|
35 2007-03-18.txt:03:21:31: <SevenInchBread> ...dupdog is like, the laziest invention ever.
|
|
|
36 2007-03-18.txt:03:45:43: <SevenInchBread> RodgerTheGreat, where is the Haskell interpreter for dupdog at?
|
|
|
37 2007-03-18.txt:03:46:25: * SevenInchBread lost interest in dupdog... so never got around to fully fixing his implementation.
|
|
|
38 2007-03-19.txt:11:56:32: * ais523 apologises for not providing the source code to their Dupdog interpreter
|
|
|
39 2007-03-19.txt:11:57:25: <ais523> But now, it's in the pastebin: http://pastebin.ca/raw/401416 (Dupdog interpreter), http://pastebin.ca/raw/401410 (Thutu2 wimpmode; work in progress)
|
|
|
40 2007-03-22.txt:18:45:53: <ais523> 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
|
|
|
41 2007-03-22.txt:19:00:54: <SevenInchBread> 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. :)
|
|
|
42 2007-03-26.txt:22:56:55: <RodgerTheGreat> crashmatrix: BF, ///, SevenInchBread's earlier project dupdog, OISC, etc
|
|
|
43 2007-03-26.txt:22:59:25: <crashmatrix> Idea: promote dupdog to make engineers go wow instead of Vista :)
|
|
|
44 2007-03-26.txt:23:04:29: <crashmatrix> not completely impossible, you wrote hello world in dupdog, didn't you?
|
|
|
45 2007-03-26.txt:23:11:08: <lament> anybody got the dupdog interpreter?
|
|
|
46 2007-03-26.txt:23:17:35: <SevenInchBread> dupdog was spawned in about a minute... I put no thought whatsoever on how it could be used.
|
|
|
47 2007-03-26.txt:23:24:30: <SevenInchBread> -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.
|
|
|
48 2007-03-26.txt:23:41:43: <lament> i also have my own dupdog interpreter in python
|
|
|
49 2007-03-26.txt:23:42:24: <oerjan> The files are oerjan.nvg.org/esoteric/Dupdog.hs and oerjan.nvg.org/esoteric/FingerTree.hs (third party module)
|
|
|
50 2007-03-26.txt:23:45:01: <lament> my interpreter: z3.ca/~lament/dupdog.py
|
|
|
51 2007-03-26.txt:23:55:07: <SevenInchBread> heh.... since dupdog reverses its source code often... does that make it reversible?
|
|
|
52 2007-03-26.txt:23:59:41: <oerjan> 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))
|
|
|
53 2007-03-27.txt:00:25:21: <SevenInchBread> if dupdog were Turing complete... I'm sure it's very likely that mfit or shanty alone isn't
|
|
|
54 2007-04-22.txt:00:40:31: <SevenInchBread> and the only one I can find of Dupdog is in some illegible compiled Perl stuff.
|
|
|
55 2007-04-22.txt:00:47:15: <oerjan> http://oerjan.nvg.org/esoteric/Dupdog.hs + FingerTree.hs. You can in theory use it if you can put the right functions together...
|
|
|
56 2007-04-22.txt:01:04:29: <oerjan> actually you don't need push for Dupdog...
|
|
|
57 2007-04-22.txt:02:16:25: <SevenInchBread> (untested dupdog interpreter)
|
|
|
58 2007-06-11.txt:19:57:49: <RodgerTheGreat> I'm also a big fan of dupdog and /// for essentially that reason
|
|
|
59 2007-06-22.txt:18:27:21: <RodgerTheGreat> It was around the time we were playing around with dupdog, if you feel like searching the logs
|
|
|
60 2007-06-23.txt:03:48:54: <RodgerTheGreat> (and I've conquered Dupdog, damnit!)
|
|
|
61 2007-07-12.txt:15:19:37: <RodgerTheGreat> this reminds me of the Dupdog hello world project
|
|
|
62 2007-07-12.txt:19:10:48: <lament> fine then, check out Dupdog.
|
|
|
63 2008-01-10.txt:21:54:09: <ehird`> CakeProphet: you made dupdog? you might like this then, it's self-rewriting
|
|
|
64 2008-01-10.txt:21:55:10: <ehird`> CakeProphet: dupdog isn't turing complete, though
|
|
|
65 2008-01-10.txt:21:59:17: <CakeProphet> I actually have no clue what dupdog is.
|
|
|
66 2008-01-10.txt:22:00:07: <oklopol> dupdog is interesting in that it's not interesting in anyway, but somehow seems cool :D
|
|
|
67 2008-01-10.txt:22:05:22: <CakeProphet> the state of a dupdog program is... the source code itself.
|
|
|
68 2008-01-11.txt:01:02:38: <ehird`> btw: a good excersize would be a dupdog interpreter.
|
|
|
69 2008-01-12.txt:03:01:35: <CakeProphet> I think I shall make another language like dupdog
|
|
|
70 2008-01-28.txt:20:43:47: <ais523> 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
|
|
|
71 2008-07-21.txt:01:05:10: <CakeProphet> ...dupdog is a very bad example.
|
|
|
72 2008-07-21.txt:01:06:29: <CakeProphet> dupdog literally just used the entire source code
|
|
|
73 2008-07-21.txt:01:11:40: <CakeProphet> ...ahahaha... functional dupdog.
|
|
|
74 2008-09-18.txt:21:56:26: <tusho> that's from the dupdog times
|
|
|
75 2008-09-18.txt:21:58:05: <tusho> that's where dupdog comes from
|
|
|
76 2008-09-18.txt:21:58:22: <ais523> dupdog is great though
|
|
|
77 2008-09-18.txt:21:59:02: <tusho> i think dupdog is tc
|
|
|
78 2008-10-17.txt:23:22:32: <oerjan> was it the dupdog hello world maybe
|
|
|
79 2008-10-17.txt:23:22:37: <AnMaster> dupdog?
|
|
|
80 2008-10-17.txt:23:22:56: <fizzie> Dupdog, yes.
|
|
|
81 2008-11-03.txt:19:34:57: <ais523> BF interp? dupdog interp?
|
|
|
82 2009-07-23.txt:00:56:51: <ais523> excepting maybe Dupdog and Xigxag
|
|
|
83 2009-12-23.txt:11:59:05: <ais523> it's sort-of, dupdog range in our analogy
|
|
|
84 2009-12-23.txt:11:59:14: <AnMaster> dupdog?
|
|
|
85 2009-12-23.txt:11:59:22: <ais523> http://esolangs.org/wiki/Dupdog
|
|
|
86 2009-12-23.txt:12:00:36: <AnMaster> ais523, it says unknown computational class for dupdog
|
|
|
87 2009-12-23.txt:12:01:11: <ais523> dupdog's much nastier than slashes
|
|
|
88 2009-12-23.txt:13:29:56: <oerjan> i'm pretty sure i've pondered dupdog
|
|
|
89 2009-12-26.txt:10:39:02: <ais523> Dupdog?
|
|
|
90 2009-12-26.txt:10:42:12: <ais523> and it's hard to see how to do that for dupdog
|
|
|
91 2009-12-26.txt:11:03:48: <AnMaster> 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?
|
|
|
92 2009-12-26.txt:11:15:02: <ais523> I suspect dupdog can't be done by a PDA
|
|
|
93 2009-12-26.txt:11:17:41: <AnMaster> ais523, but dupdog doesn't have stdin?
|
|
|
94 2009-12-26.txt:11:18:03: <ais523> AnMaster: exactly, which is why LBA doesn't even make any sense wrt dupdog
|
|
|
95 2009-12-27.txt:10:17:06: <ehirdiphone> Btw, anyone trying to prove dupdog sub TC could try to implement it in Total FP.
|
|
|
96 2009-12-27.txt:10:21:14: <oerjan> ehirdiphone: dupdog in Total FP seems unlikely. after all iirc it is pretty clear that some dupdog programs don't terminate
|
|
|
97 2009-12-27.txt:11:06:16: <AnMaster> <ehirdiphone> 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.
|
|
|
98 2010-04-13.txt:23:09:57: <songhead95> or dupdog
|
|
|
99 2010-04-13.txt:23:10:08: <ais523> hardly anyone's heard of dupdog
|
|
|
100 2010-04-13.txt:23:10:24: <AnMaster> which one was dupdog now again?
|
|
|
101 2010-04-13.txt:23:10:42: <ais523> http://esolangs.org/wiki/Dupdog if you need a link
|
|
|
102 2010-07-28.txt:16:39:40: <ais523> like the whole TCness of Xigxag/Dupdog?
|
|
|
103 2010-07-28.txt:16:40:13: <cpressey> Had not heard of Dupdog before.
|
|
|
104 2011-01-01.txt:19:26:24: -!- updog has joined #esoteric.
|
|
|
105 2011-01-01.txt:19:26:31: <elliott> Boy, I've got a massive plate of updog right here.
|
|
|
106 2011-01-01.txt:19:26:31: <updog> What's updog?
|
|
|
107 2011-01-01.txt:19:26:40: <elliott> I don't know, updog. What *is* updog?
|
|
|
108 2011-01-01.txt:19:26:40: <updog> What's updog?
|
|
|
109 2011-01-01.txt:19:26:47: <oerjan> updog is edible?
|
|
|
110 2011-01-01.txt:19:26:47: <updog> What's updog?
|
|
|
111 2011-01-01.txt:19:27:57: <oerjan> i have some suspicions about updog
|
|
|
112 2011-01-01.txt:19:27:58: <updog> What's updog?
|
|
|
113 2011-01-01.txt:19:29:52: <elliott> In Newspeak updog is doubleplusgood.
|
|
|
114 2011-01-01.txt:19:29:52: <updog> What's updog?
|
|
|
115 2011-01-01.txt:19:30:55: <elliott> hmm updog's got broken
|
|
|
116 2011-01-01.txt:19:30:55: <updog> What's updog?
|
|
|
117 2011-01-01.txt:19:31:10: -!- updog has quit (Remote host closed the connection).
|
|
|
118 2011-01-01.txt:19:32:11: -!- updog has joined #esoteric.
|
|
|
119 2011-01-01.txt:19:33:01: <elliott> AW DAMMIT UPDOG WHY DO YOU HAVE TO BE SO UPDOG
|
|
|
120 2011-01-01.txt:19:38:57: -!- updog has quit (Remote host closed the connection).
|
|
|
121 2011-01-01.txt:19:39:27: -!- updog has joined #esoteric.
|
|
|
122 2011-01-01.txt:19:39:56: <elliott> Updog!
|
|
|
123 2011-01-01.txt:19:39:56: <updog> What's updog?
|
|
|
124 2011-01-01.txt:19:41:44: -!- updog has quit (Remote host closed the connection).
|
|
|
125 2011-01-01.txt:19:41:54: -!- updog has joined #esoteric.
|
|
|
126 2011-01-01.txt:19:42:23: <elliott> Updog
|
|
|
127 2011-01-01.txt:19:42:24: <updog> What's updog?
|
|
|
128 2011-01-01.txt:19:43:13: -!- updog has quit (Remote host closed the connection).
|
|
|
129 2011-01-01.txt:19:43:56: -!- updog has joined #esoteric.
|
|
|
130 2011-01-01.txt:19:43:59: -!- updog has quit (Remote host closed the connection).
|
|
|
131 2011-01-01.txt:19:44:19: -!- updog has joined #esoteric.
|
|
|
132 2011-01-01.txt:19:44:36: <elliott> updog is in Ruby.
|
|
|
133 2011-01-01.txt:19:44:36: <updog> What's updog?
|
|
|
134 2011-01-01.txt:20:02:29: <elliott> ais523: i have a lot of updog lying around, can you take care of it?
|
|
|
135 2011-01-01.txt:20:02:29: <updog> What's updog?
|
|
|
136 2011-01-02.txt:17:07:30: <Phantom_Hoover> What's updog?
|
|
|
137 2011-01-02.txt:17:07:30: <updog> What's updog?
|
|
|
138 2011-01-03.txt:00:02:00: * Sgeo glares at updog suspiciously
|
|
|
139 2011-01-03.txt:00:02:01: <updog> What's updog?
|
|
|
140 2011-01-03.txt:00:02:12: <elliott> I wrote updog in like five minutes Sgeo :P
|
|
|
141 2011-01-03.txt:00:02:13: <updog> What's updog?
|
|
|
142 2011-01-03.txt:00:02:49: <Sgeo> elliott, updog, or the updog part of the script?
|
|
|
143 2011-01-03.txt:00:02:49: <updog> What's updog?
|
|
|
144 2011-01-06.txt:07:37:09: <Sgeo> And updog's presense here disproves my theory
|
|
|
145 2011-01-06.txt:07:37:09: <updog> What's updog?
|
|
|
146 2011-01-06.txt:07:37:34: <oerjan> hm i thought it could be updog too...
|
|
|
147 2011-01-06.txt:07:37:34: <updog> What's updog?
|
|
|
148 2011-01-06.txt:07:39:36: * Sgeo glares at the kicked updog menacingly
|
|
|
149 2011-01-06.txt:07:40:32: <Sgeo> So yeah, updog feeds shutup
|
|
|
150 2011-01-06.txt:17:18:59: <elliott> hm did updog crash?
|
|
|
151 2011-01-06.txt:17:20:03: <elliott> ok, looks like updog being kicked broke shutup since they run on the same service supervisor
|
|
|
152 2011-01-06.txt:17:20:40: <Sgeo> elliott, you're still trying to hide shutup being fed by updog?
|
|
|
153 2011-01-06.txt:17:20:42: <Sgeo> shutupdog
|
|
|
154 2011-01-06.txt:17:21:41: <elliott> oerjan: you realise that updog is a0
|
|
|
155 2011-01-06.txt:17:21:59: <oerjan> and since it didn't shut up when _you_ were away, updog was the main suspect
|
|
|
156 2011-01-06.txt:17:23:25: <Sgeo> Prove it. Run shutup without running updog
|
|
|
157 2011-01-06.txt:17:24:17: <elliott> ok, clearly updog isn't _banned_
|
|
|
158 2011-01-06.txt:17:24:40: <oerjan> of course not, poor updog never did anything wrong
|
|
|
159 2011-01-06.txt:17:27:02: -!- updog has joined #esoteric.
|
|
|
160 2011-01-06.txt:17:28:53: <elliott> but i won't bother if you're going to kick updog
|
|
|
161 2011-01-06.txt:17:28:54: <updog> What's updog?
|
|
|
162 2011-01-06.txt:17:29:43: <elliott> oerjan: so are you going to ban updog if i restart the instance so that shutup unbreaks?
|
|
|
163 2011-01-06.txt:17:29:44: <updog> What's updog?
|
|
|
164 2011-01-06.txt:17:30:22: -!- updog has quit (Remote host closed the connection).
|
|
|
165 2011-01-06.txt:17:32:07: -!- updog has joined #esoteric.
|
|
|
166 2011-01-06.txt:17:33:13: <Sgeo> Vorpal, updog was kicked for an experiment to see if shutup would stop reacting to my Newspeak and Active Worlds obsessions
|
|
|
167 2011-01-06.txt:17:33:13: <updog> What's updog?
|
|
|
168 2011-01-06.txt:17:36:31: <oerjan> Vorpal: i can even imagine him being honest about what code updog is running, as long as he has something listening in between :)
|
|
|
169 2011-01-06.txt:17:36:31: <updog> What's updog?
|
|
|
170 2011-01-06.txt:17:38:59: <oerjan> of course it doesn't have to be updog.
|
|
|
171 2011-01-06.txt:17:39:00: <updog> What's updog?
|
|
|
172 2011-01-06.txt:17:39:20: <oerjan> but it _is_ suspicious that it stopped when i kicked updog.
|
|
|
173 2011-01-06.txt:17:39:21: <updog> What's updog?
|
|
|
174 2011-01-06.txt:17:40:03: <Sgeo> Of course, if elliott wanted, he could switch it over to him then remove updog, as a "demonstration" that it wasn't updog
|
|
|
175 2011-01-06.txt:17:40:04: <updog> What's updog?
|
|
|
176 2011-01-06.txt:17:41:25: <elliott> Sgeo: and now you are applying your learnings to updog
|
|
|
177 2011-01-06.txt:17:41:26: <updog> What's updog?
|
|
|
178 2011-01-06.txt:17:43:27: <Sgeo> >updog< Factor
|
|
|
179 2011-01-06.txt:17:43:27: <updog> What's updog?
|
|
|
180 2011-01-06.txt:17:45:25: <Sgeo> elliott, I'd ask you how that even makes sense in any way whatsoever other than updog being the source, but
|
|
|
181 2011-01-06.txt:17:45:26: <updog> What's updog?
|
|
|
182 2011-01-06.txt:17:48:38: <Sgeo> oklopol, well, given the evidence, there's a LOT pointing to updog currently being the accomplice
|
|
|
183 2011-01-06.txt:17:48:38: <updog> What's updog?
|
|
|
184 2011-01-06.txt:17:58:33: <Sgeo> Phantom_Hoover, feel free to test shutup by msg'ing updog
|
|
|
185 2011-01-06.txt:17:58:34: <updog> What's updog?
|
|
|
186 2011-01-06.txt:18:06:45: <Sgeo_> cheater99, if elliott's telling the truth, AND updog and shutup are running on it... he's failing miserably
|
|
|
187 2011-01-06.txt:18:06:45: <updog> What's updog?
|
|
|
188 2011-01-06.txt:18:07:40: <Sgeo_> 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
|
|
|
189 2011-01-06.txt:18:07:40: <updog> What's updog?
|
|
|
190 2011-01-07.txt:20:10:47: <Sgeo> updog
|
|
|
191 2011-01-07.txt:20:10:47: <updog> What's updog?
|
|
|
192 2011-01-13.txt:02:06:43: <Sgeo> elliott, we all know that shutup's source is updog
|
|
|
193 2011-01-13.txt:02:06:43: <updog> What's updog?
|
|
|
194 2011-01-13.txt:02:07:40: <Sgeo> I think the bug where updog doesn't distinguish between msgs to the channel and to it hurts you even more
|
|
|
195 2011-01-13.txt:02:07:40: <updog> What's updog?
|
|
|
196 2011-01-13.txt:02:09:24: <Vorpal> <Sgeo> I think the bug where updog doesn't distinguish between msgs to the channel and to it hurts you even more <-- hah
|
|
|
197 2011-01-13.txt:02:09:24: <updog> What's updog?
|
|
|
198 2011-01-17.txt:22:30:53: <elliott> updog
|
|
|
199 2011-01-17.txt:22:30:53: <updog> What's updog?
|
|
|
200 2011-01-17.txt:22:30:59: <elliott> what is updog
|
|
|
201 2011-01-17.txt:22:30:59: <updog> What's updog?
|
|
|
202 2011-01-17.txt:22:32:01: <j-invariant> What's updog?
|
|
|
203 2011-01-17.txt:22:32:01: <updog> What's updog?
|
|
|
204 2011-01-18.txt:01:22:10: -!- updog has quit (Remote host closed the connection).
|
|
|
205 2011-01-18.txt:14:59:49: <elliott> ais523: well, I wiped it to run updog before, so "no", but yes, you could get it trivially
|
|
|
206 2011-01-18.txt:15:00:10: <ais523> hmm, is updog like dupdog?
|
|
|
207 2011-01-18.txt:15:00:22: <quintopia> ohey. where did updog go and what did it do while it was here?
|
|
|
208 2011-01-18.txt:15:00:34: <elliott> I took it down, and it replied to messages containing updog with "What's updog?"
|
|
|
209 2011-01-18.txt:15:14:23: <oerjan> <quintopia> 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
|
|
|
210 2011-01-22.txt:22:37:50: <Sgeo> updog
|
|
|
211 2011-02-04.txt:23:26:22: <Sgeo> So is updog.
|
|
|
212 2011-03-14.txt:14:03:03: <ais523> I still don't know whether Dupdog is turing complete or not
|
|
|
213 2011-03-14.txt:16:04:09: <oerjan> i certainly cannot recall proving dupdog definitely non-TC
|
|
|
214 2011-03-14.txt:16:09:23: <elliott> Gregor: Quick, add !dupdog so that oerjan can start proving.
|
|
|
215 2011-03-14.txt:16:11:27: <Vorpal> ais523, so is it a CA or TM what? I think I need to read up on dupdog
|
|
|
216 2011-03-14.txt:16:11:39: <ais523> what, dupdog?
|
|
|
217 2011-03-14.txt:16:12:29: <Vorpal> <ais523> what, dupdog? <-- I thought you were talking about dupdog above
|
|
|
218 2011-03-14.txt:16:13:11: <ais523> dupdog was one mentioned, but so were Xigxag and the 2,3 machine
|
|
|
219 2011-04-27.txt:20:14:22: <elliott> Vorpal: dupdog
|
|
|
220 2011-05-16.txt:04:32:55: <Sgeo> updog?
|
|
|
221 2011-07-04.txt:00:38:48: <oerjan> i think i briefly considered if they were useful for implementing dupdog
|
|
|
222 2011-09-05.txt:08:58:55: <CakeProphet> so you have the same code being evaluated by possibly different interpreters. Like dupdog but not as a stupid.
|
|
|
223 2011-09-12.txt:09:27:27: <CakeProphet> help make dupdog TC
|
|
|
224 2011-10-13.txt:21:35:59: <oerjan> i recall i tried genuine Data.FingerTree for http://oerjan.nvg.org/esoteric/Dupdog.hs
|
|
|
225 2011-10-13.txt:21:36:46: <CakeProphet> oerjan: lol dupdog.
|
|
|
226 2011-10-13.txt:21:37:07: <CakeProphet> I've considered creating a new language based on dupdog, but I have absolutely no idea how to make it interesting.
|
|
|
227 2011-10-13.txt:21:45:35: <CakeProphet> okay so... the question for improving upon the concept of dupdog is.
|
|
|
228 2011-10-13.txt:21:52:32: <elliott> in dupdog
|
|
|
229 2011-10-13.txt:21:54:18: <CakeProphet> I would think that an efficient dupdog interpreter is actually somewhat difficult.
|
|
|
230 2011-10-13.txt:21:59:39: <oerjan> elliott: i am wondering if Data.FingerTree is lazy enough for my Dupdog.hs to actually work efficiently on huge duplications
|
|
|
231 2011-10-13.txt:22:02:45: <oerjan> incidentally, i don't think anyone has proved dupdog conclusively non-tc
|
|
|
232 2011-10-13.txt:22:06:28: <elliott> CakeProphet: Anyway, Dupdog has a way to make the program "larger", which is a kind of control structure, and it has a conditional.
|
|
|
233 2011-11-08.txt:17:09:14: <CakeProphet> atehwa: no dupdog assignments? :P
|
|
|
234 2011-11-08.txt:17:09:34: <CakeProphet> "prove that dupdog is not Turing complete" would be a good assignment
|
|
|
235 2011-11-08.txt:17:13:05: <CakeProphet> actually I suppose the problem would be "prove that dupdog is or is not Turing complete"
|
|
|
236 2011-11-11.txt:17:20:50: * CakeProphet is the esteemed creator the dupdog programming language.
|
|
|
237 2011-11-13.txt:01:09:19: <CakeProphet> this is essentially what I did with dupdog.
|
|
|
238 2011-11-29.txt:19:18:01: <elliott> kallisti: dupdog
|
|
|
239 2011-11-29.txt:19:20:30: <kallisti> 14:17 < elliott> kallisti: dupdog
|
|
|
240 2011-12-21.txt:21:52:04: * kallisti holds claim to the glorious language known as dupdog.
|
|
|
241 2011-12-29.txt:07:59:40: <kallisti> Ngevd: while you're at it prove dupdog is or isn't Turing complete. kth
|
|
|
242 2011-12-29.txt:07:59:59: <Sgeo> dupdog?
|
|
|
243 2011-12-29.txt:08:02:14: <kallisti> for example the dupdog category, where objects are character interpreters and composition of interpreters forms a new interpreter.
|
|
|
244 2011-12-29.txt:08:02:26: <kallisti> for example the dupdog language itself is mfit composed with shanty
|
|
|
245 2012-01-16.txt:17:44:00: <kallisti> is dupdog
|
|
|
246 2012-02-01.txt:20:52:31: <Ngevd> Just written a quick Dupdog interpreter in Haskell
|
|
|
247 2012-02-01.txt:21:12:59: <oerjan> _not_ the dupdog program, but the interpreter
|
|
|
248 2012-02-01.txt:21:14:59: <Ngevd> dupdog hello.dupdog wrap=157
|
|
|
249 2012-02-01.txt:21:15:39: <oerjan> Ngevd: hm ok. dupdog hello.dupdog --wrap 157 would be easier to convinve getOpt to do, i think.
|
|
|
250 2012-02-01.txt:21:17:23: <fizzie> 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"), ...].
|
|
|
251 2012-02-01.txt:21:18:10: <oerjan> ["hello.dupdog", "--wrap", "157"] is even easier to parse
|
|
|
252 2012-02-01.txt:22:44:40: <oerjan> @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.)
|
|
|
253 2012-02-01.txt:22:58:01: <oerjan> @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.
|
|
|
254 2012-02-02.txt:01:54:09: <kallisti> lolwat someone made a dupdog thing?
|
|
|
255 2012-02-02.txt:01:56:53: <oerjan> i've thought for a while that dupdog is like made for using ropes
|
|
|
256 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.
|
|
|
257 2012-02-02.txt:02:14:36: <kallisti> I think this would make dupdog quite a bit more powerful, though I'm not sure how to quantify how.
|
|
|
258 2012-02-02.txt:02:15:30: <kallisti> it's not dupdog anymore
|
|
|
259 2012-02-06.txt:00:14:19: * kallisti has a plan to make a really simple revision to dupdog.
|
|
|
260 2012-02-06.txt:00:15:37: <kallisti> ColonelJ: http://esoteric.voxelperfect.net/wiki/Dupdog by all means go ahead
|
|
|
261 2012-02-06.txt:00:37:41: <ColonelJ> kallisti: dupdog isn't turing complete
|
|
|
262 2012-02-18.txt:14:45:33: <elliott> You know [[Dupdog]]?
|
|
|
263 2012-02-18.txt:14:46:19: <kallisti> also I've got BRAND NEW IDEAS REGARDING DUPDOGOIDS (yes that's what they're called now)
|
|
|
264 2012-02-18.txt:14:47:02: <elliott> I think a Dupdog proof of TCness/TinCness would be theoretically interesting.
|
|
|
265 2012-02-18.txt:14:49:47: <Taneb> ~!~ --infinite loop in dupdog?
|
|
|
266 2012-02-18.txt:14:49:56: <elliott> @tell oerjan You could try and figure out whether Dupdog is TC or not. You know, if you wanted to.
|
|
|
267 2012-02-18.txt:14:52:22: <elliott> What other dupdog programs have been written apart from that hello world?
|
|
|
268 2012-02-18.txt:15:04:25: <elliott> The only thing that needs changing about dupdog is the output system.
|
|
|
269 2012-02-18.txt:15:04:50: <kallisti> I'm just exploring different ideas. I'm not trying to "fix" dupdog at the moment.
|
|
|
270 2012-02-18.txt:15:06:10: <elliott> And it's not like dupdog programs that do coherent ASCII output are going to be written anyway.
|
|
|
271 2012-02-18.txt:15:07:39: <kallisti> 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.
|
|
|
272 2012-02-21.txt:01:45:31: <oerjan> @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
|
|
|
273 2012-02-21.txt:22:09:39: <kallisti> oh right dupdog stuff
|
|
|
274 2012-02-21.txt:22:09:54: <kallisti> also I'm probably going to revise dupdog in the near future
|
|
|
275 2012-02-21.txt:22:10:22: <ais523> because existing-dupdog's TCness is an interesting unsolved problem
|
|
|
276 2012-02-21.txt:22:26:48: <oerjan> i was thinking, has anyone even constructed a dupdog program which we're _sure_ doesn't halt?
|
|
|
277 2012-02-21.txt:22:42:32: <oerjan> `pastelogs taneb.*dupdog
|
|
|
278 2012-02-24.txt:05:21:02: <kallisti> give me a reason I shouldn't moderately improve the semantics of Dupdog, and then name the result "Dupdog"
|
|
|
279 2012-02-24.txt:05:22:07: <elliott> Call the result Dupdog++ or something.
|
|
|
280 2012-02-24.txt:05:22:25: <kallisti> ZUPDOG
|
|
|
281 2012-03-06.txt:18:45:07: <kallisti> FOR EXAMPLE DUPDOG
|
|
|
282 2012-03-06.txt:18:47:33: <kallisti> so for example in a language that's a superset of dupdog, a [ could ignore all source up to ]
|
|
|
283 2012-03-06.txt:19:28:36: <kallisti> advacing the study of dupdogoids.
|
|
|
284 2012-03-07.txt:03:13:34: <oerjan> 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.
|
|
|
285 2012-03-07.txt:03:14:07: <elliott> oerjan: yeah, it was dupdog
|
|
|
286 2012-03-13.txt:22:17:48: <ais523> although don't mention something like Dupdog or Xigxag, I don't have a clue with those
|
|
|
287 2012-03-30.txt:16:59:34: <Taneb> The Dupdog model is interesting
|
|
|
288 2012-03-30.txt:17:03:59: <Taneb> Perhaps with an accumulator that can be incremented or reset, and a method for duplicating its own source a la Dupdog
|
|
|
289 2012-03-30.txt:17:07:19: <Taneb> I've decided to think about Dupdog differently
|
|
|
290 2012-07-18.txt:07:06:24: <kallisti> it's based off of dupdog, in some ways.
|
|
|
291 2012-07-18.txt:07:08:01: <kallisti> in dupdog, the first character in the source is interpreted as a command. in dogless, it's the character after the first ]
|
|
|
292 2012-07-18.txt:20:36:14: <kallisti> ais523: btw I made a spiritual successor to dupdog
|
|
|
293 2012-07-23.txt:05:07:47: <spirity> zzo38: it's the dupdog-based language I described earlier.
|
|
|
294 2012-07-25.txt:09:33:02: <kallisti> 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.
|
|
|
295 2012-07-25.txt:10:07:58: <itidus21> <-- possibly over excited about dupdog?
|
|
|
296 2012-07-28.txt:00:32:01: <kallisti> what's a good name for a language that's based very roughly off of dupdog but kind of more like ///
|
|
|
297 2012-07-28.txt:00:33:34: <Phantom_Hoover> updog, to reference channel history.
|
|
|
298 2012-07-28.txt:00:35:03: <kallisti> but I don't remember anything named updog.
|
|
|
299 2012-07-28.txt:00:35:33: <Phantom_Hoover> And then elliott brought in another totally unrelated bot named updog which did nothing but say "what's updog" whenever its name was mentioned.
|
|
|
300 2012-07-28.txt:00:35:48: <shachaf> what's updog
|
|
|
301 [too many lines; stopping]
|
