00:00:13 Mmkay. . . Before I start; anyone *else* care?' 00:00:31 RodgerTheGreat: you are interested arn't you? 00:00:43 in BFM? 00:00:46 yes 00:00:54 I guess it could be interesting 00:01:00 oerjan: Feel free to discuss it, too; you're the other person who understands it right now. :p 00:01:10 but let me solve this rubics cube first.... 00:01:26 If you don't get it in 3 minutes, I'll smack you upside the head. 00:01:32 ok 00:01:40 In the meantime, I'll solve mine, too. 00:02:41 done 00:03:11 pikhq: you too? 00:03:48 Done. 00:03:57 Let's start, then. 00:04:00 ok 00:04:19 First, we've got the commands that allow BFM to be Brainfuck complete. . . 00:04:30 add variable number 00:04:47 variable number? 00:05:04 add 00:05:07 ah 00:05:14 uhm and what is variable? 00:05:17 Sorry; should be less vague. 00:05:32 Adds to . . . 00:05:46 subtract 00:05:54 Self-explanitory from that. 00:05:54 yeah but what can variable be? 00:06:02 @ 00:06:04 ah 00:06:20 Declares a variable at in the Brainfuck memory. 00:06:37 (a variable "current" is automatically declared) 00:07:10 current just means that the operation acts on the current location in the Brainfuck memory. 00:07:14 right 00:07:27 Moves right in the Brainfuck memory. 00:07:31 left 00:07:40 Same, except s/right/left/. 00:07:48 wont it get quite confused when one tries to write moving code? 00:08:03 at 00:08:17 yes. it is wise to use only the current variable in combination with right/left. 00:08:22 Tells the compiler that the current location is the 's location. 00:08:30 ah 00:08:47 It's not merely wise, it's the only thing you can do sanely. 00:09:11 while {} 00:09:16 and then you use at to switch back to known positions 00:09:23 While !=0, execute . 00:09:44 Finally: 00:09:49 set 00:09:53 are the macros written for wrapping code or for nonwrapping? 00:10:19 Pretty much the same as "while {subtract 1};add ". 00:10:29 jix: wrapping. 00:10:34 ok 00:10:48 So, that's it for pure Brainfuck equivalency. . . 00:10:53 do you have arrays implemented? 00:11:03 the stdlib assumes wrapping. the base commands might work in either way 00:11:07 RodgerTheGreat: I've not done an array macro yet. 00:11:13 hm 00:11:39 So, we've got a few more commands left. . . 00:11:43 since they'd amount to a datatype, rather than a function, it might be best to make them part of the spec. 00:11:43 is0 00:11:59 Tells the compiler that =0. 00:12:03 isnot0 00:12:13 Same, except !=0. 00:12:34 does is0 produce code to set variable = 0 or tells it only the compiler... 00:13:14 jix: Only tells the compiler, so the compiler won't set it to 0 again (when it's optimizing). . . Those two commands are only needed if the compiler's assumptions are wrong. 00:13:47 They do nothing when you've not enabled optimization. 00:13:48 cool 00:13:57 hmm 00:13:59 interesting 00:14:01 And one last command: 00:14:07 * jix is thinking of implementing some highlevel lang using bfm as backend 00:14:31 macro {} {} {} {} 00:15:05 Declares a macro , which executes , with , , and as arguments. 00:15:13 A macro would be called as follows: 00:15:28 > : 00:16:01 (the seperation of arguments into input, output, and temp are just to make code calling the macro easier to understand) 00:16:05 hm 00:16:18 and can each contain several variables 00:16:25 or none 00:16:51 The > and : are only needed when you've got output or temp arguments. 00:17:24 btw pikhq i noticed that there is currently no way to have only output and temp arguments 00:17:32 Argh; forgot a handful of commands. 00:17:45 oerjan: Need to fix that. 00:17:50 in 00:18:00 Takes input, and puts it into . 00:18:03 out 00:18:10 Outputs . 00:18:16 source 00:18:28 Executes the code in . 00:19:02 (^ is replaced with the location of the stdlib macro library) 00:19:18 comment {} 00:19:37 A comment block (when the compiler isn't told to strip this, it gets sent with the output). 00:19:46 That's all, I believe. 00:19:56 Unless you want an exhaustive spec of the macros in stdlib? 00:20:05 pikhq: no i don't 00:20:21 Good; I'm not willing to talk about those right now. 00:20:44 hmm i have a feature suggestion.... tool and the stdout of the tool gets inserted into the code 00:20:57 the macros in stdlib are in any case good to read to see how to code in the language 00:22:23 (the compiler may act oddly on code that's nonstandard, so don't do it!) 00:23:04 what do you mean by nonstandard? 00:23:30 while [variable] ("[ Wheee! ]') {code} 00:23:32 :p 00:24:07 (I *think* that would make the compiler vomit on your terminal) 00:24:21 let's try that 00:24:49 so nonstandard = syntax error 00:24:59 Yeah. 00:25:16 only 15 lines 00:25:43 oh wait 00:25:48 i called the interpreter wrong 00:26:02 ./bfm --file file.bfm > file.b 00:26:08 why --file? 00:26:18 Or: ./bfm --file file.bfm --strip 1 --optimize 1 > file.b 00:26:29 Haven't bothered getting the command line parser done right. 00:26:35 ah ok 00:29:54 Any luck? 00:33:56 is it possible to pass numbers as arguments to macros? 00:34:10 Only variables. 00:35:07 have you tried? 00:35:13 no 00:35:28 Only variables, according to the spec; whether it works on the compiler or not is beyond me. . . 00:35:41 Err. . . 00:35:49 * pikhq beats his brain into submission 00:36:01 why? 00:36:03 it could be useful to have numbers too 00:36:26 The question, then, is how to get it integrated into the spec. . . 00:36:35 And the compiler. 00:36:55 Hmm. 00:37:49 macro {} {} {} {} {}? 00:37:57 i should think the compiler already allows it 00:37:59 macro {} {} {} {} {}, I mean. 00:38:05 . . . Oh. 00:38:19 Just change the spec, then? :p 00:39:39 Yeah, it does work. 00:39:56 After banging my head against the wall for a while, I think I've got my trefunge instruction wrapping working. Now to test it. :D 00:39:59 Fine; macros can be passed variables or numbers (be careful with this). 00:40:06 Voila. 00:40:46 for what it's worth you could probably squeeze through {} blocks too i expect 00:41:09 Hmm? 00:42:13 oerjan: pikhq: GregorR: ihope: everyone else don't forget to submit your statements! 00:42:38 jix: I'm thinking about what they should be. 00:43:09 i am not sure whether to submit what i have or try to improve it 00:43:34 oerjan: even if you don't have many or some that arn't that funny.... together with the rest they will be 00:43:49 boring statements are 1000x better than no statements at all 00:43:56 Mmh. 00:44:01 oh they are all somewhat insane 00:44:09 oerjan: well no problem then 00:44:16 ouch 00:44:20 oerjan: i misread your msg 00:44:30 jix: If you want to see a finished BFM project, http://pikhq.nonlogic.org/basm.tar.bz2 (understanding it could be a bit difficult; sorry). 00:44:42 i am not sure whether to submit < i thought OH NO!!!> 00:45:15 What's your email again? 00:45:23 pikhq: jannis@harderweb.de 00:45:56 thats @web.de easy to remember 00:46:19 pikhq: i think {} blocks can also be macro arguments 00:47:13 after all the macro and while commands essentially work that way 00:47:43 oerjan: Ah. 00:47:59 http://www.zib.de/zuse/Inhalt/Kommentare/Html/0684/universal2.html <- FOUND IT! This article is fascinating. I mentioned it a few weeks ago, but I didn't want to scan it in from my book for fear of summoning copyright demons. 00:53:00 I've got 3 commands so far. . . 00:53:22 I think you'll laugh hysterically at them. ;) 00:53:30 ok 00:53:58 "The result shown in this paper seems counterintuitive, until we realize that operations like multiplication and division are iterative computations in which branching decisions are taken by the hardware." 00:54:04 "The conditional branchings we need are embedded in these arithmetical operations and the whole purpose of the transformations used is to lift the branches up from the hardware in which they are buried to the software level, so that we can control the program flow. The whole magic of the transformation consists in making the hardware branchings visible to the programmer." 00:54:15 ^ sums up the paper well. 01:05:08 * pikhq has sent off his entry 01:05:21 jix: Feel free to laugh as soon as you see my entry. 01:06:25 i'll wait with looking at them until the deadline 01:06:31 will be more fun to read them all at once 01:06:52 You'll get a kick out of mine, I assure you. 01:07:16 i hope we get a lot of funny and incompatible syntax ^^ 01:08:11 Mine has three syntax types in it. 01:08:31 mine doesn't really has syntax it's just nargh i can't explain without showing them.... 01:08:32 * pikhq grins evilly 01:08:49 you could say mine has 15 types of syntax or so ^^ 01:09:29 Got a bit over 21 hours to go. 01:09:43 (I think) 01:09:47 yeah 01:10:03 oh and if someone hasn't 15 statements yet and thinks ah this one really has to go in you can submit a 2nd mail 01:10:06 It *is* 01:09 UTC, right? 01:10:12 pikhq: dunno 01:10:23 pikhq: i was on some website that had an uhm dunno what clock 01:10:37 i allways fuck up times between time zones :| 01:11:05 * pikhq only submitted 8 (4 of which were defined in terms of the others). . . 01:11:08 00:10:39 gmt sais this side 01:11:43 22 hours, then (thought I was in UTC-7, not UTC-6; damn you, daylight savings time!). 01:13:07 i'm 2 hours ahead of gmt now but 1 hour ahead when the other daylight saving state is.... 01:16:35 Anyone else care to submit? 01:16:40 We need your evil ideas. 01:16:51 well there is plenty of time left... i just wanted to remember everyone 01:17:01 Bit under a day. 01:17:09 and i expect GregorR to submit ideas... he always has good ideas.... 01:17:16 -!- anonfunc has joined. 01:17:22 Garr 01:17:30 GregorR: whatis? 01:17:35 Do you have anything resembl---oh right, you're not reading it. 01:17:54 How about basic guidelines for statement structure? How can we submit statements if we don't know what a statement looks like :P 01:18:03 line-separated? ;-separated? 01:18:07 GregorR: well it can be anything! 01:18:08 no limits 01:18:13 just come up with something 01:18:23 might be that your particular statement needs a ; and some others don't 01:18:44 Razor-X: How's judging going on the contest? 01:18:45 What abouve variables. 01:18:47 Are there variables? 01:18:56 GregorR: well if you need variables just use them 01:19:00 there will be variables then 01:19:04 if you want a tape.... just use it 01:19:10 same for stack / whatever 01:19:12 But if there are only variables in two statements, that's sort of ridiculous :P 01:19:23 That's the idea. 01:19:47 of course there will be a way to swap data between tape/variables if needed etc.... but that's part of the 2nd round... 01:19:50 One thing we'll have is the hardest to implement language ever. 01:20:15 * pikhq has a tape, stack, *and* variables used by his statements. . . 01:20:18 Bwahahaha! 01:20:39 My statements alone also provide for Turing completeness. 01:21:06 hmm i dunne but i think mine would too 01:21:26 i hope we get nondeterminism somehow 01:23:36 How many am I supposed to do? 01:23:59 GregorR: between 5 and 15 01:25:45 * pikhq feels that this language is going to be really hard to parse 01:25:55 Yeah :P 01:26:00 I have no intention of helping with that 01:26:49 * pikhq drags you into that 01:28:31 i'm sure there wont be a compiler for the language 01:29:13 i'm sure i should go into bed now 01:30:55 It's a requirement. ;p 01:31:14 Well, I have three ... 01:31:18 (at least, an implementation is required) 01:34:12 Sending to jix, right? 01:34:32 GregorR: yes to my email address 01:34:49 GregorR: but you have a few ours left.... 01:35:11 +h 01:35:13 -!- jix has quit ("Bitte waehlen Sie eine Beerdigungnachricht"). 01:41:08 -!- kipple_ has quit (Read error: 110 (Connection timed out)). 01:44:53 -!- ihope has quit (Read error: 110 (Connection timed out)). 01:49:38 Hmm 01:49:56 * Sgeo doesn't know if he should use the incoming table for computations etc 02:05:21 -!- oerjan has quit ("Good night."). 02:36:32 -!- Sgeo_ has joined. 02:47:48 a programming language based on lojban would be fun! 02:49:10 * Sgeo_ has a lot of ideas for MKBL 02:49:17 -!- Sgeo has quit (Connection timed out). 02:50:16 Dear lord. . . 02:51:26 hm? 02:52:18 Language based on Lojban. . . Craziness. 02:59:01 -!- TehCommando has joined. 03:00:57 * pikhq sighs 03:01:25 Please evaluate (8 * 9)^56 03:02:03 PROGRAMMER ERROR: /dev/coffee is out. Refill mug. 03:03:01 Answer: 102475441987519000200272610048162721086802501989166604512727563935541058327937254889964982197984476266496 03:03:05 return full mug 03:03:25 IRP> 03:03:43 PROGRAMMER ERROR: I don't interperet math until it's RPN or sexp. 03:04:53 return 0 03:05:28 PROGRAMMER ERROR: Unwanted terseness 03:06:00 (I (not (do)) (want (to)) .) 03:06:09 please print and mail "file.doc" to me 03:06:27 404 File Not Found 03:06:42 please find "file.doc" 03:06:44 IRP ERROR: IRP shutting down. 03:06:49 410 Gone 03:07:07 !EgoBot will take care of your needs. 03:07:09 * EgoBot will take care of your needs. 03:07:40 please thank everyone else here 03:07:58 -!- Sgeo_ has changed nick to EveryoneElseHere. 03:08:39 * EveryoneElseHere is thanked. 03:09:11 please give my brother a haircut 03:09:33 ERROR: Brother not found in vicinity. 03:09:50 ERROR: Location of TehCommando unknown 03:09:50 please rename me to "Asdquefty" 03:10:21 ERROR: I-am-not-you 03:10:29 IRP> programmers: Please echo "/ignore TehCommando". 03:10:39 thx bye 03:10:40 "/ignore TehCommando" 03:10:42 -!- TehCommando has quit ("Leaving"). 03:11:06 -!- EveryoneElseHere has changed nick to Sgeo. 03:30:00 http://esoteric.voxelperfect.net/wiki/MKBL-LN 03:30:34 It's a start of a spec 03:34:07 -!- sp3tt has quit (Remote closed the connection). 03:34:08 -!- sp3tt has joined. 03:39:31 PROGRAMMER IS OVERLY POLITE. 03:41:41 Hahah. 03:42:15 Any comments on MKBL-LN so far? 03:51:45 Participate in language design. 04:01:40 Ah. INTERCAL is fun :D. 04:02:05 I feel like playing around with ASM and Forth instead of implementing SLUMTP. 04:02:43 Razor-X: Have you even *looked* at the entries for the contest yet? 04:02:47 It's been nearly a month. 04:02:57 pikhq: Somewhat. 04:03:03 I've looked at yours. 04:03:11 But I mean, the committee has not convened. 04:03:25 The contest has been *over* for a month; the commitee should've convened weeks ago. -_-' 04:03:45 Well, I just got un-busy technically yesterday. 04:04:01 I'm not sure where everyone else has been. 04:04:13 GregorR is bantering less than usual too :( 04:04:44 How about this! 04:04:47 Gregor + 19 credit hours + 20 work hours = foo 04:05:15 Committee! Meet in ##quantum in 24 hours! 04:05:32 I'll be in class in 24 hrs. 04:07:33 25 hours then? 04:07:57 I'll be on my way home in 25 hrs :P 04:08:04 How about 6 * 24 hou? 04:08:05 *hours 04:08:26 Saturdays are all free :P 04:08:35 Hooray geeks with no lives! 04:39:02 -!- CakeProphet has quit (Read error: 113 (No route to host)). 04:53:07 No comments on MKBL-LN? 05:12:31 -!- Asztal has quit (Read error: 60 (Operation timed out)). 05:23:33 -!- Arrogant has joined. 05:34:28 hey, Razor-X- I finished the spec for "synthesys" http://www.nonlogic.org/dump/text/1161556217.html 06:24:21 RodgerTheGreat: Lemme take a looksee. 06:24:48 Also, are you free to meet for the first of probably many judging meetings next Saturday? 06:26:01 oh, sure. 06:26:07 my weekends are generally free. 06:26:13 Awesome. 06:27:53 What does pop 2 mean? 06:28:24 pop the top two arguments from the stack. 06:28:36 Aha. 06:28:44 I then refer to them by their order, [1] being first, [2] second and so on. 06:29:06 it seemed like the least ambiguous way to say it. 06:29:59 Aha. 06:30:12 I don't mean to be a pain or anything, but you might want to dry a small Stack drawing. 06:30:23 Like: |1|2| -> |2| 06:30:28 hm. might be a good idea. 06:30:37 Or use Forth style comments. 06:30:46 I plan on making a more nicely formatted and better explained version of the spec soon. 06:31:16 Ah. 06:32:05 So @ pop's the first two things off the stack? 06:32:19 it's an assignment operator. 06:32:26 Oh, nevermind. 06:32:27 I see! 06:32:33 Concat made it make sense, heh. 06:32:53 the stack can contain literal values or variables. 06:33:15 Are you sure you don't want to make + pop [1], push [1] + 1 ? 06:34:27 well, that might be a better way to explain it, but remember- all variables are essentially strings. I wanted to make it clear that + and - operate on the first (or only) character of a string. 06:38:34 Well, that would be different behavior. 06:38:53 Because you could have |'a'|'b'| then a +, and you would have |'b'|'b'| right? 06:39:02 yes 06:39:12 The version I proposed would be mork ``stack-ish'' is all I meant to say. 06:39:17 hm 06:39:28 *more 06:39:47 Because Synthesis would be trivial to implement on any stack based device. 06:40:43 -!- ghostless has quit ("leaving"). 06:40:49 to a degree. #  and : are what make it very powerful, and % is a convenient feature. 06:41:17 the stack is more of a means to an end- they make it extremely easy to create long chains of function calls. 06:41:40 Ah. 06:42:16 : is the super operator ;D 06:43:07 : allows programmers to create functions that contain functions, and so on easily, as string literals are an essential to declaring functions. 06:43:32 and the fact that functions are themselves strings makes it trivially easy to make use of self-modifying code- just change the string. 06:43:45 Hmm... can you demonstrate a function for me? 06:43:48 Simple. 06:44:06 'sum' "[-~+~],"@ 06:44:14 defines a function, 06:44:24 'a' 'b' 'sum' # 06:44:49 will add together the contents of a and b (or the first characters) 06:46:08 Ah hah. 06:47:49 if I wanted a function that contained said function, I could do 'fun' "'sum' X[-~+~],X@":@ 06:48:11 then, 'fun' # will redefine the sum function. 06:48:31 have I captured your imagination? :) 06:48:35 Yes ;) 06:48:40 Simple, yet elegant. 06:48:57 I'm glad you think so. ^_^ 06:49:07 Is there any required length for the stack? 06:49:47 hm. There's none required, but I should probably define one in the spec as a "minimum expected size". 06:50:10 Yeah. 06:51:59 -!- Sgeo has quit (Read error: 110 (Connection timed out)). 06:53:01 well, I need to get some sleep soon- calc class tomorrow morning. If you have any suggestions for tweaks and modifications, just let me know. If you feel so inclined, I would be honored if you helped me write the standard library. 06:53:31 Do you have an implementation for it done, or would you want me to do one? 06:53:56 I have one in the works, but a second one would be awesome! 06:54:11 Heh. Mmmkays. 06:54:21 What would you like to see in stdlib? 06:55:08 I'm not sure yet- math functions and more complex string/number/etc manipulation and conversion seem like they would be the most useful. 06:55:23 Wait... 06:55:28 Oh. Nevermind. 06:55:41 I think passing code segments as arguments might make it possible to synthesize flow control like case... select statements and the like. 06:55:56 I have one suggestion: 06:56:30 If you want to make a few modifications to the spec to make it conform just a bit more to the architecture, I think you'll have a great low-level language. 06:56:47 ooh. a compelling concept. 06:57:08 Because it already seems like a great abstraction of the machine. 06:57:38 well, good night... er... good morning. I'd be fascinated to discuss this in more detail later. 06:57:46 Sure-z :) 06:57:53 I may or may not have an implementation done by tonight. 06:57:58 haha 07:59:59 -!- clog has quit (ended). 08:00:00 -!- clog has joined. 08:49:20 -!- ivan` has joined. 10:36:54 -!- Arrogant has quit ("Leaving"). 11:00:16 -!- ihope_ has joined. 11:00:28 -!- ihope_ has changed nick to ihope. 11:12:43 -!- jix has joined. 11:39:55 -!- ihope has quit (Read error: 110 (Connection timed out)). 11:46:03 -!- ihope_ has joined. 11:46:15 -!- ihope_ has changed nick to ihope. 12:29:40 -!- ihope has quit (Read error: 110 (Connection timed out)). 13:19:19 !ps 13:19:22 3 SimonRC: ps 13:19:54 !psd 13:19:56 Huh? 13:19:59 !psd 13:20:00 !ps d 13:20:03 Huh? 13:20:04 1 EgoBot: daemon EgoBot reload 13:20:07 2 GregorR-L: daemon cat bf 13:20:08 3 SimonRC: psd 13:20:11 4 SimonRC: ps 13:34:18 'morning, everyone. 13:42:10 Morn'. 14:19:03 bbl 14:38:34 -!- oerjan has joined. 16:06:48 -!- tgwizard has joined. 16:11:19 back 16:43:39 -!- kipple_ has joined. 17:13:02 -!- lindi- has quit ("Lost terminal"). 17:23:42 -!- oerjan has quit ("Leaving"). 17:40:46 -!- GregorR-L has joined. 17:41:23 -!- Asztal has joined. 17:44:55 bbl 18:04:08 -!- lindi- has joined. 19:08:32 Time for NAME THAT FAMOUS PASSAGE! 19:08:36 This, _ duration, it goes out and duration, it goes out and age information quite bad us it goes out bevoegheid hope this, it goes out and and and seasonal datum darkness this, it goes out and and and the seasonal datum light this, it goes out and and and and seasonal datum disbelievingness this, it goes out and and and and and seasonal datum it believes and and and and and this, to go out the age idiotic thing this, it goes out and and and and and a 19:08:37 nd many winter d3esespoir, me that us sky of oneself it goes immediately, thing because of us is going out from this and and me us who are going out hazard anything us who are not, us me which am the possibility of doing to go out me all, it is a B to go out and it fixes and compared to this me which recover, different method -goes out and the en brevity which it talks, I discover a duration by now 19:09:05 This passage has been translated: English->French->Dutch->English->German->English->Greek->English->Korean->English 19:09:25 You guess the original passage (I don't need the exact words, just the context), and you win! 19:09:31 Win nothing. 19:09:53 eek. 19:10:18 The Korean really kills it :P 19:10:19 "and and and and and" :/ 19:10:46 GregorR-L: you read my statements! 19:10:56 ? 19:11:06 you'll see in a few hours... 19:11:13 ? 19:11:31 -!- anonfunc has quit. 19:11:47 I really have no idea what that bastardised passage may be : 19:11:49 :( 19:12:01 At 11:21 I'll drop one translation :P 19:12:10 time zone? 19:12:15 Erm, 11:19 ... PST. 19:12:19 In six minutes ;) 19:12:22 argh 19:12:25 Give people a chance :P 19:12:38 Ten minutes after I posted it ;) 19:13:42 How does it manage to get numbers inside of words 19:13:48 I don't know XD 19:13:53 Good ol' Babelfish :P 19:14:59 hell 19:15:55 A psalm? 19:15:59 I dunno. 19:16:13 I think when Korean gets stripped off somebody may guess it :P 19:16:35 is the text know outside of english speaking countries? 19:16:52 I can't guarantee that it is, but I can't imagine that it isn't - it permeates the fabric of society :P 19:17:13 I think it's a biblical quote. 19:17:23 *buzz* wrong 19:17:33 I think I give up for now. 19:17:36 Almost time to strip off Korean :P 19:17:41 Less than one minute! 19:17:45 Ding! 19:17:46 _ this I am better than the period, I am more very bad from the period, this I am the age intelligence, this I am the age the idiot thing, this I am the season the faith, this I am the season the disbelievingness, this I am the season the light, this I am the season dark, this I am bevoegheid hope, this I am the a lot of winter désespoir, because us ours I have, we I have I have nothing for us, we I can I am I am all, that I go immediately our own s 19:17:46 ky, I am all, that I align the other way - en brevity I say, I find period up to now 19:18:01 I thought given all the talk about seasons/datums it may be a 1) scientist 2) philosopher 19:18:44 I don't know WHERE THE HELL the word 'datum' came from XD 19:18:47 Um. . . War and Peace? 19:18:54 Nope 19:19:22 Could've *sworn* that was the first page or so of War and Peace. 19:19:53 If you think you recognize the quote itself, just give some of the quote, regardless of context. 19:19:54 (although I may have the wrong !%$# book. . . "It was the best of times, it was the worst of times. . .", right?) 19:20:05 Ding ding! 19:20:15 Tale of Two Cities 19:20:17 oh my, that really is butchered 19:20:19 Doh. 19:20:23 XD 19:20:26 Wrong. Damned. Book. 19:20:26 LOL?! 19:20:29 GOD I love Babelfish. 19:20:34 "I am more very bad" 19:21:00 Let us continue stripping off languages until it becomes the recognized quote. 19:21:14 The next one is an important one, as the tense is destroyed here (Greek): 19:21:18 but do it in a fast run.. 19:21:18 It was best from the periods, was most badly from the periods, it was the age of intelligence, it was the age of the stupid thing, it was the era of the faith, it was the era of the disbelievingness, it was the season of the light, it was the season of Obscurity, it was bevoegheid hope, it was the winter of désespoir, much for us ours had, we has had nothing for us, we could be been everything, that go directly to the sky, ours was everything, which 19:21:18 line the other way - briefly said does, the found period so far 19:21:24 Of course 19:21:54 German was cruel to it as well: 19:21:56 He was best of the periods, was worst of the periods, he was the age of wisdom, he was the age of the silly thing, he was the era of the belief, he was the era of incredulity, he was the season of light, he was the season of obscurity, he was the bevoegheid of the hope, he was the winter of désespoir, a lot for us our has had, we have had nothing for us, us let us be everything that to the sky go directly, our were everything doing lead the other ma 19:21:56 nner - in short, the period found so far as 19:22:01 i want the german text... 19:22:04 OK 19:22:13 Er war von den Perioden am besten, war am schlechtesten von den Perioden, er 19:22:13 war das Alter von Klugheit, er war das Alter der dummen Sache, er war die Ära 19:22:13 des Glaubens, er war die Ära der Ungläubigkeit, er war die Jahreszeit des 19:22:13 Lichtes, er war die Jahreszeit von Obscurity, er war das bevoegheid der 19:22:13 Hoffnung, er war der Winter von désespoir, viel für uns unsere hat gehabt, wir 19:22:16 hat gehabt nichts für uns, wir ließ uns sein alles, die zum Himmel direkt 19:22:18 gehen, unser war alles, der Leitung die andere Weise - kurz gesagt tut, die 19:22:20 gefundene Periode soweit 19:22:22 Erm ... megaspam >_O 19:22:43 That last English one is after Dutch+French 19:22:45 And french converted "it" to "he"? 19:23:06 One of French and Dutch - there's no English between them, so Idonno :P 19:23:10 " er war der Winter von désespoir" << after this part it get's really screwed up 19:23:27 well in frensh there is no it... onle he and she 19:23:39 even things are either male or female... 19:23:42 I really wonder what Hungarian could do to it 19:23:50 but I've never found a translator 19:23:53 I don't think Babelfish has Hungarian :P 19:24:01 ok next round... 19:24:05 Somebody else's turn: I recommend English->French->Dutch->English->German->English->Greek->English->Korean->English 19:24:12 it would at least destroy all the gender 19:24:12 i'll try 19:24:22 but i'll use a different lang order 19:24:28 *shrugs* 19:24:32 gimme some time i have to find obscure translators... 19:24:44 i had one with cool languages a few hours ago... 19:24:49 lol 19:24:57 Like Esperanto and Ebonics :P 19:25:12 no 19:25:22 but it was the only one i found that had swedish 19:25:40 oh and it allows => 19:25:48 not only english <=> 19:25:51 Noice 19:26:06 Though that probably means there's a fairly destructive internal representation ;) 19:26:07 but i will revert to english at least every 2 langs so i can drop steps 19:26:11 Right. 19:27:21 found a good text 19:29:18 :( it fails from korean => english... i think i have to insert an extra space to avoid it stopping translation 19:30:04 it doesn't work from there on... 19:30:09 i have to use another translator there 19:30:14 maybe russian? 19:30:16 THAT'S EVEN BETTER 8-d 19:30:19 Erm, 8-D :P 19:31:02 nargh i have to use korean at a later stage... 19:31:05 it doesn't work there 19:31:33 lol 19:31:35 this doesn't sound good for our chances of guessing it ;) 19:31:41 haha arabic ^^ 19:31:41 Maybe I should do another one while you're doing that X-P 19:32:28 haha that really made it ridiculous 19:34:08 nargh the korean of that page doesn't work 19:35:06 haha japanese made it really cool 19:35:57 O_O 19:39:10 ok the chain is english => swedish => arabic => english => german => japanese => english => trad. chinese => russian => english => greek => english => french => english 19:39:33 i made it that long so i can drop a few times before someone recognizing it 19:39:38 here it comes: 19:39:38 Today, we are handle decreased the daily newspaper of the first boat splendourful, [[“iynfwrm' ayshnsbwryfyk' ayshndyrktyfn]]. This traction outside of ours street, initially examined in the team [[hystwryn]], garden, request for divine the blessings the clean dish. [“ammnt] the truth causes complexes [[, the jam of the pain of the mwtsGnd]] with the all workmen, when it flowers. Us it country of the family of the state of the family of the idea 19:39:39 of the connection of the troops of knowledge of arm that it is him is very important. Racingism us 1, is used, the solution and reason. [ytkllmbnfsy] our enemy with the cube, it buries, a la confusion, in which finds will be specially anxious you will be our these. We obtain profit! 19:40:20 GregorR-L: got an idea? 19:40:23 A hint: Is "newspaper" anywhere in the original? 19:40:37 GregorR-L: you gave no hints 19:40:43 You asked for no hints X-P 19:40:53 i wont give hints that early... 19:41:08 Finefine 19:42:00 uh i didn't looked at the time 19:42:22 It was 11:40PST 19:42:26 i'll decrease every 5 mins ok? 19:42:29 OK 19:42:47 anyone else guessing? 19:42:56 pikhq: are you guessin? 19:43:17 Heh 19:43:25 GregorR-L: any idea? 19:43:32 I'm thinkin', I'm thinkin' :P 19:44:16 erm 19:44:27 I have a dream? 19:44:35 uh no 19:44:40 wait 19:44:44 Asztal glommed on to "racingism" :P 19:44:46 uhm i don't know 19:45:04 Asztal: you have to post text as i don't know how this is called it's very famous but i don't know how it is called 19:45:26 uhm i shall drop a step now 19:45:43 without french: 19:45:46 Today, we are decreased joystick the daily newspaper of first splendourful ship, [[“iynfwrm'ayshnsbwryfyk'ayshndyrktyfn]]. This pull outside from ours street, first examined in team [[hystwryn]], garden, prays for divine the benedictions the clean dish. [“ammnt] causes complex truth [[, the jam of pain of mwtsGnd]] with the all workers, when it blooms. Us the country of family of condition of family of idea of connection of troops of arm acquain 19:45:46 tance it is it is very important. Racingism we 1, is used a, the solution and reason. [ytkllmbnfsy] our enemy to the cube, it buries, has confusion, in which finds will be specially anxious you will be our these. We obtain profit! 19:45:48 http://www.usconstitution.net/dream.html (on second thought, looks nowhere nearÖ 19:45:56 no 19:46:08 ah i know that text too but no... 19:46:20 *whew* 19:46:34 it's so funny 19:46:37 I love "joystick" -> "handle" :P 19:47:18 i love that part too 19:47:23 but not only in this step... 19:47:40 This pull outside from ours street ... 19:48:41 GregorR-L: I bet half of those words which look like they're probably not too far wrong have been rotated through 720 degrees of wrongness :( 19:48:49 Probably ^^ 19:49:09 i can't stop laughing ^^ 19:49:21 it's too hilarious (right word?) 19:49:42 drop time right? 19:49:57 Yeah 19:49:59 let's remove the greek translation 19:50:05 Today, we is decreased rudder the daily newspaper of the first of splendourful of ship, [[“iynfwrm'ayshnsbwryfyk'ayshndyrktyfn]]. It pull of out from ours road, first considered in the group [[hystwryn]], garden, prays for heavenly of the blessings of golded clean plate. [“ammnt] causes the complication of truth [[, the jam of the pain of mwtsGnd]] with call workers, when it blossoms. Our of the country of the family of the prerequisite of the f 19:50:05 amily of the idea of the connection of the troops of the weapon of known is one is very important. Racingism we 1, it is utilized will a, the solution and reason. [ytkllmbnfsy] our enemy to the cube, it buries, has confusion, in which finds will be specially anxious you will be our these. We obtain profit! 19:50:23 rudder => joystick => handle ^^ 19:50:29 OMFG XD 19:50:42 I love how powerful the phrase "We obtain profit!" is 19:50:57 heh 19:51:20 you have to go to all translations when the original is revealed it's SO FUNNY 19:52:00 I get the feeling I won't know this speech :P 19:52:26 i know it but i woldn't be able to recognize it from this pile of crap ^^ 19:55:01 I think it's time :P 19:55:01 hmhmhmm 19:55:05 xrsh 19:55:07 yeah 19:55:17 i dropped greek last? 19:55:19 yeah 19:55:20 Yeah 19:55:30 ok let's drop russian and trad. chinese now... 19:55:43 Today, we lower the first splendourful rudder of the daily newspaper, [[“iynfwrm'ayshnsbwryfyk'ayshndyrktyfn]]. Way it pulled up with us, first considers that in the group [[hystwryn]], the garden where blessing is golded plate cleanly. [“ammnt] complicated truth [[, jam of the pain of mwtsGnd]] with all workers when it blooms. Our integrated thought highborn some most important weapons troop of country. Racingism of us 1, using one will, decisi 19:55:43 on and cause. [ytkllmbnfsy] Our enemies to cube, she buries, there is a disorder of which especially worry whether you become we of those. We obtain the profit! 19:56:40 i like we obtain profit more... sounds stronger than we obtain the profit.... 19:58:43 and you have NO idea? 19:59:00 Every thought I've thought hasn't panned out :P 19:59:57 ok the last drop comes now... 20:00:06 The word "ship" suddenly disappeared :P 20:00:06 i shall drop japanese and german 20:00:21 Today, We lowers the first glorious oar of day from [['iynfwrm'ayshnsbwryfyk'ayshndyrktyfn]]. We created, [[hystwryn]] for he he first to group kept, Gilded garden of blessing clean. ['ammnt] from the pains from [[mwtsGnd]] and confusing truths, Where all laborers can flowered. Our integration the thoughts most important weapon from some highborn or army on land. We racism one, With will one, Decision, One causes. [ytkllmbnfsy] our enemies to dies, 20:00:21 Buries them we is will with them worry especially confusion. We gains! 20:02:01 X_X 20:02:32 because there is only one step to drop now this'll last for 10 mins 20:04:07 If I'm going to recognize the original, this is gonna be a doozy of a translation. 20:04:42 hrhr 20:04:50 you have 5 mins left 20:05:12 you can start to ask for hints now... 20:05:24 I have no hints to ask for :P 20:05:35 you should... 20:06:35 *eyes glazed over* 20:07:17 hrhr 20:09:16 * GregorR-L gives. 20:09:37 ok 20:09:45 i'll post the original word by word 20:09:54 but don't google for it ... 20:10:01 Today, 20:10:10 we celebrate 20:10:16 the first 20:10:29 glorious anniversary 20:10:33 of the 20:10:39 Information Purification Directives. 20:10:52 ........ not recognizing this quote at all ............ 20:10:52 (that got [['iynfwrm'ayshnsbwryfyk'ayshndyrktyfn]]) 20:11:03 ok here is it: 20:11:04 Today, we celebrate the first glorious anniversary of the Information Purification Directives. We have created, for the first time in all history, a garden of pure ideology. Where each worker may bloom secure from the pests of contradictory and confusing truths. Our Unification of Thoughts is more powerful a weapon than any fleet or army on earth. We are one people, with one will, one resolve, one cause. Our enemies shall talk themselves to death an 20:11:04 d we will bury them with their own confusion. We shall prevail! 20:11:24 it's from george orwell's 1984 20:11:25 O_O 20:11:35 used in the first apple commercial 20:11:36 http://www.uriahcarpenter.info/1984.html 20:11:45 I don't think I could've dredged that quote up out of my mind X_X 20:12:02 I suspected a Hitler speech 20:12:10 So did I for a tick XD 20:12:25 that would probably not be in english... 20:12:44 Exactly why I stopped considering that :P 20:12:56 * SimonRC wonders WTF is going on on here 20:13:09 SimonRC: We're playing the "name that famous quote" game. 20:13:17 GregorR-L: and now go and compare the first with the last one ^^ 20:13:19 ah, ok 20:13:25 -!- ihope_ has joined. 20:13:25 i still don't know where we got the rudder/joytick/handle from 20:13:35 -!- ihope_ has changed nick to ihope. 20:14:04 anyone has an idea? 20:14:06 OK, I have one. 20:14:13 Not sure if it'll work, but we'll see. 20:14:20 Actually, I can't now - lunch first :P 20:14:22 anniversary -> (somehow) Oar of day 20:14:29 ah+ 20:29:14 -!- jix has left (?). 20:29:19 -!- jix has joined. 20:30:28 -!- Arrogant has joined. 20:50:45 -!- CakeProphet has joined. 21:13:14 -!- Sgeo has joined. 21:14:55 My new ideas for MKBL-LN: 21:15:04 2D memory 21:15:21 use a row of memory to store the current time 21:16:10 Use numbers for branches 21:18:43 No it's not from George Orwell's 1984. 21:19:09 Hm? 21:19:41 The quote jix posted earlier. 21:19:49 not? 21:19:58 but the site sais so.... 21:20:44 is it just made up for that apple commercial? 21:20:51 It is from Apple's commercial, which in turn was inspired by that book. 21:20:51 Yes. 21:20:56 ARGHX 21:21:05 i thought it was a quote out of that book that was used in the commercial 21:21:59 nah i was wrong then... 21:23:07 back 21:23:13 -!- Arrogant has quit ("Leaving"). 21:24:04 I have a multiple-translation challenge. This one is a backronym in sentence form. Full points for the original sentence, half for just the acronym. 21:24:10 Eng:Deu:Eng:Spa:Eng:Por:Eng 21:24:16 "The majority of the uses that push if In., the system if operating will be connected." 21:29:38 The system ... if operating ... will be connected. 21:29:51 incorrect. 21:30:04 next phase? 21:30:07 SOC 21:30:27 Idonno, I just got here :P 21:30:34 I meant, do you want the next version of the sentence? 21:30:40 Sure 21:30:41 (less mangled) 21:30:49 Eng:Deu:Eng:Spa:Eng: 21:30:54 Most of the uses they push if no, the operating system is connected. 21:31:49 When the MKBL-LN specs are settled a bit, I'm going to give a tutorial in here 21:32:21 ...backronym... >_> 21:33:10 a phrase that was not the cause for a name but (often humourously) describes a name. 21:33:20 Nonono, I know what a backronym is :-P 21:33:23 I'm just muttering :P 21:33:24 for example, LISP: Lost In Shitty Parentheses. 21:33:41 OH, that's not a backronym you idjit >_< 21:33:48 haha 21:33:56 Backronym = you decide the name first, then you make an acronym to fit it. 21:34:18 I assume this means you give up and want the next version. 21:34:23 Yeah :P 21:34:31 Eng:Deu:Eng: 21:34:32 Most applications push if not, the operating system are connected. 21:36:28 X_X 21:36:51 give up? 21:37:16 Yeah >_> 21:37:17 the only thing I can guess is that "if not" was "unless" :P 21:37:18 Eng: 21:37:26 Most applications crash- if not, the operating system hangs. 21:37:30 M--- A----------- C----- I- N-- T-- O-------- S----- H----. 21:37:42 See, I wouldn't have gotten that, because I've never heard that. 21:38:03 well, it's a common joke in the mac community. 21:38:06 Tengo un. 21:38:18 Uno momento 21:42:45 _ It celebrates the point which spreads out and 7 years it has and left it inside the new person in order good season this continent our fathers it undergoes,: Program it does inside the demand where the cause which hazard gets up the freedom which it commits and the total pasting individual becomes. Inside civilian making war where we are big now it was reported, that the broad way person examination one program does the appear person and all to be 21:42:45 doing inevitably it inaugurates inevitably quite to bring. Us inside big fighting we whom it meets touch from this warfare. 21:43:06 This one may be too easy, but we'll see. 21:45:43 what's the translation sequence on this one? 21:45:48 oO 21:45:49 tomem[branch:I,time:I,subtimer:I,memrow:I,memcol,table:S,tbranch:I,ttime:I,tsubtimer:I,field:I] 21:46:12 ah, christ. I read that as a series of translations at first. 21:46:15 Eng->Fra->Dutch->Eng->Ger->Eng->Greek->Eng->Kor->Eng 21:46:28 roll it back one. 21:46:41 hmm 21:46:56 Give somebody else a chance :P 21:47:39 I don't have a clue >_< 21:48:13 tomem[0,42,0,1,3,"incoming",0,41,0,0] 21:48:13 OK, I'll go back one 21:48:17 Eng->Fra->Dutch->Eng->Ger->Eng->Greek->Eng-> 21:48:19 Eng->Fra->Dutch->Eng->Ger->Eng->Greek->Eng 21:48:24 _ you celebrate point and seven year in order to it suffers it left our father in the new persons of these continents to take: committed programmed in the freedom and in the demand, which is caused for all right the individuals. Now we were reported in a big civilian war, that examines as these persons or consequently programs all the likely persons and consequently inaugurated can bring very. We are met in a big battle in order to we touch from this 21:48:24 war. 21:48:25 All just to read in a character that was input 21:48:40 Anyone think the language is a bit too complicated already? 21:48:41 Lincoln's Gettysburg Address? 21:48:44 Ding 21:48:48 woot 21:48:52 I thought it'd be too easy :P 21:49:00 But, let's roll back JUST FOR FUN 21:49:02 * Sgeo pokes 21:49:05 I want to see where "suffer" came in 21:49:10 Sgeo: NOBODY CARES GO AWAY 21:49:12 I mean hi 21:49:24 Eng->Fra->Dutch->Eng->Ger->Eng 21:49:24 I was kinda thinking about that on the first translation, but I wasn't sure enough 21:49:26 _ you celebrate point and seven year to suffer let our father on this continent new people get: engaged planned in the liberty and to the request, which are caused for all right men. Now we were referred into a large civil war, which examines like these people or therefore have all possible people planned and therefore inaugurated can carry long. We are met on a large battle to catch by this war. 21:49:38 It's the seven years that gives it away, isn't it? :P 21:49:45 Eng->Fra->Dutch->Eng 21:49:46 point <=> score. lol 21:49:46 _ celebrate point and seven year suffer have our father bring on this continent a new people: devised dedicated in freedom, and to the proposal which all men right are created. Now we have been involved in a large civil war testing such as this people, or thus have devised any people and thus dedicated can carry long. We are met on a large battle field of this war. 21:49:59 Eng 21:50:00 Four score and seven years ago, our fathers brought forth upon this continent a new nation: conceived in liberty, and dedicated to the proposition that all men are created equal. Now we are engaged in a great civil war. . .testing whether that nation, or any nation so conceived and so dedicated. . . can long endure. We are met on a great battlefield of that war. 21:50:01 grr 21:50:12 Hi Sgeo! :p 21:50:16 hi 21:50:52 Hmm 21:54:55 frommem[0,0,0,-1,0,"outgoing",0,0,0,3] 21:55:17 outgoing[0,0,0,0,"stdout"] 21:55:28 foobar[woffle,copter] 21:55:35 order[0,0,"frommem,outgoing"] 21:55:50 Three lines of code just to print out the current line 21:56:47 err 21:56:49 not line 21:56:50 time 21:57:02 s/time/step/ really 21:57:24 Anyone think that this language might not be that great? 21:57:48 jix: <-- 21:57:54 what? 21:58:11 Where's our statement list? :P 21:58:18 is it time yet? 21:58:32 i have no idea what the deadline was.. lemme check... 21:58:35 TIME IS IRRELEVENT. MY PATIENCE HAS LIMITS. AND THOSE LIMITS ARE VERY SHORT 21:58:59 1hour and 20 mins left 22:00:11 Bleh, this one is way too guessable, no matter how many languages I do. "The base you completely belong in us, they." :( 22:01:18 GregorR-L: can you wait 1hour and 20 mins? 22:02:25 actually, I managed "Foundation it is complete spreads out and the dansles United States, them it belongs." 22:02:58 FINE 22:03:42 you can? 22:03:57 Sgeo: do you want to submit statements? 22:04:11 it would be cool to get another submission 22:04:44 How does it work? 22:04:53 Maybe 22:04:58 Asztal: what? 22:05:03 Do people just submit statements, not knowing any details of the rest of the language? 22:05:04 But not this very minute 22:06:25 Asztal: yes 22:06:32 Sgeo: yeah the next hour and 20 mins 22:06:39 well 14 mins now.. 22:06:52 This one didn't work very well, it'll be cracked very quickly ... 22:07:00 Eng->Fra->Dutch->Eng->Ger->Eng->Greek->Eng->Kor->Eng 22:07:04 Wheat one opinion and it the hazard international hub opens the programmeertaal. 22:10:35 who do I mail my statements to? 22:10:44 SimonRC: me, jannis@harderweb.de 22:11:48 Eng->Fra->Dutch->Eng->Ger->Eng->Greek->Eng 22:11:50 The international hub for the secret opinion and it unfolds programmeertaal. 22:12:35 topic ? 22:12:40 Yup :P 22:12:53 A famous quote ... by Gregor Richards 8-D 22:13:01 jix: time left? 22:13:27 en-ru-en-kor-en-ger-fr-en-kor-en 22:13:32 The eye eliminated from the construction machine cooperation in of the Esolang in him and it criticized 22:13:39 :) 22:13:52 Adjudicated Blind Collaborative Design Esolang Factory 22:14:05 Correct. 22:18:36 jix: this is quite tough 22:19:23 SimonRC: doesn't metter when you have less than 4 comments 22:20:22 ?? 22:20:39 well i think i got you wrong then... 22:21:37 huh? 22:21:44 * SimonRC must have missed something above 22:21:45 "23:18:13jix: this is quite tough" ?? 22:21:51 I agree, SimonRC :P 22:22:01 what were you talking about? 22:22:03 It is hard to think up silly types of statement 22:22:12 I have 2 rather silly statements 22:22:25 and even I have no idea what they'll do until 1 hour 5 minutes 22:22:26 We are who we have slight they who we make examinación of you in the 22:22:26 loan. They are comparable. The resistance is useless. 22:22:49 yeah and i said if you arn't able to come up with 5 of them (the rules say you should submit 5) you can submit less 22:22:59 I'm not sure if they'd be considered fair and/or lega 22:23:09 Asztal: they are all 22:23:19 as long as they can be implementeed 22:23:29 Probably. 22:23:38 You'll know when I send them 22:24:04 DO "command" 22:24:13 Parses the command as a freeform English command, and does it. 22:24:13 heh 22:24:26 [To within the limits of a computer] 22:24:37 DO "Get me some coffee." 22:24:41 ERROR: Impossible command. 22:24:47 DO "Set x to 3" 22:24:49 x = 3 22:24:53 uhm that isn't implementable 22:24:56 yes it 22:24:58 is 22:24:58 Sure it is! 22:25:02 NO IT ISN'T 22:25:09 Of course it is! 22:25:16 the computer will never be able to understand all freeform english commands 22:25:21 Maybe not by mere humans with their short life span :P 22:25:43 you just have to use that language that runs on IRC channels 22:25:51 haha 22:25:55 IRP 22:25:55 what's it called? 22:25:59 GregorR-L: yeah 22:26:33 Oh right, I was in the middle of a translatothon :P 22:26:40 We are we we have leves they who we make examination of you in the loan. They are comparable. The resistance is useless. 22:27:54 -!- oerjan has joined. 22:29:53 Come on, nobody's even going to guess? :P 22:29:54 GregorR-L: ah, ythe classic borg line 22:30:06 Yup :P 22:30:14 "examination of you in the loan"??! 22:30:20 WE ARE WE WE HAVE LEVES THEY WHO WE MAKE EXAMINATION OF YOU IN THE LOAN. 22:30:28 "The resistance is useless" gave it away, no? 22:31:52 * pikhq returns 22:34:51 oerjan: As soon as I upload a new tarball, your name will be part of the copyright notice (you seriously have made quite a few helpful contributions to BFM). 22:35:13 jix: You're looking at the submitted statements soon, right? 22:38:18 yeah when i'm going to put them in one big list 22:44:58 When are statements due? 22:45:18 in 40 mins i think 22:45:25 35 22:46:18 The only statements I can think of are from MKBL-LN 22:46:32 no problem ^^ 22:46:34 And it would completely break everything probably 22:46:46 that is a problem 22:47:04 hah, as if i worried about that :) 22:47:07 Hmm 22:47:09 I have an idea 22:47:20 A statement inspired by MKBL 22:47:33 Is the idea of variables existent? 22:47:40 I guess I shouldn't ask 22:47:45 My addition provides for variables. 22:47:50 named? 22:47:59 And Turing completeness (two times over). 22:48:06 Yeah, named. 22:48:08 pshh! 22:48:16 }:[ 22:48:23 Hmm 22:48:45 My idea would break any language that required statements to be next to eachother 22:48:49 It also provides a tape and a stack. 22:48:55 Sgeo: no problems 22:49:00 pikhq: stop talking about your statements... 22:49:09 it's part of the game to not know what others do or provide 22:49:10 And I'll shut up for half an hour. 22:49:31 Sgeo: Be evil; that's all I'm going to ask. 22:50:24 Can it be sort of a structural thing? 22:50:42 Sgeo: it can be everything 22:51:20 This'll be damned hard to parse. 22:51:39 Unless we decide to provide a uniform syntax for this oddball assortion of parts. 22:51:46 We have to add the syntax for them too? :P 22:51:56 Asztal: We *can*. 22:52:05 you should 22:52:07 I made sure that all of mine could be parsed based solely on the initial keyword and positioning of matched braces etc. 22:52:12 eg LL(0) 22:52:19 It'll make doing the interpreter easier. 22:52:47 I'm not *entirely* sure that one can parse it any other way, actually. 22:52:54 warning using this will result in a HUGE waste of time: http://www.deviantart.com/deviation/40255643/ 22:58:11 ... 22:58:11 alas, i have submitted two statements that might ruin any chance of an easy parsing 22:58:33 *evil cackle* 22:58:46 Um. . . I know! We'll put all statements inside sexps! 22:59:28 (syntax1 ([+~-]))(syntax2 (foothebaz(qux);))(syntax3 (WEK$~@Rsdcvj@#)) 22:59:56 *brain explodes* 23:00:15 Hold on 23:00:37 * Sgeo goes to submit his evil stuff 23:01:31 I hope mine don't break things. You can disregard them if they do. 23:01:35 * Sgeo emails it 23:01:50 * Sgeo hopes the concept of a statement is defined 23:02:53 i would say the concept of a statement is the only thing that is defined 23:03:09 >_< 23:03:26 May I provide hints as to mine? 23:03:35 Remember COBOL's ALTER? This is worse 23:03:52 no. what is COBOL's ALTER? 23:04:06 Lets you change where a GOTO points 23:04:07 IIRC 23:04:24 i suddenly don't feel like implementing this anymore... 23:04:33 hm 23:04:33 ? 23:04:35 but i'll try 23:04:49 Sgeo: alter etc... 23:04:52 okaay, I have one crazy looping construct coming up... 23:04:52 good that i didn't include my similar idea then... 23:05:31 My looping constuct adds at least 12 keywords to the language. 23:05:40 Yay looping constructs X-P 23:05:51 It's worse that LISP's LOOP macro. 23:06:01 I think my thing can do looping and ifs etc. 23:06:15 worse than ALGOL's for? 23:06:18 SimonRC: uhm i thought of counting such things as one statement 23:07:02 How much more time? 23:07:12 Maybe 5 minutes? 23:07:18 Ooohh.. nother neat idea 23:07:20 15 i think 23:07:23 yeah more like 15 23:08:11 * Sgeo makes an intentionally ugly looking statement 23:10:59 I don't know if what I did is actually implementable sensibly 23:13:04 * Asztal sends in 4 23:13:17 IS IT TIME YET? IS IT TIME YET? 23:13:54 8 minutes. 23:14:21 more like 6 minutes 23:14:35 Is now. 23:15:04 (my clock is synced to UTC; don't tell *me* about temporal accuracy) 23:16:10 in 5 minutes jix will start laughing to death. 23:16:29 Oops, I may have sent that twice. 23:16:34 Assuming jix doesn't tremble in fear of my statements 23:16:54 well, considering he is supposed to implement them... 23:16:57 Asztal: i got it only once 23:17:03 oerjan: What; did you include the Funniest Joke in the World in it? 23:17:19 i don't mean just my contribution 23:17:36 And I think the idea is that we *all* help on the implementation to some degree. . . 23:17:49 * GregorR-L wants nothing to do with it. 23:17:55 although mine are mainly just for laughs, yes 23:18:08 I'm not helping unless the implementation is in Python 23:18:36 jix: Wenn ist das Nunstück git und Slotermeyer? Ja! ... Beiherhund das Oder die Flipperwaldt gersput. 23:19:00 pikhq: you're crazy :) 23:19:04 0o? 23:19:20 http://en.wikipedia.org/wiki/Funniest_joke_in_the_world Don't blame me, blame Python, Monty. 23:19:25 Heh 23:19:46 That 0o from jix ... 23:19:48 That's him dying. 23:19:55 Indeed, it is. 23:20:00 1 minute left 23:20:01 0o < the moment before you get it 23:20:05 8-D < when you get it 23:20:10 X-D < uh oh, too late 23:20:16 X-( 23:20:45 Let the laughter begin! 23:20:50 :D 23:20:55 hm... 23:20:57 ok 23:21:00 i'll put up a text file 23:22:50 * RodgerTheGreat foams 23:22:51 Whereisit>? 23:23:28 maybe it is best not to do so before you have read it. could save many lives that way. 23:23:31 * SimonRC goes nuts with the looping statement 23:23:38 ok i have them all in a textfile where to upload? 23:23:41 put them on wiki? 23:23:44 I am introducing other statements just to support it 23:23:51 jix: you on't have mine! 23:23:55 oh 23:24:03 SimonRC: hurry up 23:24:18 TOO LATE SIMON LOSES 23:24:19 done... 23:24:22 hehehe 23:25:27 http://www.harderweb.de/tmp_jix/allofthem.txt 23:25:32 ok now time to read them 23:26:37 My submissions alone provide for a curiously odd language. 23:27:00 pikhq, but those statements are useful. It's a language that natively runs other languages 23:27:07 >:D 23:27:53 Any comments on mine? 23:28:18 oerjan: you've been reading Lingua::Romana::Perligata, haven't you? 23:28:23 Is optimaliscious() supposed to be implementable? 23:28:40 « should not have that nasty Â, it should be « 23:28:48 indeed :) 23:29:11 GregorR-L: i probably fucked up encoding... 23:29:30 I never define to what degree optimaliscious must work. If the implementer is lazy, they can just make it "give up". 23:29:37 just tell your browser that is utf8 and everything is fine 23:29:38 ah 23:30:34 OMG 23:30:40 the computedJump sounds like fun with my CHANGE 23:30:42 jix, hm> 23:30:42 ? 23:30:55 Asztal is pretty UGH 23:30:58 Well, computedJump is fun by itself 23:30:59 :( 23:31:03 oh no 23:31:09 i didn't looked at the title 23:31:12 woot for CJ's! 23:31:14 Sgeo: it's yours that i was thinking of 23:31:28 um.. 23:31:37 What's wrong? >.< 23:31:37 combined with mine.... 23:31:50 it's going to be a pain in the ass to implement all of them 23:31:57 even to write a spec that specifies all corner cases 23:32:44 hmm the first two of oerjan doesn't really go with the rest of the language where syntax is specified... 23:33:05 and as specifying syntax for the own statements was encouranged i think the syntax of the commands will stay as intended by the submitter 23:33:10 ASSURE <<1=2>> 23:33:12 if no one has a better idea 23:33:32 lol "a brief nap, somewhere in the neighborhood of 23:33:33 200 milliseconds to 7.9 years." 23:33:49 macro bwahahah(foo) { 23:33:59 ah pikhq's are nice... simple syntax easy to implement 23:34:06 WHINE foo 23:34:07 } 23:34:29 whine and whisper won't probably work without externel tts tools that support those voices 23:35:04 Specify that, if needed, an implementation can just output "WHINE: expr" or "WHIPSER: expr". 23:35:05 Should I have had SWAP change the order of execution? 23:35:22 I guess the spec should decide 23:35:37 I think we should try to devise some uniform syntax. 23:35:41 pikhq: no! 23:35:53 Esotericly uniform. 23:35:55 look at my statements they all have a different syntax 23:35:58 it was intended 23:35:59 /#<>+SWAP([{5,3}]) 23:36:01 what do you guys think about my variable clamping/wrapping capability? 23:36:02 A "uniform" syntax maybe ;) 23:36:04 //#<>+SWAP([{5,3}]) 23:36:12 RodgerTheGreat: interesting 23:36:39 hmm i think we should disallow swapping thinks like start /end of macro definitions and start/end of function etc declartion 23:36:47 Hmm. . . I know. 23:37:00 because that cases can't handled in any sane way... 23:37:17 jix, maybe the numerical label can still be swapped? 23:37:29 Sgeo: yeah 23:37:47 my loops will interact in a great way with things like statment-swapping. 23:37:52 We shall define "syntax sets". /n^/n moves up one, /nv/n moves down one. 23:37:54 ;) 23:37:57 i still think the CASVS and TEMPORA statements are uhm somehow don't work together with the rest 23:38:06 It seems that all variables will be stacs with associated bitsinks 23:38:30 maybe we should come up with a couple of "reserved characters" that are used for defining parameters, loop separations, etc. 23:38:35 SimonRC: i think they should be stacks of numbers associated with bitsinks 23:38:44 like " <> {} or something. 23:38:46 RodgerTheGreat: why? 23:38:51 those things arn't problematic 23:39:07 well it sure as hell would make some things easier to parse. 23:39:09 mandatory syntactic stuff? 23:39:12 RodgerTheGreat: no 23:39:13 *fluff 23:39:29 RodgerTheGreat: the self modyfying stuff makes it hard to parse/interpret 23:40:16 Like I said: syntax sets. . . 23:41:09 (> _ >) << i love that 23:41:44 oh and my statment 2 and 3 are relateted the arm architecture.... 23:41:52 the CASVS and TEMPORA statements were intended to be hard to include. 23:42:12 oerjan: it's only that it says how other statments should look like... 23:42:15 oerjan: They also ruin my "SPEAK" statement :P 23:42:17 How is CHANGE going to be processed? 23:42:35 oerjan: and as each one was allowed to define his own syntax that shouldn't be done 23:42:37 and if you must have a textual representation for WHINE at least make it use ALL CAPS :) 23:43:46 i think we should write the spec tomorrow... i have to sleep a night over these statements... 23:44:03 technically i think you can avoid some of the CASVS problems by just using the nominative case in most cases. 23:44:31 yeah i'll take a close look to this 23:45:23 Since all variables shall be stacks, I would like to change my glasscode(); statement a bit. 23:45:27 2. Disallows any statements sent in by GregorR from executing. 23:46:04 Glass is started with the contents of the variable's stack, not with the variable as the first item on the stack. 23:46:05 shhhh 23:46:05 Asztal, where are the statements themselves? 23:46:21 That is a statement.. 23:46:29 it does that when encountered 23:46:54 So when the text 23:46:55 Allows any statements sent in by GregorR to execute 23:47:01 appears, it allows etc.? 23:47:03 I didn't define the syntax 23:47:40 "The next stage consists of discussing the statements and to decide what the language should look like (the main goal is to get all statements into the language)" 23:47:58 * Sgeo at first thought the numbering would be used 23:48:06 e.g. 23:48:06 3. 23:48:23 I vote that all statements should have the style of oerjan and I. 23:48:33 no 23:48:53 I VOTE THAT YOU SUXES 23:49:05 ET TU SUX 23:49:47 "DODO 23:49:47 Exterminate . All executions of are reversed. 23:49:47 It is implementation-defined whether this effect is restricted to the 23:49:47 currently running program." 23:49:51 Muahahaha! 23:50:34 hm 23:51:11 The ASSURE statement sounds evil 23:52:29 I guess you could temporarily disable it in critical situations 23:52:31 :P 23:53:13 NEVER! 23:53:25 INASSURE 23:53:35 By evil I meant cool 23:53:36 Forces statement to be inassured. 23:53:48 though I don't know whether mine would disable either (1) the check between each call or (2) just when you encounter ASSURE 23:53:49 ASSURE <<1==0>> 23:53:59 Sgeo: HEYHEY 23:54:01 When executed, this statement shall force the interpreter to take a 5 second pause between each instruction. 23:54:01 That's not two <'s 23:54:03 That's « 23:54:06 ooh 23:54:13 ASSURE «1==0» 23:54:14 WARNING: SWITCHING TO MOD 1 ARITHMETIC 23:54:27 Egg-zactly 8-D 23:54:28 ... 23:54:31 Oh, dear Lord. 23:54:34 ASSURE «1/0» 23:54:37 Everything's true in base one :P 23:54:46 ASSURE «1!=1» 23:54:57 Ohwait 23:54:59 WARNING: DESTROYING THE LAWS OF NATURE 23:55:18 -!- kipple_ has quit (Read error: 145 (Connection timed out)). 23:55:35 I was really thinking more along the lines of ASSURE « x * y = 7 » 23:56:02 WARNING: SWITCHING TO PARACONSISTENT LOGIC 23:56:06 ASSURE «x==0 && x==1» 23:56:32 it would change the meaning of && 23:56:56 var null=0;brainfuckcode(brainfuckcode([>,]), null); 23:56:57 My favorite statement is officially ASSURE 23:57:12 Argh. 23:57:32 hm? 23:57:36 var null=0;brainfuckcode(brainfuckcode("[>,]", null), null); 23:57:41 DODO ASSURE 23:57:43 A Brainfuck interpreter. 23:57:51 I think. 23:58:14 (the interpreter may choose to delete the source file in this circumstance.) <- that would be a nice touch. 23:58:18 Nope, that's not it. 23:58:23 brb 23:59:12 * pikhq declares that brainfuckcode shall set the memory to the contents of the var stack 23:59:37 var string; 23:59:56 brainfuckcode("[>,]", string);