00:00:00 --- log: started forth/10.09.02 00:05:57 --- quit: ygrek (Ping timeout: 245 seconds) 00:10:23 --- join: DavidC99|x (~DavidC99@bas2-windsor12-1128533178.dsl.bell.ca) joined #forth 00:11:04 --- quit: DavidC99 (Ping timeout: 265 seconds) 00:12:46 --- join: H4ns1 (~Hans@pD4B9E36C.dip.t-dialin.net) joined #forth 00:13:16 --- part: H4ns1 left #forth 00:15:45 --- join: ygrek (debian-tor@gateway/tor-sasl/ygrek) joined #forth 00:39:15 --- join: martin_hex (~mjc@93-97-29-243.zone5.bethere.co.uk) joined #forth 00:39:17 --- quit: martinhex (Disconnected by services) 00:39:18 --- nick: martin_hex -> martinhex 01:11:22 --- quit: ygrek (Ping timeout: 245 seconds) 02:28:50 --- join: SunTzu (1000@c-68-56-204-104.hsd1.fl.comcast.net) joined #forth 02:29:05 does anyone here use jonesForth? 02:33:30 Forget this shit. 02:34:12 does anyone here use jonesForth? 02:34:18 No. 02:34:28 Nobody in his right mind will use this shit. 02:34:46 then stop talking and let someone else respond 02:35:17 Good luck then. 02:35:30 your scoffage is NOT appreciated 02:35:36 cease hating 02:35:58 You may not appreciate it, but this is fact: jonesForth is shit. 02:36:23 It is hardly Forth in fact. 02:36:45 you lack imagination 02:37:00 and, when you've seen one forth 02:37:13 I've seen enough of them. 02:37:23 you've seen one. 02:37:31 you canot compare them to each other 02:38:23 If you start using arbitrary words instead of regular "I", "you", "can", "see" etc, 02:38:30 can you call that English? 02:39:32 That's what jonesForth did basically. 02:40:17 it has been fixed but i'm not concerned with those idiosyncracies for my project 02:41:11 What for are you going to use it? 02:41:33 i'm not prepared to tell yet 03:03:51 --- quit: scj (Ping timeout: 272 seconds) 03:04:05 --- join: scj (syljo361@boneym.mtveurope.org) joined #forth 04:08:42 --- quit: dinya_ (Ping timeout: 240 seconds) 05:39:53 --- quit: gogonkt (Ping timeout: 240 seconds) 05:41:48 --- join: gogonkt (~info@183.27.213.56) joined #forth 06:48:52 --- quit: segher (Ping timeout: 245 seconds) 06:52:46 --- join: segher (~segher@84-105-60-153.cable.quicknet.nl) joined #forth 07:46:05 --- nick: DavidC99|x -> DavidC99 07:53:09 --- join: martin_hex (~mjc@93-97-29-243.zone5.bethere.co.uk) joined #forth 07:53:10 --- quit: martinhex (Read error: Connection reset by peer) 07:53:12 --- nick: martin_hex -> martinhex 07:57:58 --- quit: DavidC99 (Quit: Signing off...) 08:06:00 --- join: dom96 (dom96@unaffiliated/dom96) joined #forth 08:27:29 anyone awake? 08:27:38 well, nm. i'll just mumble 08:28:06 compile-time, interpret-time, run-time. 08:28:16 interp-time, run-time 08:28:34 Airforce never sleeps. 08:28:35 scantext, (read) runtime 08:29:02 read, scan, run 08:29:58 i cannot see the difference tween macro-time, interpret, and runtimes 08:30:20 they're all words, what they do when Interpreted is up to the coder 08:30:49 It isn't clear what you're talking about. 08:31:04 if a macro (i'm thinking of lispy type) then they mung what has been compiled or is to be compiled 08:31:13 (that's why it's called mumbling) 08:31:31 an inner interp just runs lists[] 08:31:54 the outter parses, finds, calls interp 08:32:04 There're no macros in (more or less traditional) Forth. 08:32:16 yea, i want to change that 08:32:23 What for? 08:32:27 flexibility 08:32:34 bc it cn be done 08:32:37 can 08:32:54 You have compiling words, which are more like hygienic macros. 08:33:06 have to define what a macro is or can do in a forth tho 08:33:10 ok 08:33:43 it's just another DSL 08:35:32 hey 08:35:50 jes? 08:36:26 compile-time words could be considered macros 08:36:58 --- join: chturne (~quassel@host217-42-5-60.range217-42.btcentralplus.com) joined #forth 08:37:10 --- part: chturne left #forth 08:37:19 lol tagline 08:43:59 You must mean "compile-only" words, but they don't exist everywhere. 08:44:33 And they don't exist in jonesForth almost for sure. 08:46:08 i think i'm developing a forth that is stateless 08:46:15 yea 08:51:40 So do that then. 08:51:49 nods 08:51:56 that's what i'm pondering now 08:52:00 I am pretty sure it would be entirely useless though. 08:52:05 why? 08:52:34 Why would you expect otherwise? 08:52:52 that's not a supportive response to "entirely useless" 08:53:01 pls write a useful thought or criticsim 08:53:29 input is welcome, baseless statements are not. 08:53:48 Because all you will have is a macro assembler. 08:53:50 If you don't understand base, it doesn't make statement baseless. 08:53:51 At best. 08:54:16 that wouldnt be useless at all: perhaps not an intended outcome, but not useless 08:54:27 The entire thing that makes forth interesting in my opinion is the fact that you can manipulate the compiler. 08:54:37 symtab lookup is Find; and run. 08:54:43 that is all that every Forth does. 08:54:55 and compiling-translation 08:55:04 Mmmm, no. 08:55:08 why? 08:55:35 manipulation is part and parcel 08:56:11 Well, the fact that you can control the compiler from source is rather important and what makes it a powerful tool for making a DSL. 08:56:26 yes 08:56:56 but that doesnt explain why your reponses are contrary to what i've written 08:57:09 Say the compiler didn't have comments, and you wanted to add comments, the ability to define the ( word is rather impressive. 08:57:16 ok 08:57:25 i'm not against any of those things. 08:58:01 but why should "contrived" *-times be implemented and specified except for one learning what the whole does? 08:58:14 where * is compile, interpret or run 08:59:05 in implementation, there is no difference between compile-, interpret- and run-time; a word is parsed from input, found, run. 08:59:24 There's difference. 08:59:28 why? 08:59:40 E.g. "+" has several meanings. 08:59:47 It can be operation or operation name. 08:59:54 tht's context-sensitive 08:59:55 Those are two distinct things. 09:00:08 What is "context"? 09:00:18 which can be specified by fig-forth style vocabulary tree 09:00:32 an actual tree with branches of lexicons 09:00:41 How do you distinguish between these two cases? 09:01:12 I suppose SunTzu wants to implement an entire stack-based language in the boot strap rather than use meta-circlarity to do it. Which is fine... Just not forth. 09:01:13 i'm thinking of how a $PATH or oop style parentage could answer that 09:01:18 Do you prefix all words with "next-is-noun" and "next-is-verb"? 09:01:32 i'm not sure yet 09:02:16 i'd rather build a minimal kernel.com and then compile the rest and then uncore() 09:02:21 So, you don't have anything except some vague idea and 09:02:21 start blaming everyone around for "baseless statements." Nice. 09:02:29 who's blaming? 09:02:36 so far only you two have 09:02:43 input is welcome, baseless statements are not. 09:02:49 [11:52] input is welcome, baseless statements are not. 09:02:52 You started it. 09:02:54 HEh, ASau beat me to it. 09:03:05 it means that I require substance in responses. 09:03:08 it's not blame per se 09:03:16 you two are such a trip 09:03:24 your help is barely minimal 09:03:39 Asau disagree on mostly everything involving technology. :o 09:03:45 It's up to you to understand it. 09:03:45 i know 09:03:47 Asau and I rather. 09:05:27 If you write words you don't understand well, others may understand them better than you. 09:05:47 i havent written incomprehensible 09:05:59 "Stateless" has particular meaning in Forth context. 09:06:06 Ugh, verilog is frustrating. I think I will need to write a preprocessor for it... 09:06:08 i know what it means 09:06:12 Unless there already is one. 09:06:15 * Deformative searches. 09:06:30 m4 09:06:43 hot Vargas girls on PBS 09:06:46 lol 09:08:02 --- part: SunTzu left #forth 09:08:28 ASau: Well, the problem is that I find myself using the same wires across many modules. In each of these modules I need to rewrite out the declarations, it would be nice to have the equivalent of a "struct" from C. 09:08:48 That way I can just pass them all as a large bus, and still be able to access them by name. 09:09:07 I am sure it can be done with m4 somehow, but probably much more complex than it needs to be. 09:09:17 Or I can just live in copy/paste hell. 09:09:44 Having 9 copies of like 27 wires that I need to change every time I make a design change. 09:10:32 I cannot believe verilog has been around for almost 20 years and no one decided "hey! I am stick of rewriting wire names over and over!" 09:10:41 Maybe I am doing it wrong. 09:11:43 If cpp fits, use it. 09:11:54 It's simpler than m4 anyway. 09:12:45 cpp doesn't fit. 09:13:02 It isn't really something a preprocessor should be doing, it should be a language feature. 09:13:07 It is like "struct" in C. 09:13:13 Well... 09:13:28 Generate verilog with something then. 09:13:31 Like Lisp. 09:13:44 Heh, maybe. ^^ 09:14:05 I will be frustrated to have to add an extra step to my synthesis procedure though. 09:14:10 No matter what I do, I lose. 09:14:15 make handles that. 09:14:36 You have loads of tools around you. 09:14:43 Yes, they're not written in Forth. 09:14:48 So worse to Forth. 09:18:26 Heh. 10:17:52 --- join: ygrek (debian-tor@gateway/tor-sasl/ygrek) joined #forth 10:33:49 ASau: Lisp -> HDLs is actually not a bad idea. 10:35:46 I hope that I'll get pforth v. 27 by the end of week. 10:36:00 Alright, next week. 11:04:42 --- join: qFox (~C00K13S@5356B263.cable.casema.nl) joined #forth 11:25:10 --- join: kar8nga (~kar8nga@78.104.80.94) joined #forth 11:59:31 --- join: fantazo (~fantazo@178-191-164-1.adsl.highway.telekom.at) joined #forth 12:35:21 --- quit: i__ (Quit: leaving) 12:43:57 --- join: gogonkt_ (~info@183.27.213.56) joined #forth 12:47:34 --- quit: mathrick (Excess Flood) 12:47:40 --- quit: gogonkt (Remote host closed the connection) 12:48:03 --- join: mathrick (~mathrick@users177.kollegienet.dk) joined #forth 14:20:06 --- quit: kar8nga (Remote host closed the connection) 14:27:37 --- quit: ygrek (Ping timeout: 245 seconds) 14:31:27 --- quit: qFox (Read error: Connection reset by peer) 15:22:12 --- quit: scj (Ping timeout: 245 seconds) 15:29:14 --- join: scj (syljo361@boneym.mtveurope.org) joined #forth 17:39:08 --- join: fantazo_ (~fantazo@178-191-166-60.adsl.highway.telekom.at) joined #forth 17:42:11 --- quit: fantazo (Ping timeout: 240 seconds) 18:14:11 --- quit: scj (Ping timeout: 240 seconds) 18:15:59 --- join: scj (syljo361@boneym.mtveurope.org) joined #forth 18:27:30 --- join: tgunr (~tgunr@cust-66-249-166-11.static.o1.com) joined #forth 18:31:21 --- quit: tgunr_ (Ping timeout: 265 seconds) 18:36:18 --- quit: tgunr (Remote host closed the connection) 18:36:50 --- join: tgunr (~tgunr@cust-66-249-166-11.static.o1.com) joined #forth 18:44:24 --- quit: tgunr (Read error: Connection reset by peer) 20:34:10 --- join: DavidC99 (~DavidC99@bas2-windsor12-1128533178.dsl.bell.ca) joined #forth 21:36:42 --- quit: crc (Ping timeout: 265 seconds) 21:37:20 --- join: crc (~charlesch@184.77.185.20) joined #forth 22:02:58 --- quit: fantazo_ (Remote host closed the connection) 23:23:10 --- join: kar8nga (~kar8nga@i-254.vc-graz.ac.at) joined #forth 23:25:23 --- quit: DavidC99 (Quit: Signing off...) 23:59:59 --- log: ended forth/10.09.02