On Fri, Feb 24, 2023, at 12:29 PM, farfadet10@gmx.fr wrote:
>> Copy-pasting is so barbaric :) you could have achieved the same with /.../
>
> oh, thanks, I'll replace it with this code instead...
>
> You can imagine I've tried some other code but I didn't have the right
> syntax...
>
> for example:
>
> * : do doer immediate does> for2 ; 
>
> which was wrong.
>

On Fri, Feb 24, 2023, at 12:18 PM, farfadet10@gmx.fr wrote:
> Well done, it's impressive to see this, it looks promising...
>
>
> In console mode (from my xterm), I got a "Invalid I/O " so I guess we 
> must try the ged 
> editor from the qemu vm, and indeed it's working this way, but I'm 
> using an AZERTY 
> keyboard so it's a p.i.t.a. to type all this in qwerty mode. Do you how 
> if there's 
> an easy way to change the layout. I've tried " -k fr" as option for 
> qemu but I suppose 
> if the OS doesn't support this it won't work. 
>

On Fri, Feb 24, 2023, at 11:52 AM, Virgil Dupras wrote:
> On Fri, Feb 24, 2023, at 11:42 AM, farfadet10@gmx.fr wrote:
>> Ok, so I guess creating a specific file with code for ANS is the way to 
>> go. I don't think I could do it myself, but I'll have a look anyway... 
>> it can be an interesting challenge...
>>
>>> but I've recently added generic iterators to Dusk and it now has a functional equivalent to DO .. LOOP, but it's "for2 .. next" instead. See doc/iter for details.
>>
>> yes, it works, if I type 
>>
>> : foo 1 11 for2 5 i  * . spc> next ;
>>
>>
>> The doc also said "for2" takes 2 arguments, a "high" number and then a 

On Fri, Feb 24, 2023, at 11:42 AM, farfadet10@gmx.fr wrote:
> Ok, so I guess creating a specific file with code for ANS is the way to 
> go. I don't think I could do it myself, but I'll have a look anyway... 
> it can be an interesting challenge...
>
>> but I've recently added generic iterators to Dusk and it now has a functional equivalent to DO .. LOOP, but it's "for2 .. next" instead. See doc/iter for details.
>
> yes, it works, if I type 
>
> : foo 1 11 for2 5 i  * . spc> next ;
>
>
> The doc also said "for2" takes 2 arguments, a "high" number and then a 
> "low" number and counts

Hello all,

I've just recorded a screencast demoing DuskCC and its editor. I hope it helps
quickly showing what makes Dusk interesting.

https://vimeo.com/800710912

I'm not very good at this, but it's better than nothing I guess...

Regards,
Virgil

On Wed, Feb 15, 2023, at 8:48 AM, Rett Berg wrote:
>> this email is replicated because I'm getting errors that my email "contains
>> HTML" from mailer@lists.sr.ht. Is there anyone that didn't receive my last
>> email? This one is sent in plaintext mode.

Yeah, sourcehut's mailing list is picky and I regret having chosen it for Dusk.
Drew picked a fight with gmail and it's a noble fight, but I don't particularly
care about "~" and "/" support by MTAs. Nevertheless, I end up with the fallout
(messy communications with anyone using gmail).

I'm contemplating the idea of merging Collapse OS and Dusk mailing lists (to
discuss broad ideas behind COS and Dusk, because they're mostly the same) and
create a new "dusk-dev" list (not on sourcehut, using the same technique I use
for Collapse OS ML) for Dusk development (to avoid spamming COS subscribers

On Sun, Feb 12, 2023, at 10:21 AM, farfadet10@gmx.fr wrote:
> Hello,
>
> I'm in no way an expert in the Forth langage. I've just begun to learn 
> it and it pleases me so far. Because of my lack of expertise in this 
> field, maybe I'm not the ideal target for DuskOS, but I'd like to try 
> anyway.

Dusk's documentation begins where Starting Forth ends. If you're interested in
diving into Dusk OS, I guess that makes you a target :)

> I was wondering about the inclusion of ANS forth implementation into 
> DuskOS. I don't know much about Forth, but I already know it's a "touchy" 
> subject, and some people just believe forth shouldn't be standardised 

On Thu, Feb 9, 2023, at 11:11 AM, Lucas Chaloyard wrote:
>> This way of organizing the code is the simplest way I found. If you can think of
>> a simpler one, I'm all ears!
>> 
>> The VMOp API is to decouple pgen from the backend. Again, if you can think of a
>> simpler way, I'm very interested in your proposition.
>
> I don't have any for now, but I was thinking about trying to think of
> one, I wanted to know more about your opinion on this before.
>
> I'll let you know if I have any interesting ideas !
>
>> DuskCC doesn't maintain an AST. If you dive into the git history, you'll see
>> that it used to, but since then, I've transformed it into a single pass which

On Thu, Feb 9, 2023, at 9:15 AM, Lucas Chaloyard wrote:
> Hello Virgil,
>
> I've been quite busy lately and I didn't have the chance to dive into
> the accelerators concept for the CollapseOS VM "stage.fs" mechanism, but
> I'll try to get back to it.
>
> In the meantime, I've been diving deep into Dusk C Compiler, and I have
> several questions to ask, if you don't mind:
>
> 1. Do you plan to add the possibility to compile code into a "binary
> executable" ?
>
> My thought is based on the idea that DuskCC is capable to write code

Hello all,

I've just pushed a new feature to Dusk: iterators (see doc/iter). I'm extremely
happy of how it turned out and as I'm briefly looking around, I'm beginning to
think that I've been really innovative with that one.

GForth only seems to have traditional looping. RetroForth, which I don't know
much, has "for-each" which could be seen as something close to my iterators, but
the documentation says "RETRO also provides `for-each` combinators for various
data structures.", which makes me think that it's not a generic mechanism. A
quick search of other forths on github gave me nothing.

So, the goal of this message is to poke people who would know more than me about
the Forth ecosystem and tell me if any other Forth has something remotely as