00:00:00 --- log: started forth/16.11.25 00:13:36 --- join: roboguy` (~roboguy_@cpe-76-92-217-212.kc.res.rr.com) joined #forth 00:52:05 --- quit: roboguy` () 01:33:31 --- quit: mnemnion (Remote host closed the connection) 01:34:26 --- join: mnemnion (~mnemnion@2601:643:8102:7c95:74e5:df04:dd1b:bfeb) joined #forth 01:38:39 --- quit: mnemnion (Ping timeout: 240 seconds) 03:07:51 --- quit: John[Lisbeth] (Remote host closed the connection) 03:13:18 --- join: John[Lisbeth] (~user@52.165.40.155) joined #forth 03:36:19 --- join: mnemnion (~mnemnion@2601:643:8102:7c95:74e5:df04:dd1b:bfeb) joined #forth 03:40:39 --- quit: mnemnion (Ping timeout: 240 seconds) 03:56:54 --- quit: nighty (Quit: Disappears in a puff of smoke) 04:18:29 okay 04:18:30 http://sprunge.us/WTJJ 04:18:35 add those lines to your .bashrc 04:18:37 just the bash++ ones 04:18:40 that should give you bash forth 04:35:41 example of usage after this? 04:35:54 will it be like power(2, 2) or 2 2 power() ? 04:36:58 --- join: mnemnion (~mnemnion@2601:643:8102:7c95:74e5:df04:dd1b:bfeb) joined #forth 04:39:03 push 2 2; power 04:39:09 safePop 04:39:38 Now bash is a very excellent concatenative language 04:39:54 [root@nerfur rough]# push 2 2; power 04:39:54 bash: stack: bad array subscript 04:39:54 bash: [-1]: bad array subscript 04:39:54 bash: [-1]: bad array subscript 04:39:56 bash: stack: bad array subscript 04:39:57 bash: [-1]: bad array subscript 04:39:58 bash: [-1]: bad array subscript 04:39:58 bash: stack: bad array subscript 04:40:00 bash: [-1]: bad array subscript 04:40:00 bash: stack: bad array subscript 04:40:03 interesting 04:40:04 bash: [-1]: bad array subscript 04:40:04 (standard_in) 1: syntax error 04:40:05 bash: stack: bad array subscript 04:40:05 bash: [-1]: bad array subscript 04:40:08 bash: [-1]: bad array subscript 04:40:09 bash: stack: bad array subscript 04:40:10 bash: [-1]: bad array subscript 04:40:11 bash: [-1]: bad array subscript 04:40:12 bash: [-1]: bad array subscript 04:40:13 bash: stack: bad array subscript 04:40:14 oh boy this may be a bug on his part 04:40:15 bash: [-1]: bad array subscript 04:40:15 bash: [-1]: bad array subscript 04:40:17 bash: stack: bad array subscript 04:40:17 bash: [-1]: bad array subscript 04:40:20 bash: [-1]: bad array subscript 04:40:20 bash: [-1]: bad array subscript 04:40:33 You allright man? 04:40:50 ? 04:41:01 You just had a huge error on your system I Think man 04:41:10 alot of your terminal output seemed to spew to the irc client 04:41:24 do I need something more besides this strings in .bashrc? 04:41:29 --- join: nighty (~nighty@s229123.ppp.asahi-net.or.jp) joined #forth 04:41:46 no I do not think so 04:42:00 you also need to type bash one more time 04:42:05 so that your .bashrc gets loaded 04:42:38 --- quit: mnemnion (Ping timeout: 260 seconds) 04:56:10 --- join: ASau (~user@netbsd/developers/asau) joined #forth 05:33:24 --- join: nal (~nal@adsl-72-50-85-7.prtc.net) joined #forth 05:55:05 --- quit: proteusguy (Ping timeout: 268 seconds) 06:07:25 --- join: proteusguy (~proteusgu@node-4lr.pool-101-108.dynamic.totbb.net) joined #forth 06:07:26 --- mode: ChanServ set +v proteusguy 06:32:25 --- join: Kumool (~nal@adsl-72-50-85-170.prtc.net) joined #forth 06:35:10 --- quit: nal (Ping timeout: 268 seconds) 06:38:35 --- join: Zarutian (~zarutian@168-110-22-46.fiber.hringdu.is) joined #forth 06:39:06 --- quit: Zarutian (Read error: Connection reset by peer) 06:39:06 --- join: Zarutian_ (~zarutian@168-110-22-46.fiber.hringdu.is) joined #forth 06:39:06 --- nick: Zarutian_ -> Zarutian 06:39:56 --- join: mnemnion (~mnemnion@71.198.73.193) joined #forth 06:44:43 --- quit: mnemnion (Ping timeout: 260 seconds) 07:04:13 --- quit: DGASAU (Read error: Connection reset by peer) 07:09:27 --- join: DGASAU (~user@lmpc.drb.insel.de) joined #forth 07:12:22 --- quit: DGASAU (Write error: Connection reset by peer) 07:12:51 --- join: DGASAU (~user@lmpc.drb.insel.de) joined #forth 07:36:18 --- join: ricky_ricardo (~rickyrica@2601:240:4203:ecb0:e1f4:3639:bf7f:38c5) joined #forth 07:40:36 --- join: mnemnion (~mnemnion@2601:643:8102:7c95:74e5:df04:dd1b:bfeb) joined #forth 07:45:16 --- quit: mnemnion (Ping timeout: 258 seconds) 08:04:40 --- join: kumul (~nal@adsl-64-237-238-87.prtc.net) joined #forth 08:05:27 --- quit: Kumool (Ping timeout: 260 seconds) 08:31:11 --- join: karswell (~user@200.135.46.217.dyn.plus.net) joined #forth 08:31:59 --- join: rgrinberg (~rgrinberg@172-97-185-7.cpe.distributel.net) joined #forth 08:41:21 --- join: mnemnion (~mnemnion@2601:643:8102:7c95:74e5:df04:dd1b:bfeb) joined #forth 08:45:57 --- quit: mnemnion (Ping timeout: 256 seconds) 09:00:44 --- quit: kumul (Quit: WeeChat 1.4) 09:48:46 --- quit: true-grue (Read error: Connection reset by peer) 10:21:52 --- join: Mat4 (~claude@ip5b4100d3.dynamic.kabel-deutschland.de) joined #forth 10:25:24 --- join: mnemnion (~mnemnion@2601:643:8102:7c95:74e5:df04:dd1b:bfeb) joined #forth 10:25:29 hello 10:30:06 --- quit: mnemnion (Ping timeout: 258 seconds) 10:49:04 --- join: mnemnion (~mnemnion@2601:643:8102:7c95:b932:b261:348f:df3d) joined #forth 11:00:38 --- quit: ricky_ricardo (Ping timeout: 260 seconds) 11:59:45 --- quit: Zarutian (Quit: Zarutian) 12:02:17 Hello Mat4, I only now saw your messages about gelFORTH. I need to set up inotify notifications for DM's. 12:02:24 I wasn't able to DM you but that's probably because you weren't online. 12:11:46 As for Boolean reduction and Quine-McCluskey, the PSoC can do dynamic partial reconfiguration at least from the ARM. I was working on parallel Quine-McCluskey until I found a paper that has an (often) faster way of finding prime implicants than Quine-McCluskey and supports incremental synthesis/synthesis of partially specified Boolean functions. 12:13:12 hello 12:15:51 hello 12:21:06 --- join: DocPlatypus (~skquinn@c-73-6-60-72.hsd1.tx.comcast.net) joined #forth 12:30:43 pointfree: That's nice. Have you implemented this approach yet ? 12:36:12 Mat4: I started something for parallel Quine-McCluskey http://hub.darcs.net/pointfree/gelFORTH-synth-experiments/browse/adjacent-minterms.4th but not the latter. On the PSoC I have only synthesized non-minimized logic so far. 12:40:30 Mat4: A paper on the latter method: http://odroid.0xffffffff.in/~deploy/parallel-synth/10.1109@DAC.1992.227866.pdf 12:45:43 --- join: roboguy` (~roboguy_@cpe-76-92-217-212.kc.res.rr.com) joined #forth 12:46:38 As side note to synthesising non-minimised logic, I have the problem that no cheap available FPGA chip allow somewhat efficient implementations of my current logic designs. However there exist some FPGA like devices which seem to be suitable for ASIC equivalent development and I'm think that these chip for example: http://www.easic.com/products/28-nm-easic-nextreme-3/ would allow me to develop much faster than current... if I would be a 12:56:45 Mat4: I had no idea such a thing existed. I know someone on reddit who would be interested in "80% lower power than FPGAs" 12:57:13 Mat4: Your message got cut off at "if I would be a" 12:59:19 ..able to get my hand on one of thus devices 13:00:31 Oh. That was the important bit. 13:05:01 the main problem in my opinion is that there approach is of course patented and as such not evaluable (at least for me). I want to release my final design with an open licence... and for this it seems that I must redevelop solutions which have already be solved and that's in my opinion quite insane from a common wealth perspective 13:08:57 --- quit: workp (Quit: leaving) 13:09:15 --- join: workp (~workp@host-89-240-182-228.as13285.net) joined #forth 13:11:04 I must also take care not implementing patented ideas, which means I end up explore complete new approaches (which may be on the other side an advantage) 13:15:38 --- quit: rgrinberg (Remote host closed the connection) 13:17:57 --- join: rgrinberg (~rgrinberg@172-97-185-7.cpe.distributel.net) joined #forth 13:29:17 --- part: Mat4 left #forth 13:52:43 --- join: nal (~nal@adsl-72-50-87-213.prtc.net) joined #forth 13:55:26 --- join: true-grue (~true-grue@176.14.222.10) joined #forth 14:45:49 --- quit: roboguy` (Read error: Connection reset by peer) 14:46:03 --- join: roboguy` (~roboguy_@cpe-76-92-217-212.kc.res.rr.com) joined #forth 14:58:24 --- join: Zarutian (~zarutian@168-110-22-46.fiber.hringdu.is) joined #forth 14:59:30 --- join: Zarutian_ (~zarutian@168-110-22-46.fiber.hringdu.is) joined #forth 14:59:30 --- quit: Zarutian (Read error: Connection reset by peer) 14:59:30 --- nick: Zarutian_ -> Zarutian 15:24:02 --- join: MickyW (~MickyW@p57A2FBB0.dip0.t-ipconnect.de) joined #forth 15:32:59 --- quit: workp (Ping timeout: 260 seconds) 15:35:44 --- part: DocPlatypus left #forth 15:53:13 --- join: Kumool (~nal@adsl-64-237-236-87.prtc.net) joined #forth 15:56:40 --- quit: nal (Ping timeout: 245 seconds) 16:46:03 --- quit: roboguy` (Read error: Connection reset by peer) 16:46:51 --- join: tano (32bd2cb4@gateway/web/freenode/ip.50.189.44.180) joined #forth 16:47:13 --- nick: tano -> Guest99683 16:47:31 --- join: roboguy` (~roboguy_@cpe-76-92-217-212.kc.res.rr.com) joined #forth 16:57:31 http://sprunge.us/WbGC 17:00:53 John[Lisbeth]: that seems to be empty 17:02:26 --- join: mat4 (~Claude@ip5b40a28a.dynamic.kabel-deutschland.de) joined #forth 17:03:32 http://sprunge.us/UVcI 17:03:38 --- quit: mat4 (Client Quit) 17:05:35 --- part: Guest99683 left #forth 17:06:41 --- join: Guest99683 (32bd2cb4@gateway/web/freenode/ip.50.189.44.180) joined #forth 17:10:36 --- quit: rgrinberg (Remote host closed the connection) 17:10:43 I've got a really really great and very forthy experience in bash 17:10:59 Hello ... i'm looking for examples of a modern use of Forth? Similar as in Philae spacecraft. 17:11:38 It is difficult to pinpoint production forth code, and honestly there's not alot of it 17:11:46 but forth has great potential for these things 17:11:56 as do other concatenative languages 17:12:23 Forth is often used in hardware design because it is very easy to get forth running on new chips. 17:12:41 You can basically use forth to breathe a chip to life and test it out 17:12:55 Forth is also used in microcode 17:13:00 so it is good for things like firmware or robotics 17:13:36 this kind fo code like the things people use to debug chips, firmware, or the low level programming in robots often do not get talked about in popular software media 17:14:05 Many forth programmers are very low level programmers very close to the hardware and they don't usually work in the cloud or on apps though sometimes they do. 17:14:32 Though some forth programmers like myself are high level programmers and I am trying to apply forth techniques to web services and systems programming 17:14:47 Does that help explain it a little? 17:16:11 20:12 < John[Lisbeth]> Forth is often used in hardware design because it is very easy to get forth running on new chips. 17:16:14 20:12 < John[Lisbeth]> You can basically use forth to breathe a chip to life and test it out 17:16:22 wtf are you talking abiut 17:19:53 Thank you John ... when I think about using Forth I always think of it as a low level programming language. Does it have enough high level support libraries ... for networking or something similar ... 17:20:45 well most true forths as in inspired by chuck moore's forth are very very barebones 17:21:11 but there are higher level versions such as factor or 8th that attempt to add more lispy type features 17:21:33 though these features can be added to forths such as gforth if you know the process 17:21:58 zy]x[yz: ? 17:27:49 --- join: rgrinberg (~rgrinberg@172-97-185-7.cpe.distributel.net) joined #forth 17:28:47 It would be great if that kind of support would be added to Forth. :D 17:29:10 Thanks for the info. It helped. 17:31:45 Guest99683, there is no canonical forth. a lot of people who use it roll their own 17:32:20 there's an ansi standard, but there's also a camp of forth users who reject the standard 17:32:42 --- nick: Guest99683 -> msiks 17:40:10 it's not necessary that the modern usage example is written in ANSI Forth, it can be some variant. It just needs to be a project from a previous 10 years. 17:45:14 --- quit: mark4 (Ping timeout: 260 seconds) 17:56:04 --- quit: Quozl` (Ping timeout: 256 seconds) 17:59:13 Guest99683: Here's a few http://www.mpeforth.com/ngr.htm#forthapps 17:59:44 --- quit: nighty- (Remote host closed the connection) 17:59:50 more on the bomb defusal application: http://www.inventio.co.uk/threeforthsmakeahole.htm 18:04:44 awesome 18:04:47 --- join: Quozl` (~quozl@owl.laptop.org) joined #forth 18:08:05 I just rediscovered this anecdote while looking for the bomb defusal article: http://alanwinfield.blogspot.com.br/2013/03/extreme-debugging-tale-of-microcode-and.html 18:18:00 --- join: nighty- (~cp@www.taiyolabs.com) joined #forth 18:19:40 --- quit: true-grue (Read error: Connection reset by peer) 18:21:11 interesting 18:47:35 --- quit: roboguy` (Read error: Connection reset by peer) 18:48:52 --- join: roboguy` (~roboguy_@cpe-76-92-217-212.kc.res.rr.com) joined #forth 19:29:50 --- quit: MickyW (Quit: Leaving. Have a nice day.) 19:35:39 --- quit: Kumool (Quit: WeeChat 1.4) 19:52:28 --- quit: Zarutian (Quit: Zarutian) 19:59:41 --- quit: msiks (Quit: Page closed) 20:48:51 --- quit: roboguy` (Read error: Connection reset by peer) 20:49:55 --- join: roboguy` (~roboguy_@cpe-76-92-217-212.kc.res.rr.com) joined #forth 21:24:34 --- join: proteus-guy (~proteus-g@180.183.112.94) joined #forth 21:31:11 --- quit: John[Lisbeth] (Ping timeout: 268 seconds) 21:42:28 --- join: John[Lisbeth] (~user@52.165.40.155) joined #forth 22:07:12 --- quit: roboguy` () 22:24:13 --- quit: rgrinberg (Ping timeout: 268 seconds) 22:31:48 --- join: rgrinberg (~rgrinberg@172-97-185-7.cpe.distributel.net) joined #forth 23:42:18 --- quit: rgrinberg (Ping timeout: 265 seconds) 23:59:59 --- log: ended forth/16.11.25