00:00:00 --- log: started forth/21.02.21 01:11:36 MrMobius: There is a valid reason but there are workarounds (assuming middle LOOP was meant to be LEAVE) 01:13:07 Like just wrap end part in an IF..THEN, or use BEGIN..WHILE..REPEAT etc instead 01:14:47 Yeah a LEAVE stack is a way I considered, it would have to be pretty much what you said, I can't think of another way. I have opted for three items on the return stack because it seems like the simplest overall solution 01:15:30 ANd the overhead is minimal and doesn't affect the amortised loop overhead (apart from using 2 bytes more return stack, and 1 byte more with plain DO) 01:33:04 --- quit: dave0 (Quit: dave's not here) 02:36:40 --- nick: jedb__ -> jedb 02:59:27 --- quit: iyzsong (Quit: ZNC 1.7.5 - https://znc.in) 02:59:50 --- join: iyzsong joined #forth 03:09:32 --- quit: yunfan (Quit: WeeChat 2.9) 03:39:31 --- join: yunfan joined #forth 03:57:09 veltas i did mean LOOP twice there 04:57:52 --- join: f-a joined #forth 05:05:52 --- quit: sts-q (Quit: ) 05:06:19 --- join: sts-q joined #forth 05:07:24 --- quit: sts-q (Client Quit) 05:07:49 --- join: sts-q joined #forth 05:28:57 Oh okay I don't understand then 07:20:56 --- join: elioat joined #forth 07:24:10 --- nick: f-a -> f-menagr-a-mo 07:25:17 what VCS do forth people use, if any? 07:25:22 (don’t know if I have already asked) 07:29:47 VCS? 07:30:01 version control system 07:30:07 version control system proteusguy, something like git yeah 07:30:12 I use git but I hate it 07:30:21 it's just the most commonly supported and therefore the de facto default 07:30:32 I see 07:32:50 --- nick: f-menagr-a-mo -> f-a 07:34:38 I'm interested in fossil, because I have some friends who have started using it and prefer it over git 07:35:04 I use darcs, but only for personal projects 07:35:46 I might move a project I'm working on rn into fossil 07:35:47 just...because 07:35:49 to check it out 07:35:58 sadly I dont' have a server to host public fossil projects on 07:36:34 not mercurial? 07:36:54 mercurial doesn't seem all that different to git to me? Honestly idk stuff about VCSs 07:36:57 I also don't have mercurial hosting 07:37:06 (rn I host my stuff on tildegit, which is a gitea instance) 07:37:20 srht exists and is good I guess but also paid 07:48:56 --- quit: elioat (Quit: elioat) 07:56:11 https://chiselapp.com/ has fossil hosting 07:58:05 cool 08:24:25 --- quit: _whitelogger (Remote host closed the connection) 08:27:22 --- join: _whitelogger joined #forth 08:57:01 I am interested in fossil but idk really about how much I gain from moving to fossil, it just seems to be simpler than git while also integrating the stuff that is currently messy with git (like issues over multiple hosts, etc) 08:57:58 --- quit: f-a (Ping timeout: 265 seconds) 08:59:25 --- join: f-a joined #forth 09:05:57 f-a: git or just .tar.gz snapshots 09:06:29 My VCS requirements are extremely basic personally, I use perforce and git at work and I prefer git there. 09:07:24 http://www.ariis.it/link/t/gb.png 09:07:39 there is a forth ×-compiler for gb, apparently 09:07:42 I *might* make something 09:11:23 Go for it, only way to learn it properly really 09:13:08 there is a forth for the gameboy 09:14:06 nihilazo: a forth *interpreter*? 09:14:17 I am using https://gbforth.org/ 09:14:31 but has some annoying limitations https://gbforth.org/limitations.html 09:14:41 (no `create` at runtime etc.) 09:16:16 oh yeah, that's gbforth 09:16:21 it's the only one I know 09:31:04 --- quit: gravicappa (Ping timeout: 260 seconds) 09:31:58 --- join: gravicappa joined #forth 09:33:52 With 8KB RAM, and assumption that any game will have essentially all code in ROM, and no keyboard, it is not surprising to me nobody has made a full interpreter forth for gameboy 09:33:57 As far as I know anyway 09:34:19 yeah, a full interpreter doesn't make too much sense 09:34:24 But there's no reason you can't make one, I think it would be quite a cool thing on a real gameboy if you had a way of writing the ROM 09:34:24 a compiler is cool though 09:34:38 you could put writable memory inside a cartridge 09:34:44 that's what, eg. LSDJ does for song memory 09:34:57 (and some games for saves, but it was surprisingly a little rare) 09:35:05 Or you could just limit to the 8KB RAM, you could do a lot with that in a tokenised forth 09:35:31 LSDJ has the main program in ROM but also has storage in the cartridge the user can write and read from 09:35:47 so did pokemon games (although they used a battery-backed RAM which isn't a very robust solution) 09:36:05 That is definitely the way to go, some kind of nv storage 09:36:33 well you cannot use `create … does>`, which is a bit of a pity 09:37:03 and a forth interpreter is likely to be running from a flash cartridge 09:37:14 in which case you can use the insanely huge flash memories that those have lol 09:37:20 Yes 09:37:36 my EMS cartridge (which everybody agrees is pretty terrible, it's like the worst GB flashcard) has 32M storage 09:37:39 which is insane for the gameboy 09:39:24 some have even more, I think some of the bennvenn ones have multiple gb of storage 10:29:41 --- quit: mjl (Ping timeout: 272 seconds) 10:30:55 --- join: mjl joined #forth 12:15:10 --- quit: gravicappa (Ping timeout: 256 seconds) 12:39:47 --- join: f-a_ joined #forth 12:40:15 --- quit: f-a (Read error: Connection reset by peer) 12:46:15 --- quit: f-a_ (Quit: leaving) 12:46:31 --- join: f-a joined #forth 12:57:40 --- quit: f-a (Ping timeout: 256 seconds) 12:59:20 --- join: f-a joined #forth 15:24:00 --- join: dave0 joined #forth 15:57:19 --- quit: Keshl (Ping timeout: 264 seconds) 16:21:59 --- join: Keshl joined #forth 16:33:13 --- quit: dave0 (Quit: dave's not here) 16:48:47 --- quit: f-a (Quit: leaving) 17:00:09 --- join: Zarutian_HTC joined #forth 17:14:26 --- join: X-Scale` joined #forth 17:16:07 --- quit: X-Scale (Ping timeout: 240 seconds) 17:16:07 --- nick: X-Scale` -> X-Scale 18:03:07 --- quit: Lord_Nightmare (Quit: ZNC - http://znc.in) 18:07:44 --- join: Lord_Nightmare joined #forth 18:33:50 --- join: boru` joined #forth 18:33:52 --- quit: boru (Disconnected by services) 18:33:55 --- nick: boru` -> boru 19:12:34 --- join: X-Scale` joined #forth 19:14:13 --- quit: X-Scale (Ping timeout: 265 seconds) 19:14:13 --- nick: X-Scale` -> X-Scale 19:18:17 --- join: dave0 joined #forth 20:15:43 --- join: gravicappa joined #forth 20:22:36 --- quit: gravicappa (Ping timeout: 272 seconds) 20:24:49 --- join: gravicappa joined #forth 20:36:40 f-menagr-a-mo: I use Git and it's very nice IMO 20:37:03 though for personal/smaller projects sometimes no VC at all 20:54:26 I use git. I hate it. Never will you find the occasion to use the default parameters to do anything useful. But it's won the market share without question. The best designed one, imho, is mecurial. 20:55:18 --- quit: sts-q (Ping timeout: 240 seconds) 20:55:51 proteusguy: what do you dislike about git? 20:56:41 --- join: sts-q joined #forth 21:07:59 dunno if mercurial has it but one feature I use all the time is git rebase which makes it painless to rewrite history 22:06:35 --- quit: djinni (Ping timeout: 260 seconds) 22:09:48 --- join: proteus-guy joined #forth 22:09:55 --- join: djinni joined #forth 22:26:06 I guess long-term mercurial might have a future as a friendlier frontend to git repos: http://hg-git.github.io/ 22:54:24 --- quit: _whitelogger (Remote host closed the connection) 22:57:21 --- join: _whitelogger joined #forth 23:42:20 --- join: hosewiejacke joined #forth