00:00:00 --- log: started forth/11.08.23 00:12:21 --- quit: Fox78 (Ping timeout: 260 seconds) 00:51:25 --- quit: betta_y_omega (Ping timeout: 260 seconds) 00:53:53 --- join: betta_y_omega (~betta_y_o@90.166.231.220) joined #forth 00:55:53 --- quit: ASau (Quit: off) 01:26:14 --- join: malyn_ (~malyn@server.strangegizmo.com) joined #forth 01:28:02 --- join: Fox78 (~fox@123.118.154.10) joined #forth 01:28:23 --- quit: malyn (Quit: Disconnecting from stoned server.) 01:28:25 --- quit: malyn_ (Changing host) 01:28:25 --- join: malyn_ (~malyn@unaffiliated/malyn) joined #forth 01:29:10 --- nick: malyn_ -> malyn 01:41:53 Unfortunately I can't find a binary for any forth on snow leopard! I don't have the developer tools on my macbook so I can't build it either. 02:00:07 http://www.complang.tuwien.ac.at/forth/gforth/Binonly/ 02:00:43 i don't use any apple products at all, but the last file listed - gforth-0.5.0-binonly-osx.tar.gz - might be worth a try? 02:03:03 heh or maybe not, unless you're on powerpc 02:03:05 $ file gforth 02:03:05 gforth: Mach-O executable ppc 02:29:25 Build it yourself. 02:29:38 gforth 0.5.0 has one major drawback. 02:29:52 Its FFI is completely broken anywhere besides l00n1x. 02:30:23 At least its libc part. 02:31:20 gforth 0.7.0 has broken marker. 02:31:36 PFE has broken "include". 02:33:55 --- join: tathi (~josh@dsl-216-227-119-3.fairpoint.net) joined #forth 02:35:07 danieljames: you only need a gforth installed to build from scratch (e.g. CVS) -- if you start from one of the distribution tarballs you should be fine. 02:35:22 This is actually wrong. 02:35:34 If you want FFI, you need libltdl and all the stuff. 02:49:09 --- quit: DGASAU (Remote host closed the connection) 02:51:36 --- join: DGASAU (~user@91.218.144.129) joined #forth 02:52:34 Sure. All I was saying is, you don't need gforth installed to build gforth, unless you're starting from CVS. 02:55:13 To build from CVS checkout first requirement is CVS accessible. 02:55:19 This isn't about gforth CVS. 03:02:05 --- quit: betta_y_omega (Ping timeout: 245 seconds) 03:07:10 --- join: betta_y_omega (~betta_y_o@90.166.231.220) joined #forth 03:11:36 --- quit: Fox78 (Remote host closed the connection) 03:19:29 Oh, ok. I saw "I can't find a binary from any forth on snow leopard", and assumed it was about building gforth. 03:55:59 --- join: MayDaniel (~MayDaniel@unaffiliated/maydaniel) joined #forth 04:00:21 Which version is called "Snow Leopard"? 04:00:33 uname -mrs 04:01:04 It is definitly wrong to assume that everyone should remember all that zoo. 04:25:28 It's not unreasonable to expect OS X users who use Forth to be aware of it. 04:27:14 I use OSX only when I need to support it. 04:31:15 I get that. But you could have just asked for the uname output instead of making blanket statements about "if you want others to understand you". 05:06:32 --- join: nighty^ (~nighty@TOROON12-1279662182.sdsl.bell.ca) joined #forth 05:11:00 --- quit: MayDaniel (Read error: Connection reset by peer) 05:55:37 --- quit: gogonkt (Ping timeout: 240 seconds) 06:08:35 DGASAU: uname reports 10.8.0 i386 06:08:54 beats me why that is different from the 10.6.8 in the 'about' box 06:18:48 ok thanks everyone- I'll install the unix dev tools and just build the latest version of gforth. I have to admit I am surprised there isn't anything simple available to download and try. Ultimately I do need something with an FFI as I will be doing some computer vision research and will need to FFI out to OpenGl and camera drivers. 06:22:36 gforth developers almost ignore anything besides l00n1x. 06:22:56 In "good" GNU traditions. 06:24:37 --- quit: nighty^ (Remote host closed the connection) 06:35:13 I will report back when I have succeeded :-) 06:35:30 --- join: Fox78 (~fox@123.121.67.75) joined #forth 07:20:48 --- join: nighty^ (~nighty@TOROON12-1279662182.sdsl.bell.ca) joined #forth 08:30:31 --- quit: ttmrichter (Quit: No wonder these puppets are always in a lousy mood.) 08:35:32 --- quit: I440r (Remote host closed the connection) 08:46:52 --- join: xpololz (~xpololz@50.80-203-124.nextgentel.com) joined #forth 08:58:55 --- join: MayDaniel (~MayDaniel@unaffiliated/maydaniel) joined #forth 09:07:36 --- quit: Fox78 (Remote host closed the connection) 09:07:54 --- join: mark4 (~mark4@baldr.openesque.com) joined #forth 09:12:51 --- quit: MayDaniel (Read error: Connection reset by peer) 09:16:35 --- join: schmx (~marcus@c83-254-205-42.bredband.comhem.se) joined #forth 09:16:36 --- quit: schmx (Changing host) 09:16:36 --- join: schmx (~marcus@sxemacs/devel/schme) joined #forth 09:18:47 --- join: xpolol (~xpololz@50.80-203-124.nextgentel.com) joined #forth 09:20:28 --- quit: schme (Ping timeout: 240 seconds) 09:20:28 --- quit: xpololz (Ping timeout: 240 seconds) 10:15:35 --- join: danieljames_ (~danieljam@94-193-7-241.zone7.bethere.co.uk) joined #forth 10:15:36 --- quit: danieljames (Read error: Connection reset by peer) 10:15:36 --- nick: danieljames_ -> danieljames 11:35:48 --- join: benny99 (~benny@f055060174.adsl.alicedsl.de) joined #forth 11:36:02 --- quit: ttmrichter|work (Ping timeout: 252 seconds) 11:41:00 Success! 12:00:59 --- quit: benny99 (Quit: Leaving) 12:02:27 --- quit: tathi (Ping timeout: 252 seconds) 12:36:13 --- join: ASau (~user@95-26-244-67.broadband.corbina.ru) joined #forth 13:54:25 does DUMP work in pforth v27? 13:58:44 I don't care. 13:58:56 I have fixed numerous pForth bugs and continue doing that. 13:59:45 In my fork it works. 13:59:55 segfaults 14:00:16 that which i've just built from pkgsrc on both i386 and amd64 (netbsd) produce segfault 14:03:11 http://sf.net/projects/apforth/ 14:03:15 That works for me. 14:04:25 On the other hand, are you sure that you're using it correctly? 14:17:01 i believe so 14:17:10 if gforth is anything to go by :D 14:17:59 --- quit: qFox (Ping timeout: 245 seconds) 14:23:09 http://pastebin.com/pm85b20Z 14:24:27 This is definitly incorrect. 14:25:04 Tick returns execution token. 14:25:13 Execution token is _not_ an address. 14:31:08 No wonder that you end with core dump. 14:31:11 * ASau shrugs. 14:32:50 --- quit: xpolol (Quit: Leaving) 14:34:12 ok so it works with a supposedly valid address (using HERE) 14:34:26 how can i get the address of an execution token in pforth? 15:12:39 --- quit: nighty^ (Ping timeout: 252 seconds) 15:13:54 Execution token is execution token. 15:14:27 Do you understand what "token" means in programming? 15:41:46 absolutely no clue..... but i figured that in this implementation there'd be some way to resolve this "token" to the address of the code that gets executed when you call the word associated with the execution token 15:43:39 "Token" means that this is opaque value. 15:44:17 Since in Forth everything is a number, it is just a random number. 15:44:25 ok fair enough 15:48:50 In particular, in pForth there's _no_ way to get the address of the code that gets executed. 16:22:33 --- join: ttmrichter (~ttmrichte@59.61.13.18) joined #forth 16:30:45 --- join: Fox78 (~fox@123.118.147.146) joined #forth 17:27:26 --- join: ttmrichter|work (6e502c2a@gateway/web/freenode/ip.110.80.44.42) joined #forth 17:39:46 --- quit: ASau (Ping timeout: 240 seconds) 18:58:21 --- join: nighty (~nighty@69-165-220-105.dsl.teksavvy.com) joined #forth 19:23:39 --- join: Deformative (~Joseph@cpe-98-155-76-109.san.res.rr.com) joined #forth 20:53:40 --- join: Joseph_ (~Joseph@cpe-98-155-76-109.san.res.rr.com) joined #forth 20:56:47 --- quit: Deformative (Ping timeout: 252 seconds) 20:58:41 --- nick: Joseph_ -> Deformative 21:22:12 --- join: IAmHere (~IAmHere@c-24-8-201-198.hsd1.co.comcast.net) joined #forth 21:56:29 danieljames: don't forget to apply patch when you start using markers. 22:03:28 --- quit: Fox78 (Remote host closed the connection) 22:35:40 --- nick: Deformative -> bernardj 22:36:46 --- nick: bernardj -> Deformatve 23:01:18 --- quit: IAmHere (Quit: IAmHere) 23:36:19 --- join: qFox (~peter@53526A79.cm-6-3b.dynamic.ziggo.nl) joined #forth 23:59:59 --- log: ended forth/11.08.23