00:34:23 | * | Anaphaxeton quit (Read error: Connection reset by peer) |
02:07:10 | * | fowl joined #nimrod |
02:56:04 | * | q66 quit (Remote host closed the connection) |
08:22:27 | * | gour joined #nimrod |
08:34:43 | * | fowl quit (Ping timeout: 248 seconds) |
08:48:13 | * | fowl joined #nimrod |
08:51:26 | dom96 | reactormonk: I see you're hard at work with the JS backend. Nice job :) |
09:07:02 | * | gour quit (Disconnected by services) |
09:07:03 | * | gour_ joined #nimrod |
09:52:23 | * | fowl quit (Ping timeout: 260 seconds) |
10:38:50 | * | FreeArtMan joined #nimrod |
10:54:01 | * | Anaphaxeton joined #nimrod |
11:32:29 | * | filwit joined #nimrod |
11:33:03 | filwit | morning folks! |
11:33:49 | filwit | whenever you get guys are around, check out my Nimrod Web Design mock up, here: http://reign-studios.com/nimrod/web-design.png |
11:35:24 | * | q66 joined #nimrod |
11:36:20 | filwit | let me know what you think, or if you'd like to see something changed (not sure I have enough Gold in there for Araq), and I will try and see what I can do. |
11:36:26 | filwit | hi q66 |
11:37:17 | q66 | hi |
12:07:18 | * | Anaphaxeton quit (Read error: Connection reset by peer) |
12:09:25 | * | FreeArtMan quit (Quit: rm -rf /) |
12:21:59 | * | Anaphaxeton joined #nimrod |
12:24:18 | * | filwit quit (Quit: Leaving) |
13:44:11 | * | Anaphaxeton quit (Remote host closed the connection) |
13:51:56 | * | Anaphaxeton joined #nimrod |
14:07:57 | * | filwit joined #nimrod |
14:11:03 | * | Anaphaxeton quit (Quit: Αποχώρησε) |
14:26:04 | * | filwit quit (Quit: Leaving) |
14:32:03 | * | Anaphaxeton joined #nimrod |
14:38:59 | * | Anaphaxeton quit (Quit: Αποχώρησε) |
14:41:50 | * | meeeee joined #nimrod |
14:51:44 | * | zahary1 joined #nimrod |
15:08:40 | * | Anaphaxeton joined #nimrod |
15:18:21 | * | Anaphaxeton quit (Remote host closed the connection) |
15:20:54 | * | Anaphaxeton joined #nimrod |
15:22:29 | * | Anaphaxet0n joined #nimrod |
15:23:10 | * | Anaphaxeton quit (Read error: Connection reset by peer) |
15:53:18 | * | exhu joined #nimrod |
15:54:30 | exhu | filwit, the design is glamorous -) although i suppose it's traffic heavy. |
16:08:33 | * | Anaphaxet0n quit (Remote host closed the connection) |
16:22:10 | dom96 | filwit's design is absolutely beautiful. |
16:26:21 | * | exhu quit (Quit: Ex-Chat) |
16:27:36 | Araq | filwit's design could indeed use more gold ;-) |
16:28:07 | dom96 | I think it's perfect already. |
16:28:17 | dom96 | You and your gold... :P |
16:28:17 | Araq | ha, I knew you'd love it |
16:30:08 | dom96 | well at least you don't want a picture of some trees or a sunset in there :P |
16:30:25 | Araq | hmm |
16:30:35 | dom96 | NO |
16:31:17 | Araq | perhaps we need a crappy background full of 0s and 1s :P |
16:31:26 | Araq | because it's about "programming" |
16:31:42 | dom96 | bleh |
16:32:19 | dom96 | I think this design is perfectly fine, and we should be worshipping filwit for his great work ;) |
16:32:49 | Araq | I think we should do a voting on the forum |
16:33:27 | Araq | but if we switch to that design, I'd prefer to switch the design when 1.0 or a significant milestone is released |
16:34:10 | dom96 | i think if anything then on the release |
16:34:15 | dom96 | *next release |
16:34:25 | Araq | the fonts he used are excellent btw, I like them very much |
16:34:42 | Araq | I wonder if these are standard fonts |
16:36:03 | Araq | well we'd better include important features in the next release |
16:36:08 | Araq | *for |
16:36:25 | dom96 | yes :P |
16:45:49 | dom96 | so what's up Araq? |
16:53:59 | * | _ponce quit (Remote host closed the connection) |
16:54:04 | * | FreeArtMan joined #nimrod |
16:54:11 | * | _ponce joined #nimrod |
16:58:58 | gour_ | "User defined type classes" are not implemented ( yet)? |
16:59:07 | * | gour_ is now known as gour |
17:00:20 | Araq | dom96: not much, I'm still working on the generational GC |
17:00:41 | Araq | gour: afaik, yes |
17:02:48 | gour | they're planned for 1.0? |
17:03:08 | Araq | not sure ;-) |
17:03:16 | Araq | it's not on my todo |
17:03:58 | dom96 | what are these "type classes" exactly? |
17:04:07 | Araq | ask zahary |
17:06:30 | gour | although not familiar-enough with neither nimrod nor D, but I consider that the former has much more stuff in a very nice shrink-wrapped package |
17:06:33 | gour | ok |
17:06:35 | zahary1 | well, you can read about them in the manual |
17:06:55 | gour | zahary1: what's the plan with user-defined ones? |
17:09:00 | * | Anaphaxeton joined #nimrod |
17:12:13 | zahary1 | they will be similar to the protocols in clay - just a predicate that is either true or false for a given type. the most common type of predicate should just check that a piece of usage code compiles for the given type and there will be a simple syntax in type sections that optimises this case |
17:13:43 | gour | zahary1: should i investigate about clay language? |
17:13:45 | gour | :-) |
17:17:45 | zahary1 | https://github.com/jckarter/clay/wiki/Protocols |
17:18:54 | zahary1 | http://channel9.msdn.com/Events/GoingNative/GoingNative-2012/A-Concept-Design-for-C- the updated plans for concepts in C++ are somewhat similar too (even more than clay) |
17:27:35 | gour | thanks |
17:27:51 | * | Anaphaxeton quit (Quit: Αποχώρησε) |
17:28:12 | * | Anaphaxeton joined #nimrod |
17:28:42 | dom96 | aww, I can't create infix operators from words? |
17:28:53 | reactormonk | dom96, div isn't one? |
17:29:11 | Araq | yeah but 'div' is a keyword |
17:29:20 | dom96 | yeah, I mean non keyword operators. |
17:29:39 | Araq | make a proposal, I'd like to have them too |
17:29:51 | Araq | I don't think it can work with the current parser though |
17:30:57 | Araq | on the other hand x.infixOperator(y) is not too bad |
17:31:07 | dom96 | well say I declare: |
17:31:21 | dom96 | proc `bh`(foo, bar: int): int = ... |
17:31:27 | dom96 | 5 bh 12 |
17:31:34 | reactormonk | Araq, found the bug btw |
17:31:35 | dom96 | Parser cannot handle that I guess |
17:31:41 | Araq | reactormonk: which one? |
17:31:48 | Araq | dom96: indeed |
17:32:00 | Araq | it should not rely on the symbol table |
17:32:10 | Araq | so anything you have to declare doesn't work |
17:32:40 | dom96 | 5 ~bh 12? |
17:32:43 | Araq | you need to come up with things like: a |infix| b |
17:33:13 | Araq | or: 5 ~bh 12, yeah |
17:33:33 | * | zahary1 quit (Quit: Leaving.) |
17:33:46 | Araq | a `infix` b would be nice, but it's ambiguous |
17:35:28 | reactormonk | Araq, https://github.com/Araq/Nimrod/issues/329 https://github.com/Araq/Nimrod/issues/328 |
17:35:38 | dom96 | a (bh) b # definitely ambiguous right? |
17:36:13 | * | zahary1 joined #nimrod |
17:36:56 | dom96 | Thing is: having special symbols for this means that it's not consistent with the current infix keywords :\ |
17:37:55 | * | Anaphaxeton quit (Quit: Αποχώρησε) |
17:38:21 | * | Anaphaxeton joined #nimrod |
17:39:28 | * | Anaphaxeton quit (Remote host closed the connection) |
17:39:46 | * | Anaphaxeton joined #nimrod |
17:40:26 | Araq | reactormonk: yes for #328 |
17:40:40 | Araq | dunno about #329 |
17:40:49 | Araq | what caused unittests to fail for JS? |
17:41:19 | Araq | dom96: yeah but it was a conscious design decision |
17:41:25 | dom96 | Araq: out of curiosity, why did you decide to use keywords for things like bit shifting etc? |
17:42:06 | Araq | bit shifting was a close call, but << has the wrong precedence given Nimrod's precedence rules |
17:43:08 | Araq | and I wanted to keep them simple (they are a more complex now anyway) |
17:44:13 | Araq | dom96: I really don#t want to write x `or` y `and` z, so I made them keywords |
17:45:25 | dom96 | yes, well, I meant. Why keywords instead of |, ||, && etc. Just because of precedence rules? |
17:46:24 | Araq | || and && are uglier |
17:48:43 | Araq | in my mind they are like 'if', I don't use ?? for 'if' either |
17:50:00 | dom96 | that's an interesting way of looking at it. I completely agree with you of course. |
17:53:29 | * | meeeee quit (Quit: meeeee) |
18:51:18 | * | Anaphaxeton quit (Quit: Αποχώρησε) |
19:05:54 | reactormonk | Araq, I sneaked in two other commits - are they good to merge? |
19:06:23 | Araq | let me have a look |
19:09:30 | * | gour reached the end of the manual (1st slow reading).. |
19:09:39 | reactormonk | gour, yeah, it's short. |
19:10:58 | gour | Araq: once again, congrats for putting together very well-designed language...now i've better understanding why noSideEffect/func is not a big issue considering how many pragmas are on disposal for programmer |
19:12:09 | * | zahary2 joined #nimrod |
19:12:17 | * | zahary1 quit (Ping timeout: 252 seconds) |
19:12:43 | reactormonk | I'd prefer a sligtly less verbose syntax for pragmas, but fuck it. |
19:13:52 | Araq | actually I thought about using Unicode's « » as alternatives for {. .} |
19:14:05 | reactormonk | is that complicated? |
19:14:15 | dom96 | reactormonk: what's less verbose than the current syntax? |
19:14:25 | reactormonk | dom96, no idea. |
19:14:44 | Araq | reactormonk: no but it means « » is not available for operators anymore then |
19:14:53 | reactormonk | hm |
19:15:02 | Araq | well currently every unicode char is valid for identifiers only |
19:17:25 | Araq | you can use {. } instead of {. .} btw but I'm not sure it's a good idea |
19:21:09 | NimBot | Araq/Nimrod 2a7aaf8 Simon Hafner [+0 ±1 -0]: UTC weekday in JS |
19:21:09 | NimBot | Araq/Nimrod 4847427 Simon Hafner [+0 ±1 -0]: elif on JS instead of generic else |
19:21:09 | NimBot | Araq/Nimrod 5448432 Simon Hafner [+0 ±2 -0]: on the path to get unittest running from JS |
19:21:09 | NimBot | Araq/Nimrod a09bea1 Simon Hafner [+1 ±1 -0]: WA for #329, caused by #335 |
19:21:09 | NimBot | Araq/Nimrod eb724a4 Araq [+1 ±3 -0]: Merge pull request #336 from Tass/unittest... 3 more lines |
19:21:55 | Araq | reactormonk: what's the problem with #335? |
19:22:10 | reactormonk | Araq, come again? |
19:22:33 | Araq | note that I deliberately don't use the lambdalifting pass for the JS backend |
19:22:40 | Araq | as JS supports closures natively |
19:22:59 | reactormonk | Araq, well, test the code |
19:23:14 | Araq | I don't want to |
19:23:20 | Araq | that's why I ask :P |
19:23:51 | reactormonk | Araq, the problem is that the proc is generated as a function outside the inner function. |
19:24:02 | Araq | ah |
19:24:05 | Araq | fix it :P |
19:24:29 | reactormonk | http://sprunge.us/LADe |
19:27:32 | reactormonk | Araq, maybe |
19:41:30 | * | Anaphaxeton joined #nimrod |
19:47:10 | gour | is there some lib for calculus available in nimrod? |
19:51:05 | dom96 | Araq: hrm, what's the deal with the implicit 'result' variable and first class iterators? |
19:53:10 | dom96 | gour: Sadly I don't think there is. |
19:54:53 | gour | is there some plan to have some support of mac os x packages in niminst or this is covered by UNIX shell scripts? |
19:55:23 | dom96 | I think gradha was planning on implementing something. |
19:55:33 | dom96 | Might want to ask him when he's around. |
19:58:15 | gour | ok |
19:58:50 | gour | the next step for me would be to play with c2nim in order to provide bindings for 3rd party C lib we'd need for our project.. |
20:04:21 | gour | is niminst good-enough to provide complete build for nimrod-based projects? |
20:04:59 | dom96 | niminst is designed to create installers. |
20:05:17 | dom96 | If that's what you're after, then yes. |
20:06:09 | gour | isn't build.sh used to build nimrod itself created by niminst? |
20:06:33 | dom96 | Yes. |
20:06:55 | dom96 | You can also get a Inno setup installer for Windows using niminst. |
20:07:39 | gour | well, for windows & mac i'd like to provide installers, but linux would be native platform, so how to build nimrod project from the source? |
20:08:09 | gour | ...and e.g. make debian/ubuntu/rpm/etc. package from it later? |
20:09:18 | dom96 | actually niminst supports the creationg of .deb packages |
20:09:24 | dom96 | *creation |
20:09:37 | * | XAMPP-8 joined #nimrod |
20:09:49 | dom96 | from source you just do: nimrod c app.nim |
20:10:47 | dom96 | You can also just generate C sources (using niminst IIRC) and then give that to your users, they will then only need a C compiler to compile your app. |
20:11:04 | gour | i didn't know about ability to create .deb..cool...but what about when one has the whole source tree, with several nimrod-based libs to create/link etc.? |
20:12:33 | dom96 | You can use babel to install them, and then it's as simple as nimrod c app (if your app simply imports that library) |
20:12:34 | gour | i spent (too) much time looking/evaluating different build systems (cmake, scons, waf, premake, tup, bento...) to find something adequate, so having all he infrastructure ready from within nimrod, would be great |
20:13:01 | dom96 | if you want to dynamically link to a nimrod library which has already been compiled then that is a bit more complex. |
20:14:56 | * | zahary2 quit (Quit: Leaving.) |
20:15:02 | gour | i also have need to build nimrod bindings for the C lib, then have some 'target' for creating docs etc....none of the before-mentioned build systems do not have explicit support for nimrod, although probably adding it to waf/tup could not be difficult... |
20:15:27 | gour | however, in case of waf this involves new dep (python) :-/ |
20:17:26 | reactormonk | Araq, would you have an idea how to fix it? |
20:17:43 | dom96 | well if you need to build C libraries then you're forced to use whatever they use. |
20:19:42 | gour | dom96: C library is built using simple make, but the point is to integrate the whole build in one single build system...of course, i excluded autoconf considering we deserve something better today |
20:24:03 | dom96 | what C libraries do you want to use? |
20:24:14 | dom96 | Do you have some custom C libraries? |
20:24:41 | dom96 | Because if they are pretty popular then they will be compiled already and available for most platforms, so you will just need to distribute the DLLs |
20:27:02 | gour | dom96: it's kind of niche library - http://www.astro.com/swisseph/swephinfo_e.htm?lang=e i did not find it available in many distros, so i'd like to include its sources, built it, build nimrod bindings as well as the rest of the project using it |
20:27:35 | Araq | reactormonk: yeah but explaining it is not that easy |
20:27:42 | gour | other things which we'd need is sqlite3, but that's not the problem |
20:28:19 | reactormonk | Araq, what to read? |
20:30:46 | dom96 | gour: Just use some bash file that builds it all for you I guess, or write a Nimrod app which does it, or use tup. There are many choices. I don't do much C compiling so I'm not sure what the best approach is. |
20:31:30 | gour | dom96: i haven't looked, but how do you build aporia? |
20:31:41 | dom96 | gour: nimrod c aporia |
20:31:42 | dom96 | :P |
20:31:53 | gour | single file? |
20:32:33 | dom96 | nimrod compiles in all the modules which aporia.nim uses. |
20:32:45 | dom96 | so it's just a matter of compiling the main file. |
20:32:51 | gour | ooh, that's good |
20:33:17 | gour | so, nimrod-side is no problem then |
20:38:16 | * | fowl joined #nimrod |
20:40:44 | * | filwit joined #nimrod |
20:40:58 | filwit | hi |
20:41:31 | Araq | reactormonk: line 970 of the JS codegen |
20:41:32 | dom96 | filwit: Your design is absolutely sexy. |
20:41:50 | filwit | thanks dom96, glad you like it :) |
20:42:03 | Araq | it adds the proc body to 'p.g.code' which is the produced JS file |
20:42:05 | filwit | i'm not sure about the colors |
20:42:15 | Araq | filwit: excellent work! |
20:42:23 | Araq | but the colors need more gold ;-) |
20:42:32 | filwit | ha! i knew it! |
20:42:36 | dom96 | Araq and his gold... |
20:42:41 | filwit | what are you thinking? |
20:43:02 | Araq | apparently we spent way more time together than I remember :P |
20:43:33 | filwit | yes, lol |
20:43:44 | filwit | do you want to logo to be gold instead of blue? |
20:43:51 | gour | my monitor shows everything too dark, so cannot comment on colors, but design is very fine |
20:44:24 | filwit | (i will have to reverse the accent colors [blue where there's gold, etc] that way) |
20:44:28 | filwit | thanks, gour |
20:44:44 | filwit | i will try and brighten the grey up if things are too dark |
20:45:17 | Araq | filwit: yeah perhaps, I don't the blue, but it's weird the crown is not gold |
20:45:18 | gour | i'll try to check tomorrow on my netbook which shows 'em more realistic |
20:45:20 | filwit | though you might try adjusting your colors, i keep my monitor pretty balanced and it looks good (IMO) the level of dark-grey |
20:45:26 | Araq | *I don't mind the blue |
20:45:35 | filwit | gour: okay, let me know if you think it's still too dark |
20:45:48 | * | gour has old 17" CRT... |
20:46:01 | * | Anaphaxeton quit (Quit: Αποχώρησε) |
20:46:13 | filwit | gour: ahh.. that makes sense |
20:46:23 | filwit | gour: you shouldn't sit in front of that thing |
20:46:26 | filwit | lol |
20:46:32 | filwit | jp |
20:46:58 | filwit | Araq: i will try adjusting things.. but you can't really use the gold and the blue (both) on the logo |
20:47:12 | filwit | they conflict too much, it looks ugly, i tried |
20:47:16 | gour | the paradox is that i've i7 with 8GB...but atm, budget is in such condition :-/ |
20:47:26 | * | Anaphaxeton joined #nimrod |
20:48:48 | Araq | I don't upgrade my CPU anymore so that the compiler doesn't get too slow on older machines :D |
20:48:51 | filwit | Araq: both the blue and the gold are exciting colors (they grab your attention) so you have to combined them with a neutral color (like white, grey, black, brown, etc) |
20:49:00 | gour | filwit: checked with my netbook...still i considered it a bit too dark |
20:49:06 | dom96 | Araq: Get a raspberry pi :P |
20:49:15 | filwit | gour: okay, i will see what i can do there |
20:49:40 | Araq | filwit: alright then I prefer gold over blue |
20:49:53 | Araq | it's a *crown* anyway |
20:49:55 | filwit | Araq: upgrade, but keep the old machine around as a test computer? |
20:50:14 | gour | filwit: i'd prefer having lighter sidebar like in present version |
20:50:18 | filwit | Araq: okay, will try it that way and post another mock-up |
20:50:21 | Araq | filwit: nah, I have no reason to upgrade anyway |
20:51:51 | filwit | you don't do anything with your computer besides program Nimrod? |
20:52:04 | filwit | what about watching movies? |
20:52:21 | filwit | guess computers have been able to play movies fine for ages huh... |
20:52:31 | Araq | it's an intel quad core, not too old |
20:52:34 | * | gour has to do some video-editing using cinelerra |
20:52:59 | * | filwit taxes the shit outta his system |
20:53:33 | filwit | i use a lot of demanding art programs, so having a good system is important |
20:53:45 | Araq | and cpus stopped getting faster years ago :P |
20:53:51 | filwit | plus, i play a couple video games (CS:GO & Skyrim) |
20:54:00 | filwit | lol, yeah true |
20:54:18 | dom96 | Only thing my PC is missing is RAM... |
20:54:21 | filwit | that's why i can't wait for Parallella to get faster |
20:54:34 | dom96 | and somehow every new stick I buy fails to work :\ |
20:54:40 | filwit | lame |
20:54:41 | reactormonk | Araq, uh-oh |
20:54:57 | filwit | i have 8gb, and Linux only ever uses ~ 2-3 |
20:55:04 | filwit | even with tons of stuff open |
20:55:11 | filwit | so it's kinda overkill |
20:55:29 | filwit | OpenShot sometimes eats it all up, but that's due to a bug I think |
20:55:46 | reactormonk | filwit, use chromium and java |
20:55:55 | gour | filwit: any news in regard to openshot's C++ lib? |
20:56:02 | filwit | i use Chromium.. don't know about Java though |
20:56:04 | Araq | bootstrap nimrod with --gc:none and compile aporia with it :P |
20:56:50 | filwit | but even chromium takes up... lets see combined, ~300mb |
20:56:55 | dom96 | I only have 2GB :\ |
20:57:10 | filwit | good thing you use Arch, domb96 :) |
20:57:37 | dom96 | Doesn't help much :P |
20:57:43 | filwit | gour: i don't know anything about OpenShot's C++ lib, sorry |
20:57:51 | dom96 | Currently using 1.5GB RAM and 500MB swap. |
20:57:59 | * | gour moved to debian after ~5yrs with arch and before that ~5yrs with gentoo |
20:59:00 | * | filwit no longer respects any of gours opinions |
20:59:10 | filwit | :p |
20:59:35 | filwit | seriously though, how could you leave Arch for Debian? |
20:59:45 | gour | filwit: jonathan (openshot dev) is working for quite some time on the new lib written in C++ - http://www.openshotvideo.com/2012/12/openshot-library-introducing-time-curves.html |
21:00:12 | gour | too bad nimrod was not really available, 'cause it would be much better than python |
21:01:19 | gour | filwit: i do not have so much time to tinker with my system as i used to have...besides that i was not overly happy with the quality which deteriorated in last few years...then things like systemd etc, |
21:01:42 | filwit | you don't like systemd? |
21:01:54 | filwit | i found it to be much easier than before |
21:02:06 | filwit | but i don't know much about things at that level |
21:04:23 | gour | well, init scripts 'just works' while i had problems with systemd when evaluating frugalware which is nice 'fork' of arch (e.g. no AUR) |
21:04:58 | gour | what are the blockers for 0.9.2? |
21:06:42 | * | Anaphaxeton quit (Read error: Connection reset by peer) |
21:07:30 | Araq | dunno, a couple of bugs and a few missing features |
21:07:54 | gour | so, not far away ;) |
21:08:32 | Araq | plus releases take too much of my time so I barely manage to make more then 2-4 per year |
21:09:06 | gour | release manager? |
21:09:26 | Araq | it's mostly automated already |
21:09:51 | Araq | windows and mac os X testing machines would be very helpful though |
21:10:03 | gour | what takes most of the time then? |
21:10:20 | gour | i can winxp under vbox, not other OS-es |
21:10:25 | gour | *test |
21:10:32 | fowl | arch linux has this habit of introducing system-breaking changes and expecting you to read the arch front news before installing them |
21:10:42 | * | gour nods |
21:11:08 | fowl | i also disliked the high-and-mighty feeling i got from the ppl in ##archlinux who would rather chide you than help you fix stuff |
21:11:54 | gour | fowl: #archlinux is one of the most useless channel i've ever visited, although i like(d) arch |
21:12:09 | fowl | yeah |
21:12:17 | fowl | arch itself is a good distro and i loved aur |
21:12:28 | gour | noise/signal ratio is...welll |
21:13:07 | * | XAMPP-8 quit (Ping timeout: 248 seconds) |
21:13:27 | Araq | cleaning up the documentation, building the installers, updating the website, ensuring the installers work |
21:13:52 | Araq | somehow it always takes half a day |
21:14:59 | gour | it would be nice that the present manual one days evolves into PIN (Programming in Nimrod) |
21:15:55 | filwit | color-swap and I lightend the background: http://reign-studios.com/nimrod/web-design2.png |
21:15:58 | * | Anaphaxeton joined #nimrod |
21:16:10 | filwit | you can compare the two: |
21:16:14 | filwit | http://reign-studios.com/nimrod/web-design.png |
21:16:15 | filwit | http://reign-studios.com/nimrod/web-design2.png |
21:16:32 | gour | much better, imho |
21:17:15 | filwit | also, I kinda like how the "nimrod" text is just a flat-color.. but if you want it to look more like "gold" Araq, I can try and add a little shine to it |
21:17:20 | filwit | gour: great! |
21:17:38 | Araq | filwit: I like the *first* one better ;-) |
21:17:53 | filwit | LOL |
21:18:05 | filwit | there is no pleasing you, i quit |
21:18:12 | gour | filwit: the 3es could be more readable? |
21:18:14 | Araq | perhaps make only the crown gold |
21:18:18 | filwit | no, but what exactly do you like about the first one? |
21:18:35 | filwit | gah... that's going to look ugly |
21:18:36 | filwit | but okay |
21:18:55 | Araq | the side feels warmer if the side-bar is in gold :D |
21:18:59 | Araq | *the site |
21:19:20 | Araq | the blue sidebar is too cold |
21:19:23 | filwit | also, I agree with gour about the grey colors. I think it looks better with the lighter grey bg. what do you think about that Araq? new grey or old grey? |
21:19:59 | Araq | hrm I suppose I should check how it looks on my real machine |
21:20:16 | Araq | on my laptop the darker grey looks better |
21:20:55 | filwit | hmmm... maybe okay i can darken it a little |
21:21:11 | filwit | dom96, do you have an opinion on the second image? |
21:23:33 | filwit | ps. Araq, gour. My code example is stolen from the D homepage, but I think the actual website should have something similar (the current example is too short) |
21:23:54 | Araq | I noticed as there is no 'byLine' in Nimrod :P |
21:24:28 | filwit | yeah... and i did "count.inc" instead of "count += 1".. not sure which is better |
21:24:31 | Araq | filwit: the darker colors look better on my real monitor too |
21:24:48 | filwit | okay, well i will adjust some stuff |
21:25:13 | filwit | i'm telling you though, the whole "two-color icon" thing isn't going to look good (and if you think it does you're crazy) |
21:25:19 | Araq | what if you make the *white* part of "nimrod code" and the of the crown in gold? |
21:25:43 | Araq | why is it white in the first place? |
21:26:25 | filwit | white is a neutral color |
21:26:36 | filwit | like i said, both the blue and the gold are the accent colors |
21:26:41 | filwit | they grab your attention |
21:26:54 | filwit | you cant put them side-by-side, they conflict |
21:27:04 | filwit | so you use a neutral |
21:27:11 | filwit | and since the background is dark |
21:27:22 | filwit | white is really the only choice |
21:27:34 | Araq | what you say makes sense |
21:27:40 | dom96 | oh sorry was away |
21:27:46 | dom96 | give me a sec to read what was said :P |
21:28:00 | filwit | i'll play around with different combinations and see what I can come up with that looks good |
21:28:58 | filwit | ps, dom86, notice the butterfly Aporia icon |
21:29:13 | filwit | that actual icon is to simple for what the real one should be |
21:29:29 | filwit | but i have an idea about how to make the Aporia one |
21:31:56 | filwit | BTW... i sorta forgot, why is there a "inc()" command in Nimrod again? Why not just require people to do "count += 1" ? |
21:32:04 | dom96 | I prefer the first one, the background is too light in the second one I think. |
21:32:19 | Araq | "inc" existed before "+=" :P |
21:32:19 | filwit | okay, thanks for the input |
21:32:26 | dom96 | filwit: Yes, I noticed the Aporia icon. Very nice touch ;) |
21:36:40 | Araq | filwit: also 'myEnumValue += 1' looks weird, inc(myEnumValue) does not |
21:43:44 | filwit | hybrid colors and grey-value: http://reign-studios.com/nimrod/web-design3.png |
21:44:17 | filwit | Araq: i much prefer 'myEnumBalue += 1' to 'inc(...)' |
21:45:07 | Araq | *shrug* I don't think you should be able to add ints and enums |
21:45:28 | dom96 | I think the background colour should be as dark as it was at the beginning. |
21:45:44 | filwit | okay, will try that |
21:46:02 | filwit | Araq, what do you think about the logo hybrid-colors? |
21:46:08 | filwit | compare with the other versions |
21:46:15 | filwit | http://reign-studios.com/nimrod/web-design.png |
21:46:17 | filwit | http://reign-studios.com/nimrod/web-design2.png |
21:46:19 | filwit | http://reign-studios.com/nimrod/web-design3.png |
21:46:21 | Araq | I agree with dom96 about the background color |
21:46:27 | filwit | k |
21:46:55 | Araq | I'm wondering if "nimrod code" is appropriate |
21:47:11 | Araq | or if it should be "nimrod" instead |
21:47:16 | filwit | sure |
21:47:53 | filwit | what about the colors though? |
21:48:05 | * | gour --> sleep. will check log tomorrow :-) |
21:48:11 | Araq | the crown is great now :-) |
21:48:26 | filwit | you like the gold crown with the blue letters? |
21:48:27 | dom96 | I'm wondering whether the nav button's background colours should be as dark as they were too (together with the side bar gray) |
21:48:40 | * | gour quit (Quit: WeeChat 0.4.0) |
21:49:05 | filwit | dom96: i think they where a bit too dark before |
21:49:11 | Araq | the gold crown with the blue letters is good |
21:49:16 | filwit | it was hard to see, they are a bit more clear now |
21:49:24 | Araq | but please make one with gold letters for comparison |
21:49:43 | filwit | Araq: *sigh*... somehow i knew you where going to like that combo |
21:49:44 | filwit | lol |
21:49:45 | dom96 | filwit: sure. |
21:50:00 | filwit | okay, i will make another one real quick |
21:52:19 | * | dom96 can only imagine how hard it will be to get all browsers to render this correctly |
21:53:50 | filwit | it's easy, i have been doing this kind of thing for awhile |
21:54:14 | dom96 | That's good to hear :) |
21:54:21 | filwit | most browsers are pretty consistent these days, even IE |
21:54:49 | filwit | usually you just give a warning message if someone has IE 7 and below, telling them to download Firefox or Chrome |
21:54:49 | dom96 | I haven't done serious HTML coding in a while, so i'm still stuck in the "ugh, IE6 must be supported" mindset. |
21:54:56 | dom96 | But we can screw IE 6 :P |
21:55:13 | NimBot | Araq/Nimrod e39b93c Araq [+0 ±4 -0]: micro optimizations for the evaluation engine |
21:55:13 | NimBot | Araq/Nimrod 857694d Araq [+0 ±6 -0]: preparations for a generational GC |
21:55:13 | NimBot | Araq/Nimrod 696f7f2 Araq [+6 ±22 -5]: Merge branch 'master' of github.com:Araq/Nimrod |
21:55:14 | filwit | yeah, IE has a much lower network traffic now actaully |
21:55:41 | filwit | but yeah, a few years ago IE6 (and 7... and 8) where a bitch |
21:55:50 | filwit | IE8 is till a concern, but not a hug deal |
21:55:51 | dom96 | But it's probably quite rare that potential Nimrod programmers would even use IE. |
21:56:02 | filwit | really the only thing it lacks is semi-transparent pngs |
21:56:10 | dom96 | Unless maybe they are forced at work. |
21:56:27 | dom96 | I can help you with the HTML/CSS if you'd like. |
21:56:46 | filwit | yes that's true, but the point of advertising is to grab a larger audience.. so who knows :) |
21:57:13 | filwit | okay, but I'll probably be fine making the HTML myself |
21:57:25 | filwit | will let you know if i run out of time and need your help |
21:57:43 | Araq | filwit: excellent, thanks a lot |
21:58:06 | Araq | it should be easy to adapt whatever html you come up with with our build system |
21:58:21 | Araq | er, templating system |
21:58:25 | filwit | yes i'll just give you guys the code and let you work it in |
21:58:30 | dom96 | filwit: Great. Thanks a lot for doing this btw! |
21:58:43 | filwit | you said before you just use flat-html files per-page right? |
21:59:12 | filwit | dom96: np :) like i said I'm willing to help in these ways |
21:59:23 | dom96 | yeah. We may add some dynamic stuff to the website though. |
21:59:25 | Araq | filwit: yeah |
21:59:34 | filwit | this stuff is quite a bit simpler (to me) than implementing a compiler feature |
21:59:54 | Araq | ah well I was about to answer: |
22:00:17 | dom96 | in fact hrm, perhaps it would be nice to think about the future of the website. |
22:00:37 | dom96 | It will be very noticeable if we're forced to hack stuff in. |
22:00:38 | Araq | no, nimrod's flat procs do not "fall down" for a complex project |
22:00:57 | Araq | there are other reasons that make the compiler hard to hack |
22:01:18 | fowl | Araq: i want to poke around the VM |
22:01:22 | fowl | whats a good entry point |
22:01:36 | dom96 | filwit: Will the sidebar be visible on all pages? |
22:01:37 | filwit | also, you should really consider using less abbreviation, Araq. It's really hard to follow |
22:01:55 | Araq | filwit: I never wrote it with contributors in mind :P |
22:02:01 | filwit | lol |
22:02:10 | filwit | yeah i understand |
22:02:19 | filwit | dom96: that's the basic idea |
22:02:29 | filwit | we should keep this project simple right now |
22:02:34 | Araq | but I also don't get why the abbrevs are hard |
22:02:40 | filwit | flat HTML is fine, since we're all programmers here |
22:02:54 | filwit | if the sight starts getting really big, we can move to a CMS |
22:03:06 | filwit | but that takes quite a bit more time |
22:03:28 | filwit | Araq: because descriptive names are .. descriptive |
22:03:31 | dom96 | A simple jester app can be written instead of using a full blown CMS ;) |
22:04:16 | filwit | Araq: I don't like how C# forces you to set all those "public static override" stuff everywhere, but I do think their library names are done well |
22:04:17 | Araq | filwit: nah, it'll only be verbose |
22:04:26 | dom96 | Araq: When you have abbreviations everywhere, you have the same abbreviations in different procedures meaning different things. As you try to understand the flow of the code you move between procedures and get confused quickly. |
22:04:35 | dom96 | Well at least I think that is a bit of a problem for me. |
22:05:12 | Araq | honestly I think if the abbrevs are hard for you, maybe you shouldn't hack the compiler in the first place :P |
22:05:26 | Araq | 'sem' is a prefix which means "semantic checking" |
22:05:44 | filwit | Araq: i think that's a poor attitude towards the issue if you want more support |
22:05:51 | Araq | the compiler has like ~50 procs which start with 'sem' |
22:06:06 | Araq | 'semanticCheckIf' vs semIf |
22:06:18 | Araq | that's a problem for perhaps 5 minutes |
22:06:20 | filwit | ^ perfect example |
22:06:47 | filwit | no, much more than 5mins |
22:07:01 | Araq | the trick is to ask Araq :P |
22:07:08 | filwit | you just think that cause you understand the structure, and honestly I think you just pick things up really fast |
22:07:35 | dom96 | "maybe you shouldn't hack the compiler in the first place :P" Yep, I shouldn't be. I am extremely unqualified, I have barely an idea of what 'semantic checking' is, and I don't have the time to learn this stuff. But the fact is that you are all I have, so if you want me to fix the compiler for you, abbreviations do not help me :P |
22:07:41 | filwit | when you don't know what's going on, and are reading the code to try and learn, having descriptive names helps a lot |
22:08:14 | dom96 | I would say most potential contributors are in that boat. |
22:09:13 | dom96 | You can just force people that know how compilers work to work on your compiler, but there are very few people that have that kind of experience. |
22:11:03 | Araq | have you guys ever read http://nimrod-code.org/intern.html#short-description-of-nimrod-s-modules ? |
22:11:45 | filwit | once a long time ago, but yeah that is useful |
22:12:02 | filwit | still, some of those modules are pretty big |
22:12:11 | filwit | the internals get pretty confusing sometimes |
22:12:38 | Araq | yeah the internals could be improved |
22:12:45 | filwit | i don't care about local-var abbreviation, that is easy to follow |
22:12:47 | Araq | no, it's not the abbrevs fault :P |
22:13:51 | Araq | you have to realize that nimrod is more complex than you think it is |
22:14:00 | Araq | and the compiler reflects that |
22:14:28 | Araq | and there are books describing how a compiler works |
22:14:55 | filwit | Araq: I've shown tree different (C#/Java) programmers D before (independently). and a universal complaint was that the Standard lib was "too abbreviated" "like C++ STL" |
22:15:14 | filwit | Nimrod is 5 times more abbreviated than D |
22:15:26 | Araq | and yet it's still too verbose :P |
22:15:38 | Araq | for instance there is not enough type inference for anon procs |
22:15:55 | dom96 | filwit: how so? |
22:16:08 | filwit | dom96: length vs len |
22:16:17 | filwit | dom96: "inc()" |
22:16:28 | filwit | dom96: newseq() |
22:16:35 | Araq | I keep writing lenght so making that 'len' was a good idea |
22:16:53 | filwit | Araq: i prefer "count" and always have |
22:16:56 | Araq | python also chose that btw |
22:17:01 | filwit | makes much more sense |
22:17:11 | Araq | a string has no "count" |
22:17:13 | dom96 | 'count' to me sounds like an action |
22:17:20 | dom96 | as in 'count this for me' |
22:17:26 | Araq | and you want the same term everywhere |
22:17:39 | Araq | otherwise you never know if it's len, length, count, size ... |
22:17:47 | Araq | like it's in C# |
22:18:01 | Araq | it's also very bad for generic code |
22:18:11 | filwit | dom96: yes, but it also means the "count of something" whereas "size/length" is more spacial |
22:18:24 | Araq | fowl: start with compiler/evals.nim |
22:19:14 | filwit | Araq: I dont' like everything about C#'s design |
22:19:25 | filwit | Araq: and the count/length thing is one of them |
22:19:34 | filwit | (of the things i don't like) |
22:19:39 | Araq | actually I wanted to make it an operator: # |
22:19:52 | Araq | but then it was too late, # was taken for comments |
22:20:23 | filwit | what would '#' be used for? |
22:20:36 | Araq | it makes no sense to have an operator for bit shifting, but none for 'len' |
22:20:46 | Araq | # would be 'len' |
22:20:56 | Araq | it's common in math |
22:21:23 | filwit | waayy to cryptic |
22:21:25 | filwit | :P |
22:21:42 | Araq | yeah. for 5 minutes. |
22:21:51 | filwit | for learning |
22:21:55 | dom96 | that would be quite elegant |
22:22:03 | Araq | and then you appreciate you never have to guess what it's called, as it is always # |
22:22:08 | filwit | people wont learn your code if it's really hard to understand at a glance |
22:22:27 | filwit | and new-programmers (like Game Script writers) will have a really hard time using things |
22:22:45 | filwit | which is what I wanted Nimrod for in the first place |
22:22:57 | Araq | interesting |
22:23:13 | filwit | but, ultimately it started to get to complicated. Which is why I'm arguing this issue so much |
22:23:50 | filwit | if you haven't noticed, i'm a bit of a perfectionist.. but people often don't realize how important the details are, and "first impressions" are very important as well |
22:24:31 | filwit | I found D because, at first, it looked like a hybrid of C++ and C#... unfortunately it has too many technical problems, and it's syntax is a bit over complicated |
22:24:51 | filwit | Nimrod gets things right though |
22:24:54 | filwit | on the technical level |
22:25:02 | filwit | the GC design is great |
22:25:09 | filwit | and most of the syntax is great too |
22:25:23 | filwit | there are just fundamental concepts that I think break it |
22:25:40 | filwit | like you having a "new" and a "newarr" and a "newseq" |
22:25:52 | Araq | there is no newarr :P |
22:25:52 | filwit | that points to a fundamental design flaw, IMO |
22:25:58 | filwit | oh, my bad |
22:26:05 | filwit | still, you get my point |
22:26:09 | filwit | it's hard to remember |
22:26:13 | Araq | I could easily overload 'newseq' to 'new' |
22:26:14 | filwit | and it's hard to learn |
22:26:33 | filwit | yes, but like i said, i think it points to a bigger problem |
22:26:41 | filwit | things should be type-specific |
22:26:43 | Araq | but you should use 'var x: seq[int] = @[]' anyway I guess |
22:27:02 | Araq | you can also do: var x = int.new() |
22:27:24 | filwit | yes see that is exactly what I'm talking about |
22:27:39 | filwit | there are two ways of making a sequence, and that's confusing |
22:27:51 | filwit | it would be much better to say 'var x = int.new()' |
22:28:02 | filwit | and consistently use that syntax throughout |
22:28:14 | filwit | and enfore it as a standard somehow |
22:28:28 | filwit | but anyways, that is just my thoughts |
22:28:46 | dom96 | I don't think i've ever used newSeq() |
22:29:05 | Araq | well we'll get proper constructors soon anyway for different reasons |
22:29:11 | filwit | yes because we're talking about a core item |
22:29:20 | filwit | seq is a core type |
22:29:33 | filwit | so having a "convenience" syntax isn't that big a deal |
22:29:46 | filwit | but apply the concept to other peoples objects |
22:30:02 | Araq | yeah I then can use 'new T(...)' great |
22:30:12 | Araq | except that I don't know the parameters anyway |
22:30:22 | Araq | and it's not 'new T' when it's behind a factory |
22:30:23 | filwit | hmm, interesting. didn't know you where adding that in |
22:30:38 | filwit | Araq: i agree with you |
22:30:46 | Araq | I'm adding something like that in |
22:30:50 | filwit | Araq: i never liked contructors either |
22:30:52 | Araq | syntax is up for debate |
22:31:19 | filwit | one sec |
22:31:40 | dom96 | how about: make seq[T] |
22:31:41 | dom96 | :P |
22:34:26 | filwit | this is what i wish Nimrod did: https://gist.github.com/PhilipWitte/4969024 |
22:34:37 | * | FreeArtMan quit (Ping timeout: 244 seconds) |
22:34:53 | filwit | and I wish that it was consistent like that, thoughout the standard-lib |
22:35:47 | filwit | that to me, is easy and elegant to understand |
22:36:08 | filwit | you can bind things to the type directly, and enforce that it's used like OOP |
22:36:28 | filwit | and there is a distinction between an "init" and a "proc" |
22:36:49 | filwit | but ultimately it's looks and feels the same as a global functions bound to a type |
22:36:54 | Araq | not unlike Delphi does it |
22:37:13 | filwit | i've never used Delphi, so i can't comment |
22:37:25 | filwit | but i'm sure others have used similar designs |
22:37:39 | filwit | the point is, they probably don't have Nimrods awesome compiler behind them |
22:37:45 | Araq | is the implicit this/self passed by 'var'? |
22:37:55 | Araq | in your design? |
22:38:08 | filwit | no, ref probably (off the top of my head) |
22:38:34 | filwit | you could always have a way of distinguishing that, for instance.. if it's a tuple |
22:38:38 | filwit | it's probably var |
22:38:41 | filwit | (maybe) |
22:38:54 | filwit | or there could be a pragma |
22:39:24 | Araq | what about: |
22:39:34 | Araq | proc (var Foo).bar = ... |
22:40:24 | filwit | I'm perfectly fine with that.. and ultimately i think there should be a way of "embeding" the procs like regular OOP code |
22:40:29 | filwit | type Foo = |
22:40:33 | filwit | bar : int |
22:40:44 | filwit | foo : proc() = |
22:40:50 | filwit | bar = 10 |
22:41:06 | filwit | but that was just sugar for: |
22:41:20 | filwit | proc (var Foo).foo() = ... |
22:41:30 | Araq | well as I said, you can get that today with a macro |
22:41:37 | dom96 | https://gist.github.com/dom96/4969058 |
22:41:53 | dom96 | That's already possible with macros isn't it? |
22:41:59 | Araq | and maybe we should sanctionize a 'class' macro for the stdlib |
22:42:20 | dom96 | I prefer that over writing 'Foo.' |
22:42:33 | Araq | dom96: yeah but you can go even further than that |
22:42:45 | dom96 | Araq: what do you mean? |
22:42:51 | filwit | Araq: sure, but the whole language needs to be consistent like that... AND you need to be able to build global variabls like that as well (IMO) |
22:43:18 | filwit | if things aren't consistent, it's incredibly hard to use. |
22:43:32 | filwit | Nimrod is a big project, so changing something like that would take a lot of time |
22:43:51 | filwit | it's not really a realistic request of me |
22:44:13 | Araq | I get your point but you're also overly concerned about this |
22:44:30 | Araq | for instance, Lua is widely successful for game modding |
22:44:30 | filwit | like i said, perfectionist :) |
22:44:47 | filwit | yes, but I would never use Lua for games |
22:44:48 | Araq | and it neither has classes nor does it even catch most typos |
22:45:07 | filwit | well the Classes are more for the Game Engine itself |
22:45:18 | filwit | but not entirely |
22:45:46 | filwit | i have a really good design actually, which requires Partial classes (or similar concepts) |
22:45:50 | filwit | that we're making in C# |
22:45:55 | filwit | i don't like C# |
22:46:11 | Araq | dom96: check fowl's class macros for example |
22:46:25 | Araq | filwit: see that's suprising |
22:46:40 | Araq | I don't get what you dislike about C# |
22:46:43 | filwit | Araq: tell me, is it possible to make a macro which binds a var to a type? |
22:46:54 | Araq | filwit: yes |
22:47:05 | Araq | er, or no |
22:47:14 | Araq | depending on how you look at it |
22:47:24 | filwit | Araq: Mono sux, and I'm a linux fan. C# is low, and overly bloated, doens't support range based syntax, etc, etc |
22:47:32 | filwit | C# is slow*** |
22:47:33 | dom96 | Araq: You mean inheritance and stuff? |
22:47:51 | Araq | dom96: I mean no need to split 'Foo' into a type and a class |
22:48:12 | dom96 | Araq: I see, yes, of course. |
22:48:30 | dom96 | fowl's class macro is in fact very cool |
22:48:53 | filwit | Araq: can i do something like: var Person.speed = 10... then access it like: for p in people: p.pos += Person.speed ?? |
22:52:17 | Araq | filwit: no ;-) |
22:53:26 | Araq | you can do: mac Person.speed = 10 |
22:53:35 | Araq | where 'mac' is a macro |
22:53:58 | Araq | but why is that so important in the first place? |
22:54:16 | filwit | because when you use someone's library, you do this: |
22:54:25 | filwit | var player = Person.new() |
22:54:39 | filwit | and everywhere, you're using "Person.whatever" |
22:54:56 | Araq | so you have player.speed vs. Person.speed :P |
22:54:56 | filwit | so then, when you want to access global settings, you use the same syntax |
22:55:19 | filwit | no, lets do this: |
22:55:24 | filwit | type Person = |
22:55:29 | Araq | yeah, yeah, got it |
22:56:23 | filwit | okay fine, the point is. if you have an interal Person function, which uses a global variable, and you also want to present that to other to set in a consistent way (same applies to global functions), then everything is consistent |
22:57:15 | filwit | look, know that i'm not actually making a feature request here or anything... i understand that's really unrealistic and unfare of me to ask |
22:57:19 | filwit | i'm just arguing a point |
22:57:26 | Araq | btw games/simulations is one of the domains where OO can shine ;-) |
22:57:51 | Araq | it was called "simula" for a reason |
23:00:19 | filwit | idk, this is why i started making my own language. I wanted to get nitty-gritty with the syntax, but It was hard hacking on Nimrod, so I figured it would be just as easy to re-write my own (syntax-wise) |
23:01:19 | filwit | obviously, my language isn't going to go anywhere |
23:01:22 | filwit | it's just a toy |
23:01:44 | Araq | you know, the compiler has the infrastructure for alternative syntaxes |
23:01:59 | filwit | yeah i was thinking about that last night |
23:02:45 | filwit | but idk, I will have to take another look |
23:03:12 | filwit | one of the things I did with my design, was that the "compiler" was designed to stay open, and accept changes in real-time |
23:03:41 | Araq | like nimrod's :P |
23:03:49 | Araq | zahary is working on that feature |
23:03:52 | filwit | it maintains lists of things, so if a change is made, it catches and reports the error instantly (or it could if there was a IDE) |
23:04:06 | dom96 | Araq: oh yeah, I think you missed my question about first class iterators. Do they support the implicit 'result' variable? |
23:04:10 | filwit | yes i hear that Nimrod now has compiler-as-a-service |
23:04:14 | filwit | that's good to hear |
23:04:37 | Araq | yeah and it's lots of work ;-) |
23:04:54 | filwit | yes because the language wasn't designed that way to begin with :) |
23:05:11 | Araq | that's debatable |
23:05:36 | filwit | well i wasn't saying there's something wrong with Nimrod |
23:05:40 | Araq | it always had an ID mechanism to support incremental compilation |
23:05:54 | Araq | it's MUCH harder than you think it is :P |
23:06:02 | filwit | i was saying to make something "say open" vs "run 'n done" is a bit different |
23:06:24 | Araq | plus generating C doesn't help |
23:07:00 | Araq | it's much easier to do in an interpreter |
23:07:16 | filwit | Araq: i know.. like I said, i started writing a language :P it's complicated. mine can only add ints together right now in interpreted mode |
23:07:24 | Araq | dom96: I can't remember, try it |
23:07:29 | dom96 | Araq: I get odd results when I don't define the 'result' variable. |
23:07:43 | Araq | o.O |
23:08:04 | Araq | well you never have to define it |
23:08:12 | Araq | it's either there or it isn't |
23:08:21 | filwit | Araq: yeah exactly.. the language has to be designed to be interpreted , and compiled (obviously doesn't work in all cases) |
23:08:43 | dom96 | yeah, this is definitely a bug :P |
23:09:00 | Araq | dom96: not necessarily |
23:09:11 | Araq | does 'return' set your explicit 'result' var? |
23:09:23 | Araq | well ... hrm how would you know |
23:09:46 | dom96 | with each 'yield' the 'result' variable seems to be reset. |
23:09:57 | Araq | filwit: I have a hard time coming up with a language that can be compiled but not interpreted |
23:10:22 | Araq | dom96: that's a feature I guess |
23:10:38 | dom96 | Araq: Care to explain how this is a feature? :P |
23:10:42 | Araq | what does 'result' mean when you 'yield' anyway? |
23:10:47 | filwit | Araq: i just ment that certain pointer arithmetic wont work in interpreted mode (not safely at least). |
23:11:18 | Araq | well safety is a whole different topic :P |
23:11:26 | filwit | lol, yeah |
23:11:31 | dom96 | Aporia really needs a gist feature... |
23:12:06 | filwit | pointer arithmetic is inherently unsafe anyways, so i guess it's the programmers fault if he kills the compiler |
23:12:35 | dom96 | Araq: https://gist.github.com/dom96/a0fbc9ab2bca9bf35ce8 |
23:12:57 | filwit | dom96: what do you mean gist feature? |
23:13:07 | Araq | if you pass fat pointers around, it's easy to make pointer arithmetic safe, filwit |
23:13:27 | dom96 | filwit: As "Gist my selection and place URL in clipboard." |
23:13:30 | dom96 | *As in |
23:13:48 | dom96 | So that I don't have to switch to my browser and do it |
23:13:52 | filwit | Araq: unless the pointers have to be a certain size (they're passed to GPU shader constants for example). |
23:14:10 | filwit | Araq: in which case, they have to be completely unmanaged |
23:14:26 | filwit | Araq: thought that's a really, really rare situation |
23:14:31 | filwit | though** |
23:15:07 | filwit | dom96: not a bad idea |
23:15:09 | Araq | dom96: ok, that's a bug I guess |
23:15:22 | dom96 | ok, i'm reporting |
23:17:57 | Araq | filwit: please make that alternative parser and use the rest of nimrod's compiler |
23:18:46 | Araq | the shebang can be used to tell which syntax to use: #! alternativeSyntax |
23:18:55 | filwit | Araq: i will look into it |
23:19:13 | Araq | and ask if you're stuck |
23:19:39 | Araq | filwit: I know you don't want to hear it but ... |
23:20:11 | Araq | first design with golden crown and "nimrod" would be best I think |
23:20:27 | Araq | no "nimrod code" please |
23:21:12 | filwit | yeah that's fine, i will adjust somethings |
23:21:27 | filwit | so you like the blue? |
23:21:37 | filwit | oh nvrmd |
23:21:44 | filwit | you said golden crown |
23:21:54 | Araq | and golden "nimrod" |
23:22:00 | filwit | okay |
23:22:02 | filwit | one sec |
23:22:05 | Araq | the blue is then only in the navigation |
23:22:19 | filwit | so.. not the first design then :P |
23:22:29 | Araq | yes the first design |
23:22:40 | filwit | okay, one sec |
23:22:42 | Araq | the side-bar stays gold |
23:23:07 | filwit | yeah i understand, i'm going to grab something to eat |
23:23:11 | filwit | and will make it after |
23:53:23 | filwit | okay: http://reign-studios.com/nimrod/web-design4.png |
23:53:32 | filwit | if you like it, i will make the HTML |
23:54:09 | filwit | notice i added a hint of a shine to the "nimrod" to make it look more metallic |
23:54:16 | filwit | but that's about the only change |
23:54:47 | Araq | I noticed it |
23:54:49 | Araq | I like it |
23:54:57 | Araq | all of it :-) |
23:55:00 | filwit | great! |
23:55:09 | filwit | will make the template then |
23:55:54 | Araq | excellent |
23:56:32 | Araq | I'll add a "design by filwit" in the footer |
23:56:42 | Araq | well I may use your real name |
23:57:04 | filwit | okay, I'll add that in |
23:57:14 | filwit | do you know my real name o.O? |
23:57:43 | Araq | nah |
23:57:52 | filwit | oh btw, you like the gold footer right? |
23:57:53 | Araq | but it shouldn't be too hard to figure it out |
23:57:55 | filwit | (vs the blue) |
23:58:13 | Araq | yes I like it |
23:58:15 | * | dom96 thinks he would prefer the flat colour for the "nimrod" text |
23:58:26 | filwit | no dom96 |
23:58:28 | filwit | dont start |
23:58:32 | Araq | but gold is not really a color, dom96 |
23:58:37 | filwit | ;-P |
23:58:43 | Araq | flat gold is yellow :P |
23:58:58 | dom96 | Go back to blue :P |
23:59:06 | Araq | blue is too cold |
23:59:09 | filwit | (i know dom96, i know) |
23:59:36 | dom96 | The gold is too flashy |