00:09:11 -!- RedDak has quit (Read error: 104 (Connection reset by peer)). 00:41:16 -!- timotiis has quit (Read error: 110 (Connection timed out)). 01:17:26 -!- cc_to_ide has joined. 01:29:33 -!- GreaseMonkey has joined. 01:36:03 -!- cc_toide has quit (Connection timed out). 01:45:36 -!- Corun has joined. 01:45:51 -!- tusho has quit. 02:35:54 -!- Corun has quit ("This computer has gone to sleep"). 02:42:37 -!- cc_to_ide has changed nick to cctoide. 02:56:02 -!- cctoide has quit ("Leaving"). 04:37:26 -!- Sgeo has joined. 05:06:18 -!- pikhq has quit ("leaving"). 05:27:18 -!- RodgerTheGreat has joined. 05:27:24 'sup, folks? 05:53:25 'lo 05:54:25 what are you up to this evening, GreaseMonkey? 05:54:55 coding a new bot 05:55:04 piemonkey is pretty hackish 05:56:15 neat 05:56:49 I've been working on stuff for a comic book I plan to make 06:31:51 -!- cherez has quit (Read error: 110 (Connection timed out)). 06:32:29 -!- cherez has joined. 07:59:59 -!- clog has quit (ended). 08:00:00 -!- clog has joined. 08:01:20 G'night all 08:04:14 -!- jix has joined. 08:19:05 -!- Sgeo has quit (Read error: 110 (Connection timed out)). 09:49:55 -!- Hiato has joined. 10:04:58 -!- Hiato has quit ("Leaving."). 10:56:14 -!- GreaseMonkey has quit ("Remote closed the previous member app"). 11:35:34 -!- Judofyr has joined. 12:03:15 -!- Slereah_ has joined. 12:03:15 -!- Slereah- has quit (Read error: 54 (Connection reset by peer)). 12:05:01 -!- Slereah- has joined. 12:05:01 -!- Slereah_ has quit (Read error: 54 (Connection reset by peer)). 12:25:50 People, never go three years without sorting your files 12:25:54 You'll regret it 12:30:40 -!- timotiis has joined. 12:46:10 -!- sebbu2 has joined. 12:48:16 -!- sebbu3 has joined. 12:48:46 -!- sebbu has quit (Nick collision from services.). 12:48:48 -!- sebbu2 has quit (Nick collision from services.). 12:48:54 -!- sebbu3 has changed nick to sebbu. 13:20:36 hm 13:20:49 no one seen ais? 13:20:53 or tusho? 13:21:05 (the place is boring without them) 13:21:14 ;) 13:22:21 Deewiant, there? 13:22:22 -!- planofish has joined. 13:22:30 -!- planofish has left (?). 13:22:35 does a D program made for phobos compile and work with tango? 13:29:15 -!- Slereah- has quit (Read error: 54 (Connection reset by peer)). 13:30:29 AnMaster: you'll need tangobos and might need to make some small changes 13:30:38 ah 13:31:06 well that genx that tusho recommended, LOTS of compiler warnings 13:31:20 mostly casting const char* to non-const ones 13:31:37 so compile that file without warnings. :-P 13:31:51 Deewiant, no, rather fix them 13:32:51 I generally don't bother if it's somebody else's code and known to work 13:33:00 but yes, that works too. :-P 13:36:00 Deewiant, I have high quality standards for code I use in my own projects, way higher than if I just depend on it already being installed (and currently I only depend on libc, and optionally boehm-gc) 13:50:07 -!- pikhq has joined. 13:54:11 Deewiant, down to 2 warnings now 13:54:16 these two will be hard to fix 14:37:52 Deewiant, also it uses sprintf in some places instead of snprintf 14:37:56 UGH 14:41:51 nothing wrong with that if you have a buffer of the max possible size 14:42:00 e.g. %d and 11 14:53:11 Deewiant, indeed, but that wasn't the case here 14:53:13 it was strings 14:53:23 static constUtf8 storePrefix(genxWriter w, constUtf8 prefix, Boolean force) 14:53:30 sprintf((char *) buf, "xmlns:%s", prefix); 14:53:40 and if they're internal, they might now the size 14:53:55 Deewiant, I traced the code backwards, it is not checked before it is sent to said function 15:03:13 -!- ais523 has joined. 15:03:41 AnMaster: there? 15:04:25 ais523, yes? 15:04:32 AnMaster: I finished fffungi 15:04:36 wow! 15:04:44 but there are some things I'd like to discuss with you about it 15:04:50 yes, go ahead 15:04:59 the main issue is distributing it 15:05:07 at the moment I have patches + a script that applies them 15:05:12 hm 15:05:27 but the patches being GPLv3 makes it kind of tricky to distribute with C-INTERCAL 15:05:41 ais523, isn't C-INTERCAL "gpl2 or later"? 15:05:44 yes 15:05:49 the distribution's fine 15:06:01 it's just having two files that aren't normally used with a different licence is a pain to explain on the 'packaging' 15:06:24 ais523, well cfunge already contains some BSD code in lib, and shortly also some MIT 15:06:29 ofc I could just licence the patches under gpl2+ as it would come to the same thing when combined with your gpl3 code, but I'd need your permission to do that 15:06:34 included and customized libraries basically 15:06:45 oh, I found a bug in cfunge's string load 15:06:51 oh? 15:06:54 Deewiant: also a bug in mycology 15:06:56 details so I can fix it 15:07:03 AnMaster: off-by-one in the loop counter 15:07:14 you basically put the trailing NUL of the string onto the end of the program 15:07:23 ais523: \o 15:07:23 so if you try to wrap round the bottom row, it hits the NUL and reflects 15:07:33 ah 15:07:40 Deewiant: if negative k reflects, then it prints 'reflects' but also another message 15:07:42 ais523, got a patch for that? ;) 15:07:46 AnMaster: yep 15:07:53 also another patch which it would be helpful for you to apply 15:08:03 which doesn't affect cfunge at all when not combined with C-INTERCAL 15:08:08 ais523, oh btw your patch is your custom interpreter main loop file + your fingerprint right? in that case, go ahead with GPL2+ 15:08:12 Deewiant: I think you have a missing semicolon 15:08:17 AnMaster: yes, that's all 15:08:25 ais523, care to upload the patches somewhere? 15:08:26 I've pushed fffungi to the C-INTERCAL repo 15:08:29 so I can review and such 15:08:32 so you can get it from there 15:08:56 * AnMaster darcs pull 15:09:21 ais523, where in c-intercal repo? 15:09:34 the patch is etc/cfunge.patch 15:09:47 for the whole thing, the script's etc/cftoec.sh 15:09:53 which compiles cfunge into a library 15:10:03 ais523: hmm, doesn't look like that to me... what does it print? 15:10:16 Deewiant: maybe I have an older version 15:10:18 let me run it again 15:10:42 UNDEF: k with a negative argument executes more often than the absolute value of the argumenteflects 15:10:48 ais523, the other patch hm I see yes 15:10:59 lets me use a command-line define to change the handprint 15:11:08 um 15:11:14 that sounds like an old mycology? 15:11:17 ais523: looks like what it actually does is it executes more often and then prints something extra 15:11:37 Deewiant: nah, it reflects, but after pushing the string "reflects" to the stack it ends up in a different string by mistake 15:11:45 hmm 15:11:47 there's a semicolon meant to skip that bit, but it doesn't match another semicolon 15:11:49 6443244db122653f5479bd1751988175 *mycology.b98 15:12:03 Deewiant, didn't you fix that bug some ages ago iirc? 15:12:07 there should be a semicolon in column 110 which it skips to 15:12:15 (from column 47) 15:12:30 and yes, this is from the latest version of mycology which dates back to may 15:12:44 -!- Corun has joined. 15:13:24 I only have a changelog up to march and I don't see me messing with that, but it could be it was earlier 15:13:24 ah yes, I think I just have an old version 15:13:36 2007-12-02 16:35 mycology.b98 15:13:46 yes, that's old :-) 15:13:46 I'm going to have to get a newer version, I think 15:15:18 ais523, they are commited locally (with minor changes to add a comment explaining why I did that in global.h) but not pushed as the local code is broken (changing TURT to use the a library for xml generation, library is added under lib/genx/*.c) 15:15:34 ah, ok 15:15:45 I'll remove the bit of my code that patches cfunge once the newer version is pushed 15:15:58 oh, and the fingerprint still says example.com as the URL 15:16:08 I'll fix that once I have a website up describing it 15:16:30 there's a page in the C-INTERCAL manual describing IFFI now, so I just need to put the manual online and I can link to that 15:16:37 incidentally, have you tried the test program? 15:16:51 pit/tests/iffit1.i with pit/tests/iffit2.b98 15:17:57 ais523, haven't tried it yet as my local cfunge source doesn't compile atm 15:18:06 ok 15:18:10 try it with an older revision 15:18:19 too lazy, it will be fixed soon 15:28:15 -!- timotiis has quit (Read error: 110 (Connection timed out)). 15:45:20 -!- Hiato has joined. 15:49:28 -!- jix has quit (Nick collision from services.). 15:49:38 -!- jix has joined. 16:07:06 ais523, there? 16:07:10 yes 16:07:11 would this be valid C: 16:07:12 genxStartElement(g_path) || return false; 16:07:14 just wondering 16:07:21 no, return isn't a function 16:07:27 ah right 16:07:28 you can do || exit(EXIT_FAILURE) though 16:07:29 true 16:07:36 ais523, no I don't want that 16:07:39 except that exit returns void 16:07:56 so I suggest you use an if 16:08:53 -!- tusho has joined. 16:09:24 hi ais523 16:09:27 hi tusho 16:09:30 you win 16:09:54 yep 16:10:23 ais523: when did it arrive at your end? 16:10:26 16:09 16:10:35 before I focused Konversation 16:10:51 anyway, I finished my C-INTERCAL/cfunge FFI 16:11:00 ais523: i meant to the second, really 16:11:00 :P 16:11:04 and cool 16:14:32 tusho, btw you said genx handled CDATA? it doesn't 16:14:37 also the code is way ugglier now 16:14:41 huh, I was pretty sure it did. 16:14:47 I will mention this is thanks to you in a comment 16:14:49 well, it may be uglier but it's more correct 16:14:54 a lot of static buffers 16:15:01 as I need to do stuff like: 16:15:09 snprintf(sminx, sizeof(sminx), FIXEDFMT, PRINTFIXED(minx)); 16:15:09 snprintf(sminy, sizeof(sminy), FIXEDFMT, PRINTFIXED(miny)); 16:15:15 genxAddAttributeLiteral(gw, gns, (constUtf8)"x", (constUtf8)sminx); 16:15:15 genxAddAttributeLiteral(gw, gns, (constUtf8)"y", (constUtf8)sminy); 16:15:19 and so on and so on 16:15:23 AnMaster: send patches to tim bray making it better. 16:15:26 i'm sure he'd love them 16:15:53 tusho, also it contained sprintf() for untrusted data instead of snprintf() (fixed that) and lots and lots of compiler warnings 16:16:09 fixed all but two compiler warings 16:16:11 warnings* 16:16:18 it was developed circa 2004 16:16:22 so gcc is probably more pedantic now 16:16:24 again thanks to you cfunge will no longer compile with -Werror 16:16:29 unless you plan to send me a patch 16:16:39 AnMaster: fix the other two maybe...? 16:16:55 tusho, they are quite complex cases of casting a const char * to a char * 16:17:03 that will need major redesign to work 16:17:42 this is why you don't use const :) 16:17:47 tusho, ... 16:17:51 the code already does 16:17:58 also a string literal is a const char * 16:18:46 tusho, also creating a path is much harder as the path goes inside an attribute 16:18:57 so I need to malloc() a buffer for them and grow it as needed 16:19:06 AnMaster: ok, are you going to complain at me for like five hours about it? 16:19:16 as I can't just append like I could with fprintf() before 16:19:30 tusho, why would I? 16:19:47 tusho, I think you overcomplicate stuff though 16:19:51 AnMaster: you've managed 5 minutes already 16:19:51 :) 16:20:02 [... and me overcomplicating stuff? Coming from you?] 16:20:24 I would prefer S-Expressions 16:20:29 way more elegant than XML 16:21:18 AnMaster: Produce s-expressions and use the scheme SXML library to turn them into XML. 16:21:26 I think it runs on Guile so you should be able to embed it. 16:21:31 haha 16:21:43 that would be even more overcomplicated and bloated 16:22:24 anyway, anyone who likes looking at Befunge-98 code with COME FROMs in: http://eso-std.org/darcs/c-intercal/pit/tests/iffit2.b98 16:22:35 that interfaces with http://eso-std.org/darcs/c-intercal/pit/tests/iffit1.i 16:22:50 just a test program, all they do is print out numbers in sequence as they do various tests 16:23:29 oh, I went a bit overboard in the Befunge program 16:23:56 it's pretty dense, with code interleaving around other code, and also self-modifying 16:24:05 not only that, but it alters the syntax of the INTERCAL program 16:24:08 because I wanted to test that 16:25:14 -!- Corun has quit ("This computer has gone to sleep"). 16:25:15 that befunge code is write only heh 16:25:27 AnMaster: you can read individual bits 16:25:31 by tracing them in your head 16:25:40 start at the start, and also in each possible direction from each middot 16:26:06 I find Befunge isn't usually as hard to read as it looks 16:26:12 -!- Hiato has quit ("Leaving."). 16:26:17 compared to something like Unlambda, for instance, which is usually as hard to read as it looks 16:27:04 -!- Corun has joined. 16:28:37 blregh I got to write a generic string builder with append or this will be painful 16:28:45 actually that could be useful in other parts too 16:29:00 oh wait I think I can take that from crossfire maybe, it got a stringconstructor iirc 16:33:59 Deewiant: "BAD: O opened 'mycotemp.tmp' for reading, won't overwrite it and thus won't test fingerprint" <-- what does that mean? 16:34:13 ais523: it means just what it says 16:34:19 ais523, that you should do rm mycotemp.tmp 16:34:22 and then try again 16:34:22 it managed to open 'mycotemp.tmp' so it won't overwrite it 16:34:28 ah 16:34:32 just in case you actually put something important in a file called mycotemp.tmp :-P 16:35:02 well, in that case ick passes mycology 16:35:18 although it's cfunge doing all the work behind the scenes, of course 16:35:21 so not that surprising 16:36:26 maybe I should write a test for IFFI... 16:36:36 that works Mycology-style 16:36:45 rather than just writing numbers 16:36:51 although I suppose Mycology writes numbers to start with 16:37:36 it has to since it only assumes that the few instructions in sanity.bf work :-) 16:37:45 yes, I know 16:37:52 in my case I wrote out numbers to save program size 16:38:01 of course I could easily have assumed that , works and not . 16:38:05 and also because reading out strings is a pain in INTERCAL 16:38:16 heh 16:38:21 Deewiant: not that easily, you'd be limited to control codes until you got arithmetic working 16:38:38 ah, true 16:38:47 that explains why I chose it like that ;-) 16:38:59 incidentally, for testing = 16:39:05 I think the echo command does the same thing on all platforms 16:39:18 as it just happens to have the same meaning in DOS, in Windows and in UNIX 16:39:32 that would work for C-system-style = 16:39:49 ais523: it's not exactly the same, as you might imagine 16:39:54 no, it isn't 16:40:05 but when given one argument consisting of nothing but letters it is 16:40:11 if that argument isn't "on" or "off" 16:40:15 :) 16:40:49 just pedantic enough now, I approve 16:41:07 ais523: echo doesn't exist in Windows or DOS except as a builtin of the shell 16:41:22 Deewiant: yep, but C system() always invokes the shell in DOS/Windows 16:41:25 ah, but = was C system() 16:41:51 except under DJGPP it optimises it if it notices that the shell isn't needed, but invokes the shell if it is 16:42:01 so it always works as if the shell was invoked 16:42:15 how can it know that at compile-time? O_o 16:42:41 Deewiant: it doesn't, there's a check in their version of libc 16:42:50 ah 16:42:56 but hmm 16:43:01 how can it know it even then 16:43:14 the shell in DOS is pretty dumb 16:43:29 yes compared to a UNIX shell 16:43:35 but it's still usable, just about 16:43:37 I mean there's the short list of builtins 16:43:45 but no globbing 16:43:55 not much interesting chaining of commands 16:43:56 Deewiant: checks to see if it refers to an executable on the PATH that isn't a shell builtin 16:44:02 does the shell handle piping ? 16:44:08 Dewi: not exactly 16:44:09 it does 16:44:13 yeah, I just realized that being DOS-only means that you only have to worry about one shell :-) 16:44:14 but DOS is single-threaded 16:44:25 so it pipes through tempfiles 16:44:31 ais523: ew 16:44:38 ais523: that sounds familiar 16:44:42 ais523: I wonder if I suppressed that memory 16:44:53 ais523: winnt cmd.exe doesn't do that does it? 16:45:04 Dewi: not sure, cmd.exe is somewhat improved 16:45:10 I don't have a copy here to try it on 16:45:17 I'd have to switch to a Windows computer to test 16:45:18 it doesn't 16:45:40 a few years ago when I was in the transitional phase from thinking in windows to thinking in unix... I used to write a lot of batch files that invoked inline perl 16:45:50 i.e. yes | head terminates 16:45:59 ah, that's good 16:46:02 and I was surprised how hard I could push windows piping 16:46:11 Dewi: i hate you for not being Deewiant 16:46:12 :( 16:46:14 people act like cmd.exe almost doesn't have it, but it's actually rather good 16:46:30 tusho: me too 16:46:38 Dewi: start being Deewiant 16:46:47 A quote I remember, not sure where from: "Microsoft shoved a lot of standard UNIX shell functionality into cmd.exe while no-one was looking" 16:46:51 tusho: but I also reserve some hatred for Deewiant choosing such a name 16:47:01 but cmd.exe still has insane variables 16:47:20 yeah the rest of it's hideous 16:47:40 the quoting rules of process execution on windows are brilliant 16:47:44 but it's surprising how similar a batch file can be to a simple shell script if you have enough textutils installed 16:47:50 let me dig them up for your viewing pleasure 16:48:02 Deewiant: nobody ever, EVER quotes correctly in windows batch files 16:48:08 Deewiant: I've run into them before 16:48:16 Deewiant: people think it's bad in unix, but... urgh 16:48:26 hm 16:48:28 and I have managed to quote correctly before, but only in situations where all the things I was quoting were string literals 16:48:31 even then it can be tricky 16:48:56 I always manage to invoke the crazy thing to do filenames correctly 16:49:03 the fish shell never requires quoting 16:49:04 hmm, can't find them 16:49:05 I kinda like that 16:49:09 argh too much to read 16:49:09 it seems like a sane shell 16:49:10 but the other day I found even that got me into trouble because doing so expands the full path, and I needed a relative form 16:49:12 anything important? 16:49:14 Dewi: well, cmd.exe tab-completes the quoting correctly 16:49:14 I thought I remembered a place where they're linked but it wasn't there after all 16:49:17 ais523, ^ 16:49:21 that's a useful trick to know 16:49:29 ais523: I meant for variables 16:49:32 AnMaster: not really, we were just discussing Windows shells 16:49:37 oh ok 16:49:41 bbl food 16:49:42 Dewi: yep, that's harder 16:49:44 ais523: the big problem is this, the shell doesn't remove quotes on batch file invocations 16:50:13 Dewi: not even if you use call? 16:50:18 ais523: so if your batch file needs to pass the param on again, it's going to either add another layer of quotes if the original user included them, or fail to add them and possibly break stuff 16:50:28 ugh 16:50:32 ah, here we are 16:50:33 http://msdn.microsoft.com/en-us/library/system.environment.getcommandlineargs.aspx 16:50:38 recursive batch files were always a bad idea under DOS 16:50:46 If a double quotation mark follows two or an even number of backslashes, each proceeding backslash pair is replaced with one backslash and the double quotation mark is removed. If a double quotation mark follows an odd number of backslashes, including just one, each preceding pair is replaced with one backslash and the remaining backslash is removed; however, in this case the double quotation mark is not removed. 16:50:57 especially as they acted like UNIX exec when called by default, and you needed a special prefix to be able to return from them 16:51:29 ais523: so to feel a little bit safe you can go "%~1" 16:51:30 same under windows 16:51:34 the prefix is "call" 16:51:37 Deewiant: that page doesn't open correctly in Konqueror at all, there are no scrollbars so I can't read more than the first few sentences 16:51:40 Deewiant: yes, I know 16:51:54 ais523: not surprising... I pasted the relevant bit 16:52:01 ais523: aah see that's the correct thing, "%~1" but I sometimes forget, the other day I was using something like "%~dpnx1" which is fine but it does expand to a full absolute canonical path, which can be bad 16:52:04 -!- Sgeo has joined. 16:52:21 HALO AIS523 16:52:24 Deewiant: that definition's the way C strings are quoted 16:52:33 ais523: but these are invocations you never see in batch files you encounter, those are just pretty much always wrong 16:52:53 Deewiant: ooh, that's eeevil 16:53:08 ais523: hm, is it? darn 16:53:31 Deewiant: except that it strips unquoted double-quotes rather than using them as string delimiters 16:54:19 Dewi: well, utilities like find on UNIX/Linux have similar quoting problems when used on files that contain literal newlines in their names 16:54:37 ais523: any kind of space, I thought 16:54:51 Dewi: it's possible to quote spaces more easily than newlines 16:54:56 although they can also be problems 16:55:20 ais523: that's something I find really odd about 'find'. By default, filenames with spaces break it. You can use \0, and usually I do, but newlines feel "good enough" in a lot of cases 16:55:29 ais523: but only the most recent gnu finds allow you to use newline as delimeter 16:55:51 to the point where I usually end up doing - perl -pe 's/\n/\0/;' | xargs -0 16:56:03 Dewi: well, I use newline-delimited find when compiling cfunge, because I know that AnMaster's unlikely to put newlines or spaces in filenames there 16:56:23 ais523: in my view, spaces in filenames is pretty common. Newlines is... really odd 16:56:25 AnMaster: also, let me know if you plan to give two files the same filename in different directories, my current code will break if you do that 16:56:39 Dewi: spaces in filenames is common on Windows but not on Unices 16:57:02 here we are 16:57:03 http://msdn.microsoft.com/en-us/library/bb776391.aspx 16:57:13 2n backslashes followed by a quotation mark produce n backslashes followed by a quotation mark. 16:57:14 whereas newlines in filenames is impossible on Windows before the most recent versions (and impossible through the normal interfaces) and very rare on Unices 16:57:16 (2n) + 1 backslashes followed by a quotation mark again produce n backslashes followed by a quotation mark. 16:57:20 n backslashes not followed by a quotation mark simply produce n backslashes. 16:57:34 Deewiant: ugh, that is pretty different from C quoting 16:57:40 ais523: yeah. So I'd be pretty comfortable using newlines 16:57:52 ais523: yeah, and that's what I was looking for. :-) 16:57:56 ais523: but xargs on lots of machines won't let me. -0 works everywhere though 16:58:25 * for provincial values of everywhere 16:58:29 Dewi: well, keeping in with the normal INTERCAL method of finding an unusual way to do things, I used find -printf to print out shell commands and piped find's output to sh 16:58:45 unfortunately that is a bit insane 16:58:54 ais523: actually... I invoke find like this really very often 16:59:04 normally I try to find a way that's sane but nobody uses it for some reason 16:59:21 find -print0 | xargs -0r -n1 bash -c 'mv -i "$0" "$0.bak"' 16:59:27 such as C-INTERCAL running just fine after a configure and make but no install, you simply have to give the path to the executable explicitly 16:59:30 ^ rename filename to filename.bak. 16:59:51 totally safe. *bash* making things *safe*. Hard to imagine isn't it 17:00:02 Dewi: find -printf 'mv %f %f.bak' | sh 17:00:14 and that method breaks if the filenames contain literal double-quotes, surely? 17:00:20 that is, your method 17:00:20 ais523: less safe, spaces, newlines, etc 17:00:24 otoh my method breaks a lot more 17:00:24 ais523: nope 17:00:29 it wasn't meant to be safe 17:00:30 just insane 17:01:19 ais523: because bash gets exactly 3 parameters with that invocation, and $0 is the one that came after the command 17:01:32 and since I have double-quoted the $0, that's watertight, or should be 17:01:46 oh, of course 17:02:22 the key is avoiding talking directly about the param until the last moment. Xargs passes it through onto the end of the list without any of that troublesome parsing 17:02:51 it's funnny the awkward recipies I end up using on a daily basis because they seem safe 17:02:58 (safe like the defaults should have been, damn it!) 17:03:21 it's dangerously close to cargo cult programming 17:06:20 -!- Slereah- has joined. 17:06:30 AnMaster: also, let me know if you plan to give two files the same filename in different directories, my current code will break if you do that <-- hm possible that will happen, indeed 17:06:41 AnMaster: what would you use it for? 17:06:45 ais523: that method shouldn't be underestimated though, just because it makes it easy to review the craziness before it runs 17:06:51 ais523: that can prevent a lot of grief 17:06:51 ais523, when I replace the funge space with a faster version I'm likely to offer both as alternatives at compile time for a while 17:06:52 :) 17:06:54 like I did last time 17:07:11 AnMaster: ah, but it wouldn't be right to compile both in at once? 17:07:17 ais523, indeed not both at once 17:07:20 at the moment I just compile and link together all the .c files in /lib and /src 17:07:22 both at once would be an error 17:07:29 so it's right for it to break when that happens 17:07:35 right 17:07:39 and I'll need to not compile one or the other depending on circumstances 17:07:44 that's fine, just let me know when it happens 17:07:48 sure 17:08:01 ais523, do you use lib/*/*.c or lib/blah/*.c atm? 17:08:11 because in the next commit two subdirs to lib will be added 17:08:24 AnMaster: recursive find atm 17:08:37 so effectively lib/*/*.c 17:08:41 but with any number of */ 17:09:16 lib/**/*.c in zsh 17:09:19 ais523, also in that commit cfunge will contain MIT code as well as current GPL3, LGPL and BSD (see COPYING, it contains several licenses, due to the libraries) 17:09:27 Deewiant, hah 17:09:37 hah? 17:09:45 "yet another zsh user" 17:09:46 AnMaster: that isn't an issue really 17:09:51 but zsh is quite bloated IMO 17:09:57 yes some nice features 17:10:02 I don't care all that much about the licences of things I link to as long as they're compatible 17:10:02 that I would like to see in bash 17:10:05 I suppose you use sh then 17:10:07 :-P 17:10:07