00:00:00 --- log: started retro/06.10.17
02:56:41 --- join: Cheery (n=Cheery@a81-197-19-23.elisa-laajakaista.fi) joined #retro
05:22:54 --- join: timlarson_ (n=timlarso@65.116.199.19) joined #retro
05:58:42 --- quit: neceve (Read error: 145 (Connection timed out))
06:16:24 --- join: Ray_work (n=Raystm2@199.227.227.26) joined #retro
08:08:59 --- join: virl (n=virl@chello062178085149.1.12.vie.surfer.at) joined #retro
08:53:46 --- quit: nighty (Remote closed the connection)
08:54:48 --- join: nighty (n=nighty@66-163-28-100.ip.tor.radiant.net) joined #retro
10:44:04 --- join: neceve (n=claudiu@unaffiliated/neceve) joined #retro
10:56:49 --- join: rabbitwhite (n=Miranda@136.160.196.114) joined #retro
10:57:29 --- quit: rabbitwhite ()
11:34:59 --- join: erider (n=erider@unaffiliated/erider) joined #retro
11:35:07 <erider> hi all 
13:42:05 --- quit: timlarson_ ("Leaving")
14:03:59 --- quit: Ray_work (Read error: 131 (Connection reset by peer))
16:01:30 --- quit: Cheery ("Download Gaim: http://gaim.sourceforge.net/")
16:02:47 <Raystm2> Good evening.
16:12:02 --- join: snoopy_1711 (i=snoopy_1@dslb-084-058-128-168.pools.arcor-ip.net) joined #retro
16:16:18 --- quit: Snoopy42 (Connection timed out)
16:16:42 --- nick: snoopy_1711 -> Snoopy42
16:29:43 --- join: snoopy_1711 (i=snoopy_1@dslb-084-058-142-159.pools.arcor-ip.net) joined #retro
16:30:20 --- quit: Snoopy42 (Nick collision from services.)
16:30:46 --- nick: snoopy_1711 -> Snoopy42
16:32:41 <lukeparrish> http://retroforth.net/paste/?id=225
16:32:49 <lukeparrish> which commenting style is cooler?
16:48:22 <erider> lukeparrish: is section a retro notation for a block of code 
16:49:21 <lukeparrish> yeah. I think Quartus came up with it when writing the ans layer, and it is integrated into RxForth.
16:51:53 <Raystm2> It would look somewhat better if all the \ were lined up... I suppose.
16:52:23 <Raystm2> those things a a tad hard to see in the code.
16:53:59 <lukeparrish> then there's the idea of integrating it as part of :
16:54:41 <erider> lukeparrish: is the feature in gforth?
16:55:02 <lukeparrish> the section feature?
16:56:08 <erider> yes
16:56:22 <lukeparrish> I'm not sure. could be.
16:56:34 <erider> hmm ok 
17:03:56 <Raystm2> knowing Quartus, and not looking it up for myself, it may even be standard or in an extention of the standard.
18:17:17 --- quit: erider ("I don't sleep because sleep is the cousin of death!")
19:04:26 <Quartus> It's not Standard. Just a really simple method of keeping the namespace uncluttered.
19:04:50 <lukeparrish> I like it.
19:07:47 <Quartus> It's inflexible, as it allows only one private and one public division in each section.  The private parts of sections cannot be accessed later by any mechanism.  Also, they cannot nest.
19:15:07 <lukeparrish> seems like nesting could be added, similarly to loc:
19:16:02 <Quartus> I recommend a module <name>  private:  public:  end-module   wordset, also with  expose-module <name>.  That's nestable, you can switch back and forth between public: and private: within a module, and it nests.
19:16:36 <lukeparrish> sounds reasonable
19:20:40 <Quartus> I built section:/;section just for use within the ANS layer for retroforth, but crc liked it and built it into the kernel.  It wasn't my intention.  I think it's too limited for general use, though it is more flexible than loc:.
20:05:52 <Quartus> For a single-wordlist system, it's simple to implement, though, and a step up over loc:, so I guess it makes a certain sense.  I would rather see multiple wordlists built into rf; they're very simple to do.
20:06:06 <Quartus> Then module/end-module can be layered on top, again very simply.
20:06:34 <lukeparrish> cool
20:07:18 <lukeparrish> almost got a module/end-module coded
20:07:18 <Quartus> I have one in standard Forth.
20:07:18 <Quartus> It's with the retro-ans stuff.
20:08:25 <lukeparrish> neat
20:08:50 <Quartus> Actually that's not entirely portable, but it works fine over the ans layer in rf.
20:08:59 <Quartus> It can be done entirely portably.
20:11:47 <Quartus> The nesting means you can include a file inside a private: section of a module, and the public words of that copy of the module become private to the current module.  This means you can load more than one copy of a given module, and make changes to its prerequisites or behaviour,which is sometimes handy.
20:17:42 --- join: Quartus_ (n=Quartus_@209.167.5.1) joined #retro
20:26:00 <lukeparrish> here we go: http://retroforth.net/paste/?id=226
20:28:25 <Quartus_> does that allow you to go back and forth between public: and private: in a module? And do modules nest? Also, I think you mean : foo test2... ;
20:28:40 <lukeparrish> whups, yeah
20:29:16 <lukeparrish> hmm. I don't know if it lets you go back and forth.
20:30:03 <Quartus_> iit's not at all easy to do that without having wordlists. So it offers little over sectiom:/;section.
20:30:33 <Quartus_> also section: doesn't take any dataspace per section.
20:30:43 <lukeparrish> true
20:31:06 <lukeparrish> this is basically just an expose-able section
20:31:25 <Quartus_> like in section:.
20:32:21 <lukeparrish> ah, ok
20:32:58 * lukeparrish is getting tired, must be time for bed
20:33:00 <Quartus_> I went through all this when going with section: in the ans module.
20:33:06 <Quartus_> heh
20:33:10 <lukeparrish> :)
22:09:22 <virl> cal
22:09:31 --- quit: virl ("Verlassend")
23:59:59 --- log: ended retro/06.10.17