proteus-guy has quit [Remote host closed the connection]
proteus-guy has joined #forth
proteusguy has joined #forth
elioat has quit [Remote host closed the connection]
deesix has quit [Ping timeout: 256 seconds]
crab1 has joined #forth
<crab1>
greetings, #forth
yunfan has quit [Quit: WeeChat 1.9.1]
xek_ has joined #forth
jsoft has joined #forth
xek_ has quit [Ping timeout: 265 seconds]
Croran has quit [Quit: No Ping reply in 180 seconds.]
Croran has joined #forth
xek_ has joined #forth
xek_ has quit [Ping timeout: 256 seconds]
<veltas>
GREETINGS crab1
jedb_ has joined #forth
jedb has quit [Ping timeout: 264 seconds]
<crab1>
How are my fellow forthers?
<proteusguy>
doing great... building new forths. ;-) what else would a forther be doing?
<crab1>
what sorts of forths are we building today?
<proteusguy>
ActorForth - strong type system which I then build a forth-like language on top of it. intended to build crypto-contracts with it.
<crab1>
I've still not made a forth to completion.
<proteusguy>
this one isn't complete yet - but it's getting closer.
<crab1>
I always end up angry at whatever architecture I'm building it on and quit
<proteusguy>
crab1, haha that's understandable. but having something working is of value no matter what.
<crab1>
it undoubtedly is, and it's something I fail to value enough
<crab1>
because here I sit, usually writing forth on paper and never executing anything whatsoever :)
<proteusguy>
keeping focus and just getting what you need done is difficult since you've always got new ideas on something else you could do with it. just expect to re-write the thing a few times, at least big chunks of it.
<proteusguy>
I always have example code for useful things that I want to run in my forth. Then I build just enough forth to execute that.
<crab1>
I've not honed in tightly enough on what I want
<proteusguy>
well there you have it. ;-)
<proteusguy>
crab1, what environment(s) are you targeting?
<crab1>
either AArch64 or Amd64
catern has quit [*.net *.split]
APic has quit [*.net *.split]
<crab1>
I want to use on one of my laptops, I have an arm and an intel lappy
<proteusguy>
oh cool. you writing in asm64 or C/C++ or something completely different? baremetal or under an OS?
<crab1>
Probably has to be under an OS since the world is telling me that getting things to boot on my ARM laptop is a PITA
<crab1>
I lean toward asm, another option is ziglang.org
<crab1>
zig is pretty nice to write in, but I still lean toward asm
<crab1>
Hell what I want at the end of the day is almost just a forth style macro assembler
APic has joined #forth
<proteusguy>
never heard of ziglang before. interesting.
<crab1>
zig is almost like 'C but everything works how you expect it to'
<crab1>
and it has decent error messages and good options for writings tests and such
<proteusguy>
looks pretty cool like a better classic 'C', a platform independent assembly language.
catern has joined #forth
<crab1>
I at least get less annoyed with Zig than I do C
<proteusguy>
my canonical implementation of ActorForth is using python. It will eventually be self hosted. Haven't decided what underlying target platform that will assume. Eventually I want to make an FGPA that interprets its primitives natively.
<crab1>
mm FPGAs are nice
<proteusguy>
ideal if you need a stack based processor...
<proteusguy>
What asm64 I've written I've done with nasm. Much prefer it to the gnu asm syntax.
<crab1>
there is also yasm
<cmtptr>
am i the one person on earth who doesn't mind at&t syntax
<proteusguy>
cmtptr, perhaps the "last" ;-)
<crab1>
Personally, I find all of the standard asm syntaxes unwieldly
<proteusguy>
crab1, I'd heard of yasm but never tried it.
<cmtptr>
maybr it's just gnu stockholm syndrome
<proteusguy>
crab1, agreed which is why I prefer writing my own asm in forth but the x86 CPU is a monster. Not something nice like 6809 or 68k.
<crab1>
but ATT is really no worse than Intel or any others in my book