00:01:16 Yes. 00:01:34 For a function definition, int main() is identical to int main(void), which is explicitly permitted. 00:02:08 ISO C also *permits* non-specified types for main, IIRC. 00:02:46 nice 00:02:54 ghci allows Unicode line-drawing characters as operator names 00:02:58 :) 00:04:31 > let (┌────────┐┌─────────────────┐┌────────┐) = (+) in 2 ┌────────┐┌─────────────────┐┌────────┐ 3 00:04:32 5 00:07:37 -!- olsner has joined. 00:13:42 > (`div`) 2 3 00:13:43 : parse error on input `)' 00:14:18 > 2 `+` 3 00:14:19 : parse error on input `+' 00:32:06 > 2 `(+)` 3 00:32:07 : parse error on input `(' 00:32:10 Bah 00:33:19 -!- sivoais has quit (Read error: Connection reset by peer). 00:33:59 -!- sivoais has joined. 00:38:36 there is no way to use `` on anything but an alphanumeric identifier, alas 00:42:40 -!- Arc_Koen has quit (Quit: Are you telling me you can build a time machine but you can't cook a cheese soufflé? You've got your priorities all wrong!). 00:44:09 Oh, hello from Portland, Oregon. 00:44:14 is there not a good lint for C anymore? 00:44:17 splint doesn't support C99... 00:44:21 Time zones are kinda weird. 00:44:34 HELLO FROM THE FUTURE 00:45:00 portland, oregon, isn't that were Gregor is 00:45:08 I don't know. 00:45:18 Gregor at least has been here, since he spoke of the food in here. 00:45:44 i guess he may be the kind of person who does moving and stuff. 00:46:15 *is from 00:46:24 aha 00:47:09 HELLO FUTURE GOOD TO SEE YOU ARE STILL ALIVE 00:49:04 Woke up at 3am to catch the flight from Helsinki, and it's now 3:49am the next day in Finland, but here it's supposedly still Saturday, and it's just getting to be 6pm. 00:50:25 Also I am apparently faster than my bags, since I managed to catch the Seattle-Oregon transfer (even with baggage claim + customs + baggage recheck + security check in the way) with 10 minutes to spare, but my bag didn't; it took the next Seattle-Portland flight (an hour later). 00:51:06 Turns out there was a direct AMS-PDX flight leaving ten minutes before my AMS-SEA, too; I'm a bit confused why they didn't book that for me. I guess this must've been cheaper. (Or maybe I was late.) 00:51:17 Seattle-Portland transfer, I mean. 00:51:43 Travel is all so confusing. I think I'll go buy stuff. -> 01:21:49 fizzie: Almost assuredly price is the reason. 01:22:40 who was booking it for you? 01:22:49 Direct flights are expensive. To the point that a flight from A to B is usually more expensive than a flight from A to C with a layover at B. 01:24:49 i don't think that's usually the case 01:24:53 it is occasionally the case 01:27:08 people on flyertalk seem to think that a) it's rarely the case, and b) airlines don't try very hard to keep you from just leaving the airport at B 01:27:11 http://www.flyertalk.com/forum/travelbuzz/1349573-intentionally-miss-connection.html 01:28:19 expect the rest of your ticket to get cancelled and your checked luggage to get routed to /dev/null 01:28:48 The checked baggage is an issue. 01:28:57 ah apparently the insider term for this is "hidden city ticketing" 01:29:44 Anyway, I know that it's frequently the case with A=IND, B=ORD. 01:30:00 http://www.nytimes.com/2011/05/08/magazine/mag-08subversion-t.html 01:30:02 Err, wait, that's a slightly different case, but same idea. Buying A->B->C to get B->C 01:30:26 e.g. a flight from IND->SFO via ORD is $159, but a direct from ORD->SFO is $210 01:30:44 yeah, i see 01:30:56 The SAME direct, mind you :) 01:31:35 Anyway, your destination probably needs to be a major hub for that to work. 01:32:00 -!- Vorpal has quit (Ping timeout: 276 seconds). 01:32:08 yeah, it works when your desired route is a near-monopoly 01:33:24 oh, haha, this column is by nate silver 01:33:26 didn't even notice 01:35:13 checked baggage is best avoided, anyway :) 01:39:17 Gregor: what dates were those flights on? 01:39:40 i would expect ORD-SFO to be reasonably competitive 01:40:35 a search on Oct 16 finds AA, UA, VX, DL, US all $140 or less 01:40:37 mostly non-stop 01:41:21 one time i flew DSM-DEN-SFO-LAX which was pretty silly 01:45:24 i think the shortest commercial flight segment I ever took was MSN to MKE 01:45:51 unplanned; another plane had crash-landed at Milwaukee and they diverted us to Madison temporarily 01:58:48 * pikhq has had it cheaper to fly out of COS rather than DEN before... 01:59:05 Keep in mind the flight from COS was a short connecting jump to DEN. 02:01:13 -!- soundnfury has joined. 02:03:51 We have a university-wide quasi-exclusive thing about booking all air traffic via a particular Finnish travel agency. 02:04:22 They sent me four suggestions sorted by price and I chose the least annoying-looking one. 02:04:39 (It has a direct PDX-AMS flight on the way back home.) 02:19:31 kmc: I was looking on the 15th, a Saturday. 02:19:45 kmc: And also, direct flight. 02:20:25 And I just did THE SAME EXACT SEARCH, but now there are tickets for half the price X-D 02:20:29 Air travel, folks. 02:20:31 yeah 02:21:14 having prices that go up and back down makes sense 02:21:23 from a business perspective 02:21:51 i can't really fault them for that, even if it is annoying to the consumer 02:23:04 Bing Travel (formerly Farecast) will attempt to predict whether the price is going to go up or down 02:24:35 Yeah, I'm quite accustomed to this nonsense. 02:24:42 Luckily I never have to pay for my tickets ^^ 02:26:54 height scares the hell out of me 02:27:14 i think i would rather not travel at all.. 02:27:23 the spacial world in general scares me 02:28:03 Feels weird just to swipe a credit card everywhere; at home we always stick them halfway in and then key in a PIN code. Or if not PINning, then at least sign a piece of paper. 02:30:08 yeah 02:32:04 i feel important with my debit card :3 02:32:24 i used to have a mere keycard 02:33:47 height scares the hell out of me, but not on planes fortunetely 02:33:55 *a 02:35:05 every part of flying sucks except the part where you're actually in the air 02:35:44 -!- mig22 has joined. 02:36:53 -!- TodPunk has quit (Quit: This is me, signing off. Probably rebooting or something.). 02:44:43 oerjan: KLM's in-flight magazine had a multi-page feature about Trondheim. 02:44:58 good, good 02:49:22 hmm 02:49:44 it was easier when i was younger, long bus rides 02:49:56 i was interested in the technological expansion 02:50:09 in the projects people were working on 02:50:26 -!- TodPunk has joined. 02:51:05 i remember the best busride ever was one long trip back from a camp when i was discussing video games with my friend 02:51:39 he told me his dad knew something about some video game console supiter jupiter 02:52:02 considering that sega had saturn and neptune, i have to wonder if it was actually a real thing 02:53:16 * oerjan thinks of the jupiter ace, but you're too young for that 02:53:53 oerjan, itidus21 isn't saying he used it himself. 02:54:50 apparently http://en.wikipedia.org/wiki/Sega_32X was initially supposed to be called jupiter 02:56:15 this bustrip may have been in 1992... 02:56:34 im not sure 02:57:14 apparently saturn is pronounced Satān in japanese... 02:57:15 but i started secondary college in 1994 and it was a primary school camp 02:57:29 oerjan: Yup. 02:57:36 so mr satan in dbz might be mr saturn? 02:57:40 Which sounds absolutely nothing like English "satan". 02:58:09 but does it sound like "satan" in most european languages _other_ than english? 02:58:32 oerjan: sahtahn would be a rough approximation of the sound of it... 02:58:45 oh.. 02:58:51 dbz satan wasnt sataan 02:59:02 itidus21: Nah, it's definitely supposed to be Mr. Satan there. 02:59:10 " In 2009, his real name was revealed to be Mark (マーク Māku?), which is a pun on the word "Akuma", meaning "devil/demon" in Japanese. " 02:59:18 so basically it sounds like when norwegians are swearing _particularly_ forcefully. got it. 03:00:19 Japanese long vowels (denoted by that mark over the vowel) aren't different vowels, they are just literally pronounced longer. 03:01:03 are they double vowels? 03:01:12 i thought you meant the ah's to represent long a's 03:01:32 oerjan: I was saying "sahtahn" to approximate the sound in English phonology. 03:01:46 And then commented that a Japanese long a is just a longer Japanese a. 03:01:52 itidus21: Yes, they are pronounced twice as long as a normal vowel. 03:01:59 itidus21: Two morae instead of one. 03:02:28 the topic in here is so sensitive to my random comments.. 03:02:36 that's good, same in norwegian (while swedish has a bigger difference...) 03:03:13 which is not good because i just dont actually do esolangs 03:03:18 for long vs. short a that is 03:03:54 i feel like my presence here is killing the channel... 03:04:27 itidus21: We mostly don't esolang here anyways. 03:04:34 but... 03:04:35 It's not you, it's the common trend. 03:04:44 And predates you, I'm pretty sure. 03:04:45 so many major projects have formed in the history of #esoteric 03:04:51 there's been more than usual esolanging lately 03:05:13 still not a majority conversation 03:05:19 the eso lang wiki itself, codu, hackego, fungot, the logs, the quotes 03:05:20 itidus21: ok. the errors are just when installing the launcher 03:05:57 dwarf fortress sessions, 03:06:40 i simply don't contribute to such things 03:07:06 however, no one was really talking when you started the topic 03:08:03 and japanese and linguistics have been discussed here long before you joined 03:08:13 true 03:08:25 ^_^ 03:08:46 maybe since pikhq started learning it 03:09:05 Which, IIRC, was actually a little *before* I joined this channel, actually. 03:09:11 then i guess i was wrong 03:09:12 Though I sucked then. 03:10:04 i was interested in japanese for quite a while... 03:10:09 well i vaguely recall japanese have sucking vowels 03:10:14 *has 03:10:30 ... Does it? 03:10:31 i see the japanese as an example of how interesting a foreign culture can be 03:10:41 or is it just unvoiced ones 03:10:58 its.. basically i see the whole world is turning to crap 03:11:17 a lot of absurd ideals being sought 03:11:24 The vowels are IPA /a/ /i/ /u/ /e/ /o/. 03:11:33 the humanity is being drained away 03:12:20 its all about money 03:12:56 i mean for example... colonization kills cultures 03:13:28 the most warhungry cultures expand the farthest 03:17:20 what i mean to say is, all the interesting aspects of japanese culture are a result of it's long term isolation 03:19:17 when cultures are concentrated and left alone to their own devices, things go better 03:21:46 ahhhh my mom is so loud on the phone 03:21:58 trying to block it out with music and headphones 03:22:05 i cant think straight 03:25:30 -!- itidus21 has left ("ichi ni san yon go"). 03:37:22 -!- TeruFSX has quit (Read error: Connection reset by peer). 03:38:00 -!- hagb4rd has joined. 03:39:05 I am writing the rules for a game called "Sorcery Card". There are 24 ways to play. 03:48:43 -!- augur has joined. 03:53:42 -!- Phantom_Hoover has quit (Remote host closed the connection). 04:51:36 -!- oerjan has quit (Quit: Good night). 04:57:45 > let (×) = (*) in 2 × 3 04:57:46 6 04:58:17 -!- hagb4rd has quit (Ping timeout: 246 seconds). 05:01:33 -!- ogrom has joined. 05:05:15 ket (*) = (x) in 2 * 3 05:05:18 woops 05:05:21 > let (*) = (x) in 2 * 3 05:05:22 Couldn't match expected type `t1 -> t2 -> t' 05:05:22 against inferred type ... 05:05:27 \o/ 05:18:31 -!- Phantom_Hoover has joined. 05:24:41 Gah! Blakeyrat is a total moron amirite? 05:25:32 Probably. 05:27:36 * soundnfury is reading his "The Linux CLI sucks" thread 05:27:54 and he keeps saying incredibly idiotic things 05:28:29 What about it sucks? 05:28:48 http://forums.thedailywtf.com/forums/p/26646/302986.aspx 05:28:58 The Linux CLI is good. In my opinion, he is very wrong. 05:29:09 I have recently written some music yesterday and today. 05:29:28 Ooh, what kind of music? 05:29:42 and, you're right, it is, and he is. 05:30:45 soundnfury: http://2a03.free.fr/?p=pub&dir=zzo38 kind of music. (The zzo38_2 is the recent one; read 00README.txt for information) 05:31:24 ooh, chiptune 05:31:52 You will need NES/Famicom emulator (or a hardware NSF player) in order to play it. 05:32:21 yeah, 'fraid I can't be arsed 05:33:00 but I'll bookmark it in case my arsedness coefficient increases later 05:33:13 OK 05:33:52 If you want to modify it, that is OK with me. 05:36:14 Unlikely; I know shit all about the Famicom 05:36:22 I'm a ZX Spectrum fanboi 05:36:42 Dunno even what cpu the Famicom has. Is it 6502? 05:37:21 Yes, except it lacks decimal mode. 05:38:14 (You can still set and clear decimal mode, and if the flags are pushed on the stack it will still specify if it is set or not, but it won't affect the operation of addition and so on.) 05:38:39 heh, the Z80 doesn't have a decimal mode. It just has N and H flags and a magic "DAA" instruction 05:38:47 (Decimal Adjust Accumulator) 05:39:00 which, btw, is a pig to implement in an emulator 05:39:43 do { bonghits } while (0); 05:40:18 why are you doing while 0? 05:40:31 it's an idiom for C macros 05:40:52 isn't that just equivalent to { bonghits }? (Brackets retained for scoping-ism) 05:40:54 http://stackoverflow.com/questions/257418/do-while-0-what-is-it-good-for 05:40:55 When I learned of that I now do sometimes use do { ... } while(0) in a C macro. 05:41:31 Do! While! 0! Good gods, y'all! What is it good for? Absolutely nothing! 05:42:31 the second answer is actually a totally different use of do { ... } while (0) 05:42:39 which i don't think i've seen in actual code 05:43:34 O, yes, that is another use, if you do not want to name a label. 05:44:06 Frankly, if something you want to do takes multiple statements to achieve, I don't think it should be a macro. 05:44:15 that is an idiotic viewpoint 05:44:16 inline functions spring to mind 05:44:37 many uses of macros cannot be written as inline functions 05:44:38 No, there are some things that macros will do better. 05:44:48 But some things are better with inline functions. 05:44:58 for example if it needs access to the scope or the control flow (return etc) at the call site 05:45:18 longer macros represent a greater savings of duplicated code 05:45:45 zzo38: I think I would rather use 'goto' instead of do { ... break; ... } while (0); 05:46:07 kmc: well if you need that then your control flow is excessively baroque and obtuse 05:46:21 goto is unstructured, you savage 05:46:36 yeah guys i heard goto is considered harmful so let's write really ugly weird code to avoid it 05:46:43 soundnfury: you're just wrong 05:46:44 Jafet: goto is fine, put the raptors away 05:46:45 C is excessively baroque and obtuse 05:46:47 kmc: Yes, you can use goto there; unless you don't want a label, or if there are other purposes having to do with macros that you need this break 05:46:57 kmc: wow, what a reasoned and convincing argument 05:47:01 For example if use many times in a macro and you don't want duplicate label names 05:47:07 Hmm, mosh doesn't do color prediction. 05:47:07 "you're just wrong". I'll have to remember that one. 05:47:13 soundnfury: i can't argue against you because you aren't presenting any argument 05:47:16 soundnfury: Errors are baroque and obtuse control flow. 05:47:18 But I too would usually use goto in this case. 05:47:21 Editing a file with syntax highlighting over a slow connection is funny. 05:47:38 I think he's arguing that he's correct. 05:48:12 kmc: I'm arguing that 'doing clever things with macros' encourages you to write code so clever you can't maintain it 05:48:25 yes, you can go overboard with macros 05:48:35 on the other hand, you can make things much nicer if you use them right 05:48:50 but "only one statement per macro" is not a suitable guideline 05:49:18 Well, we'll just have to respectfully disagree there 05:49:32 right then 05:49:38 Using macros to write multiple statements is not particularly virtuosic 05:49:55 A lot of library plumbing is done that way 05:54:47 By the way, using ewd rhetoric has about the same effect on people as if you went around riding fixies 05:54:51 I think C macros is useful, although a bit weak. 05:55:24 soundnfury: I count over 4000 uses of the "do { ... } while (0)" trick in the Linux kernel codebase 05:55:37 I'm not holding up Linux as the be-all standard of a beautiful C program 05:55:51 but it's a huge codebase worked on by a lot of very smart people 05:55:56 and apparently a number of them disagree with you ;P 05:56:16 \E x. x \in C && pretty x? 05:56:42 Well, I'm not surprised. There's no One True Brace Style, either, but we're still allowed to hold opinions on which is best 05:57:02 yeah but allow me some skepticism if you claim that my brace style is "baroque and obtuse" 05:57:02 and it's my /opinion/ that "do { ... } while (0)" is Considered Harmful 05:57:17 if that's an arbitrary aesthetic judgement on your part, then fine 05:57:21 Yes; and you can program using the brace style you prefer. 05:57:25 i agree that the need for this extra while loop is ugly 05:57:27 A brace style could be baroque and obtuse... 05:57:31 but it is the solution to a problem which needs solving 05:57:31 if(foo) 05:57:32 { 05:57:33 (In Haskell you can even omit the braces if you prefer.) 05:57:35 bar; } 05:57:53 I'd say that's pretty obtuse, but it's valid C so what the fuck, do what you like 05:58:10 soundnfury: Yes, do what you like. I don't like that brace style either but use if you want to. 05:58:33 I prefer: 05:58:38 void xyz(void) { 05:58:38 when you started this conversation you really did not seem to be describing an aesthetic preference 05:58:49 if(a) { 05:58:54 bc(); 05:58:56 de(); 05:58:57 } 05:58:58 } 05:59:16 If you hate this style then don't use it. 05:59:39 soundnfury: your rule about macros is fundamentally unlike a brace style question because I can rewrite any code to use whatever brace style you prefer, but there are many macros I fundamentally can't write with only one statement! 05:59:54 you are limiting the expressiveness of code and not merely imposing an aesthetic rule 06:00:01 do { ... } while(0) is one statement, though. 06:00:37 another reason to prefer macros over inline functions in C is that macros can be type-generic 06:01:03 the same macro can work on float or int, or it can work on every struct with a field of some particular name 06:01:10 kmc: Yes they can; there are other things you can do with macros too, though; not only those things! 06:01:18 again reducing code duplication, and making things clearer if used tastefully 06:01:26 But those are some of the things done, and I have done things like that too. 06:01:34 Some things better with functions, though. 06:01:39 yep 06:01:44 you have to consider each circumstance 06:01:56 which is why blanket rules like "goto is bad!" or "multi-statement macros are bad!" are bad 06:02:15 i do think that all else being equal, a multi-statement macro should get more scrutiny 06:02:20 in terms of "am i being too clever" 06:02:26 I agree; goto is not bad, and macros is not bad, etc 06:02:30 @yarr 06:02:30 Arrr! 06:02:33 @quote scrutiny 06:02:34 ksf says: There's always going to be cases where good programs are rejected. But those who abandon close scrutiny for the sake of ease have earned neither ease nor maintainable programs. 06:02:34 one thing that was kind of hard for me to accept is that sometimes, the best way really is just to duplicate some code 06:04:34 Wait 06:04:45 We are discussing the harmfulness of common C idioms 06:04:48 Sometimes that may be the case. 06:04:49 in #esoteric? 06:05:05 But sometimes macro is better at least my opinion. 06:05:08 Linux programmers seem to have gone a bit overboard with this idiom 06:05:16 do { current->hardirq_context++; } while (0) 06:05:23 there's no need for it here, right? 06:05:33 In that case it would certainly seem you don't need it. 06:05:50 maybe it catches some cases of misuse better 06:05:56 prevents you from using that expression as an expression 06:06:08 Yes that is one possibility. 06:06:21 Actually, every macro that expands to a statement is placed in do { _ } while(0) 06:06:31 There is some reason for it 06:06:39 kmc: couldn't you do that with ((void)(current->hardirq_context++)), or am I mistaken? 06:06:48 possibly 06:06:57 soundnfury: here is a pretty good one: 06:07:02 (Of course, you could still use it in an expression, but not any expr you'd be likely to write) 06:07:11 #define might_sleep() do { __might_sleep(__FILE__, __LINE__, 0); might_resched(); } while (0) 06:07:17 kmc: Consistency can be a reasonable goal in itself. 06:07:30 shachaf: yeah 06:07:39 As long as you have to resort to code duplication, it's probably better to have the same pattern everywhere. 06:07:43 People are pretty good at patterns. 06:07:48 yeah 06:08:05 it makes it more likely they will DTRT when they add a second statement to your macro 06:08:07 I think they should allow return from a void function to have an expression of a void function call optionally in order to specify tail call hint for the compiler. 06:08:40 heh, cute 06:09:04 (But, they don't allow that.) 06:09:54 C ought to have void values. 06:09:58 I'm pretty sure gcc ignores almost all voodoo constructs that programmers throw in to hint at optimizations 06:10:02 Well, they would be much more useful in C++ than in C. 06:10:19 Then they should allow in C++ as well. 06:10:49 Justification: template res_t foo(...) { struct { res_t res; run() { res = ...; } s; ...; return s.res; } 06:11:10 You can probably specialize a template on void. 06:11:15 Yes. 06:11:20 But then you have to write the code twice. 06:11:43 i wonder if gcc has rules specifically to detect silly tricks people do and turn them into code that's actually good on modern machines 06:11:52 zzo38: GCC does allow that, and I've used that idiom in one case. 06:12:05 You need to specialize templates anyway, because your template probably won't all work the same way for rvalue-refs, lvalues, lvalue-refs, lvalue-const-refs, pointers, or the new atomic types 06:12:07 Not to specify an optimization hint, just to make things clearer. 06:12:29 shachaf: They do? Do other compilers supporting GNU89 (such as Clang) supports that? 06:12:52 kmc: it probably happens as special cases of some optimizer passes 06:13:33 zzo38: Yes, it works in Clang too. 06:13:51 Are there any other compilers supporting GNU extensions? 06:14:05 icc supports some 06:14:26 i think some GNU extensions are very widely supported 06:14:30 for example // comments in c89 mode 06:14:48 icc uses edison's parser 06:15:06 Calling that a GNU extension is a bit strange. 06:15:09 Presumably edg implements common extensions 06:15:16 it's... a extension supported by gnu 06:15:31 Jafet: most of them can't be removed at the parsing stage, though 06:15:41 kmc: gcc doesn't support // comments in c89 mode, actually. 06:15:45 It supports them in gnu89 mode. 06:15:48 Well, the entire front-end 06:16:03 I always use GNU89 mode except compiling a program requiring a different mode. 06:16:15 Intel mainly implements the back-end 06:16:22 zzo38: Isn't that true of every mode? 06:16:54 shachaf: I am not sure exactly you mean. 06:17:35 I suppose it's not really. 06:17:46 shachaf: ah, right 06:18:04 but strangely (i discovered today) it allows mixed declarations and code with -std=c89 06:18:11 that is, declarations after statements 06:18:16 only with -pedantic does it complain 06:18:48 -std=c89 without -pedantic isn't real -std=c89 06:18:53 :3 06:19:01 gotta sleep, ttyl all 06:19:12 nn then 06:19:45 The gcc developers officially take the standards as guidelines 06:20:20 I,I non-standard static analysis 06:20:24 So they try to implement the standards for you, but It's A Crapshoot 06:20:37 And the default is always -gnuXX 06:49:38 -!- zzo38 has quit (Remote host closed the connection). 07:49:17 -!- epicmonkey_ has joined. 08:11:19 -!- AnotherTest has joined. 08:11:45 hello 08:30:15 -!- Vorpal has joined. 08:35:46 -!- Vorpal has quit (Ping timeout: 250 seconds). 08:35:54 -!- Vorpal_ has joined. 09:07:03 -!- kinoSi has quit (Read error: Connection reset by peer). 09:07:30 -!- kinoSi has joined. 09:17:31 -!- augur has quit (Remote host closed the connection). 09:21:34 -!- augur has joined. 10:00:35 -!- nooga has joined. 10:51:42 -!- Dovregubben has quit (Ping timeout: 264 seconds). 10:56:35 -!- Dovregubben has joined. 11:04:23 -!- Dovregubben has quit (Ping timeout: 268 seconds). 11:04:44 -!- Dovregubben has joined. 11:44:41 -!- augur has quit (Read error: Connection reset by peer). 12:32:22 -!- nooga has quit (Ping timeout: 252 seconds). 12:52:25 -!- MoALTz has joined. 12:57:21 -!- MoALTz has quit (Quit: brb). 12:58:09 -!- ogrom has quit (Quit: Left). 13:07:05 -!- kinoSi has quit (Read error: Connection reset by peer). 13:07:32 -!- kinoSi has joined. 13:07:38 -!- MoALTz has joined. 13:18:49 -!- augur has joined. 13:51:27 -!- MoALTz has quit (Ping timeout: 252 seconds). 14:08:34 -!- mig22 has quit (Quit: mig22). 14:11:37 -!- MoALTz has joined. 14:14:05 > 8 * 19800 + 33000 14:14:06 191400 15:00:01 -!- epicmonkey_ has quit (Ping timeout: 245 seconds). 15:05:56 -!- epicmonkey has joined. 15:15:09 -!- epicmonkey_ has joined. 15:15:14 -!- epicmonkey has quit (Read error: No route to host). 15:38:33 -!- Phantom_Hoover has quit (Read error: Connection reset by peer). 15:40:09 -!- Phantom_Hoover has joined. 15:52:18 -!- zzo38 has joined. 16:13:49 -!- copumpkin has quit (Quit: Computer has gone to sleep.). 16:21:49 -!- MoALTz_ has joined. 16:24:36 -!- MoALTz has quit (Ping timeout: 245 seconds). 16:25:13 -!- atriq has joined. 16:26:35 -!- nooga has joined. 16:27:38 @messages? 16:27:38 Sorry, no messages today. 16:28:31 -!- oerjan has joined. 16:30:49 -!- epicmonkey_ has quit (Remote host closed the connection). 16:31:22 -!- itidus21 has joined. 16:39:32 A brace style could be baroque and obtuse... 16:39:33 -!- copumpkin has joined. 16:40:44 do {{ /*********************** GLORIA ***********************/ {{ 16:40:51 -!- MoALTz_ has quit (Quit: brb). 16:40:54 zzo38: something tells me that your nes sound files are very difficult to play. 16:41:11 -!- MoALTz has joined. 16:41:19 i have several nes emulators, and i see the online file directory where the nes music is contained 16:41:30 }} /****************** IN EXCELSIS DEO *******************/ }} 16:41:41 however... the operation of appending one file onto another is beyond my ken 16:41:46 while (0); 16:41:52 itidus21: You need not append one file onto another to play them. 16:42:03 Appending one file onto another is only if you want to play ZZT files. 16:42:16 ^bonus points for using the word ken 16:42:16 in a Famicom emulator. 16:42:25 ahh 16:42:32 HEY YOUR BLATHER IS RUINING MY BAROQUE BRACE STYLE 16:42:58 itidus21: To play the .NSFs you need not append any files. 16:42:59 can you fix it? 16:43:07 lets let oerjan do his work 16:43:23 well i'm finished but it got a bit broken up 16:43:27 do {{ /*********************** GLORIA ***********************/ {{ 16:43:29 }} /****************** IN EXCELSIS DEO *******************/ }} 16:43:31 while (0); 16:44:19 itidus21: I clarified the text and will upload a new version later today. 16:44:29 For now, just load the .NSF files without appending anything. 16:44:51 when i said fix it i meant can oerjan fix his baroque brace style :D 16:44:58 i did 16:45:22 yup 16:45:25 success 16:45:27 the text doesn't seem to be properly centered in the /***/ blocks 16:45:47 Yes I know that; but that is not what I meant. 16:45:58 I meant that you can load the .NSF without appending one file onto another. 16:46:10 olsner: sadly GLORIA and EXCELSIS DEO don't have the same parity, so i cannot do that 16:46:26 *IN EXCELSIS DEO 16:46:28 hmm, choose a different proverb? 16:46:33