00:00:00 --- log: started forth/08.07.24 00:17:24 --- quit: tarbo (clarke.freenode.net irc.freenode.net) 00:17:24 --- quit: ASau` (clarke.freenode.net irc.freenode.net) 00:17:24 --- quit: Raystm2 (clarke.freenode.net irc.freenode.net) 00:17:24 --- quit: segher (clarke.freenode.net irc.freenode.net) 00:17:24 --- quit: aspect (clarke.freenode.net irc.freenode.net) 00:17:49 --- join: ASau` (n=user@79.111.17.100) joined #forth 00:17:49 --- join: Raystm2 (i=Ray@unaffiliated/raystm2) joined #forth 00:17:49 --- join: segher (n=segher@84-105-61-45.cable.quicknet.nl) joined #forth 00:17:49 --- join: aspect (i=aspect@burns.dreamhost.com) joined #forth 00:18:05 --- join: tarbo (n=me@unaffiliated/tarbo) joined #forth 00:49:05 --- join: ramkrsna (n=ramkrsna@unaffiliated/ramkrsna) joined #forth 01:05:16 --- join: qFox (i=C00K13S@234pc222.sshunet.nl) joined #forth 01:17:47 --- join: mathrick (n=mathrick@users177.kollegienet.dk) joined #forth 02:07:02 --- quit: craigoz ("Leaving.") 03:18:35 --- join: aum (n=aum@60-234-243-247.bitstream.orcon.net.nz) joined #forth 03:29:16 how many stacks does factor use? just data and return? 03:57:09 --- quit: nighty^ ("Disappears in a puff of smoke") 04:26:56 --- join: tathi (n=josh@pdpc/supporter/bronze/tathi) joined #forth 04:26:56 --- mode: ChanServ set +o tathi 04:28:38 aum: I believe factor has four stacks: data, retain, call, and catch. 04:30:34 k 04:40:05 * aum is considering adding an 'object stack' to his forth, separate from the regular data, float and call stacks 04:55:26 --- quit: tarbo (clarke.freenode.net irc.freenode.net) 04:57:30 --- join: tarbo (n=me@unaffiliated/tarbo) joined #forth 05:25:04 --- quit: aum ("Leaving") 06:38:10 We added a kind of object stack/array to pForth for our embedded use. 06:38:14 --- nick: TreyB_ -> TreyB 06:38:45 BTW, does anyone maintain pForth now? 06:39:05 --- join: koaftder (n=koft@adsl-77-224-90.rmo.bellsouth.net) joined #forth 06:39:12 I don't know. The web pages still exist. 06:57:49 --- quit: maht (Remote closed the connection) 07:07:39 --- quit: ramkrsna ("Leaving") 07:10:49 --- join: maht (n=maht__@85.189.31.174.proweb.managedbroadband.co.uk) joined #forth 07:11:36 --- part: koaftder left #forth 07:35:01 --- quit: ASau` (Read error: 110 (Connection timed out)) 07:58:41 --- quit: ecraven ("bbl") 08:29:16 --- join: madwork (n=foo@204.138.110.15) joined #forth 09:01:03 --- join: JasonWoof (n=jason@c-65-96-161-30.hsd1.ma.comcast.net) joined #forth 09:01:03 --- mode: ChanServ set +o JasonWoof 09:30:34 --- quit: JasonWoof (Read error: 110 (Connection timed out)) 10:31:23 --- join: ecraven (n=nex@cm207-109.liwest.at) joined #forth 10:56:42 --- join: ASau` (n=user@79.111.26.157) joined #forth 11:17:51 --- quit: ecraven ("bbl") 11:35:12 --- join: vixey (n=nono@amcant.demon.co.uk) joined #forth 11:54:38 --- join: JasonWoof (n=jason@c-65-96-161-30.hsd1.ma.comcast.net) joined #forth 11:54:38 --- mode: ChanServ set +o JasonWoof 12:21:22 --- join: ygrek (i=user@gateway/tor/x-be26f63d68b70edd) joined #forth 12:58:29 --- quit: tathi (Read error: 110 (Connection timed out)) 14:25:35 --- quit: ygrek (Remote closed the connection) 15:22:32 --- join: tathi (n=josh@pdpc/supporter/bronze/tathi) joined #forth 15:22:32 --- mode: ChanServ set +o tathi 15:30:59 is there a forth shell 15:31:09 which is a good replacement of zsh .. or bash or whatever 15:31:11 ? 15:36:15 Forth isn't really big on file-system manipulation. 15:36:29 ok 15:37:05 why? i think most forths for windows and *nix have fs words. 15:37:54 slava, But, it's not like, bash, or zsh, etc.. 15:38:50 what bash and zsh do is hardly rocket science 15:38:56 <.< 15:39:08 I think you're missing my point. 15:39:24 you can implement some recursive directory tree words on top of syscalls, and globs, in 2 pages of code 15:39:33 then write a simple parser for command lines and you have yourself a shell. 15:39:37 Probably not. 15:39:44 add job control and line editing for extra credit 15:39:44 Forth is a very powerful and expressive programming language. 15:40:13 once you write some layers, yes 15:40:43 Right, I haven't seen anything resembling a shell environment. 15:40:59 Although, obviously such a thing is possible. 15:41:41 factor comes with a simple shell, its 230 lines of code. 15:42:08 it doesn't do file system manipulation, it just runs processes 15:42:16 Right. 15:42:28 I'm thinking more on the order of bash/sh/zsh. 15:42:36 As in, scripting file system manipulations. 15:42:47 i wouldn't want to use shell script for that anyway. 15:43:03 Eh, it seems the most common use of these scripts. 15:43:14 File system manipulation, initialization, configuration, etc... 15:43:29 I prefer not to use shell scripting at all if I can avoid it. 15:43:31 they run /bin/rm, /bin/ls, etc for 'file system manipulation'. 15:44:05 True.. They operate using executables based off of the filesystem they run on as their kernel. 15:44:35 They're definitely based off of the filesystem. 15:44:51 Where as FORTH is pretty much file system neutral. 15:45:59 Thinking about it though, it probably would be trivial to implement a simple FORTH like shell. 15:48:32 I think I have an idea for what to program in Forth :)) 15:49:33 Lol. 15:49:51 Maybe some simple words to set up an exec environment, and run a binary. 15:50:04 Seriously, FORTH already has many features that would make it more powerful that basic sh. 15:50:10 Ahem, than. 15:50:38 { "find . -name *.txt" "grep foo" "sort" "uniq" } run-pipeline 15:51:00 Coool. 16:51:26 --- quit: ASau` (Read error: 110 (Connection timed out)) 16:52:33 --- nick: modesto -> mdst 16:54:38 --- nick: mdst -> FunWithVowels 16:55:17 --- nick: FunWithVowels -> modesto 17:01:06 --- join: craigoz (n=craigo@202.63.56.72) joined #forth 17:54:44 --- nick: modesto -> salvia 17:56:14 --- nick: salvia -> modesto 18:29:19 --- quit: tathi ("leaving") 18:29:45 --- quit: qFox ("Time for cookies!") 19:09:01 --- quit: vixey () 21:25:52 --- join: ASau` (n=user@79.111.30.233) joined #forth 22:18:03 --- join: ygrek (i=user@gateway/tor/x-d8dd4b358af9e2cb) joined #forth 23:28:46 --- join: ramkrsna (n=ramkrsna@unaffiliated/ramkrsna) joined #forth 23:32:57 --- join: _mathrick (n=mathrick@users177.kollegienet.dk) joined #forth 23:32:57 --- quit: mathrick (Read error: 104 (Connection reset by peer)) 23:42:08 --- nick: _mathrick -> mathrick 23:53:24 --- part: craigoz left #forth 23:59:59 --- log: ended forth/08.07.24