00:00:00 --- log: started forth/17.12.30 00:23:56 --- quit: dys (Ping timeout: 265 seconds) 00:29:03 --- quit: mark4 (Ping timeout: 252 seconds) 00:45:12 --- join: gravicappa (~gravicapp@h62-133-162-159.dyn.bashtel.ru) joined #forth 01:04:08 --- quit: MrMobius (Ping timeout: 260 seconds) 01:24:13 --- join: wa5qjh (~Thunderbi@freebsd/user/wa5qjh) joined #forth 01:24:35 --- quit: wa5qjh (Remote host closed the connection) 02:41:47 --- join: dddddd (~dddddd@unaffiliated/dddddd) joined #forth 02:54:15 --- quit: phadthai (Ping timeout: 248 seconds) 03:18:14 --- join: phadthai (mmondor@ginseng.pulsar-zone.net) joined #forth 04:26:34 --- quit: groovy2shoes (Ping timeout: 240 seconds) 04:33:08 --- quit: gravicappa (Ping timeout: 272 seconds) 05:36:14 --- join: deep-thought (~deep-thou@2001:8003:f064:400:f66d:4ff:fe58:ff4b) joined #forth 05:48:39 --- join: nighty- (~nighty@q029220.ppp.asahi-net.or.jp) joined #forth 06:18:20 --- quit: nighty- (Ping timeout: 246 seconds) 06:37:15 --- join: ncv (~neceve@90.192.20.90) joined #forth 06:37:15 --- quit: ncv (Changing host) 06:37:15 --- join: ncv (~neceve@unaffiliated/neceve) joined #forth 07:28:36 --- join: dys (~dys@tmo-123-190.customers.d1-online.com) joined #forth 07:56:36 --- join: gravicappa (~gravicapp@62.133.162.32) joined #forth 08:05:38 --- join: groovy2shoes (~groovy2sh@unaffiliated/groovebot) joined #forth 08:30:41 --- quit: deep-thought (Quit: Leaving) 08:49:27 --- quit: gravicappa (Ping timeout: 256 seconds) 09:16:47 --- join: mark4 (~mark4@99.30.241.51) joined #forth 10:28:55 --- join: Zarutian_PI2 (~3.1415@173-133-17-89.fiber.hringdu.is) joined #forth 10:28:55 --- quit: Zarutian_PI (Read error: Connection reset by peer) 11:08:12 --- join: jcob (~user@cpe-172-74-189-35.nc.res.rr.com) joined #forth 11:10:41 I cant seem to get gforth to build on arch :l 11:10:48 Anyone ever manage to? 11:12:17 i haven't tried anywhere but debian derivatives, but where does it fail? 11:12:58 At ./test/coretest.out, 11:13:33 Like this: ! (ret) ! (ret) ! Segmentation fault 11:13:39 where the ret is a \n 11:14:38 I guess I'm using clang, I'll try CC=/usr/bin/gcc... 11:14:45 oh. i hoped it would be some trivial issue with the C kernel not building because of assumptions about include path contents :( 11:15:32 *nod* i have not tried with clang 11:18:05 building with clang 3.8.0 i get a lot of warnings about being invoked with unsupported flags, but it seems to succeed 11:21:17 (gforth 0.7.3, ubuntu 16.04, x86-64) 11:21:19 Just got it to work using gcc 11:21:26 (insert shrug) 11:27:31 I think my yaourt under Manjaro/Arch builds with clang, some warnings but succeded. 11:36:27 I do wonder, what's the point of using forth thats been compiled from C? 11:37:23 Like, are there any libraries/frameworks etc that make it useful on gnulinux? Do people use it because its more productive? 11:45:11 --- quit: endersending (Quit: Leaving) 11:47:05 jcob: I use it as a stress ball. It is one of a few interpreters that I use that way. 12:25:02 you can link C libraries just fine from a metacompiled forth. but using C for the kernel makes it a lot easier to target multiple platforms with minimal porting effort 12:45:12 --- nick: Zarutian_PI2 -> Zarutian_PI 12:55:38 Using C for the kernel feels gross. I need to get over it. 12:57:12 it's inaesthetic but useful in a lot of real cases :/ 13:09:53 --- join: user131231 (5c13e83a@gateway/web/freenode/ip.92.19.232.58) joined #forth 13:10:05 Are there any text editors that support forth syntax highlighting? 13:11:33 vim and emacs both do 13:11:46 not that there is a lot of syntax to highlight 13:12:43 thanks 13:16:52 --- quit: user131231 (Quit: Page closed) 13:23:43 --- quit: dys (Ping timeout: 256 seconds) 14:00:45 --- join: dys (~dys@tmo-122-56.customers.d1-online.com) joined #forth 14:09:10 --- join: Gromboli (~Gromboli@static-72-88-80-103.bflony.fios.verizon.net) joined #forth 14:15:42 --- quit: ncv (Remote host closed the connection) 14:30:30 this is just another reason to hate on gforth 14:30:33 its NOT a forth 14:31:07 when gforth can metacompile 100% of its own sources then it will be forth 15:40:07 --- join: Riviera- (Riviera@2a03:b0c0:1:d0::10:b001) joined #forth 16:13:37 mark4: Then what do you suggest using? 16:39:37 well i would say x4 but... a: im biased and b: its not ans forth and c: its not as far advanced as gforth 16:39:42 i just hate gforth lol 16:39:56 does x4 metacompile itself? 16:40:23 not yet and maybe never but it COULD with the right extensions. gforth will NEVER be able to metacompile itslef 16:40:38 why not? 16:41:07 because nobody in their right minds would write a c compiler extension to make it do so 16:41:33 I do wonder, (this might be off topic sorry), why does the c compiler not expose itself 16:41:49 nothing is OT in here except trolling lol 16:41:50 while, for instance, the forth compiler and most lisp compilers do? 16:42:01 ecause c is compile time only 16:42:06 not comile time / run time 16:42:34 : constant create , does> @ ; 16:42:51 you CANT do things like that in c. part of that definition is compile time, the other part is run time 16:43:34 NIM used to have something like that but now it does not 16:44:38 when a c compiler is compiling its target application it is NOT extending itself with the application. you cannot run the code thats being compiled DURING the compile 16:45:02 now you can compile some executable and RUN that executable from within the build system but thats not the same 16:49:23 and arent build systems incredibly fragile usually? 16:49:51 exactly 16:50:04 which is why we keep getting new ones. make, cmake, kbuild... .. . 16:50:15 Zarutian_PI: yes. Please kill me, I have to use cmake all the time :~l 16:50:41 lol 16:52:48 jcob: and it breaks if something the project relies on has slightly incompatible version installed. 16:57:18 people wonder, in the case of embedded programming, why I insist of them to set up their build systems inside a VM which then get snapshot-frozen. (And no Docker 'containers' do not cut it) 17:17:13 What idiom do forth programmers use to read a whole file regardless of length? Streams? Vectors? Something different entirely? 17:20:46 (basically read till end of file I guess) 17:28:13 --- join: deep-thought (~deep-thou@2001:8003:f064:400:f66d:4ff:fe58:ff4b) joined #forth 17:36:27 Well, I guess there's slurp-file, but I dont think it works with stdin :/ 18:32:25 Zarutian_PI, can i come work for you lol 19:32:07 --- join: nighty- (~nighty@q029220.ppp.asahi-net.or.jp) joined #forth 20:41:37 --- quit: dddddd (Remote host closed the connection) 22:30:16 --- quit: mark4 (Ping timeout: 248 seconds) 23:45:38 --- quit: Gromboli (Quit: Leaving) 23:59:59 --- log: ended forth/17.12.30