reepca has quit [Read error: Connection reset by peer]
xek has joined #forth
dddddd has quit [Ping timeout: 258 seconds]
dys has joined #forth
TCZ has joined #forth
Keshl_ has quit [Quit: Konversation terminated!]
Keshl has joined #forth
Keshl is now known as Keshi
Keshi is now known as Keshl
TCZ has quit [Quit: Leaving]
TCZ has joined #forth
TCZ has quit [Quit: Leaving]
jedb_ has joined #forth
jedb has quit [Ping timeout: 256 seconds]
dave0 has quit [Quit: dave's not here]
dys has quit [Ping timeout: 260 seconds]
dddddd has joined #forth
clemens3 has joined #forth
<clemens3>
hi, what is the most popular forth on linux, is it gforth?
<crest>
gforth
deesix_ has joined #forth
dddddd_ has joined #forth
dddddd__ has joined #forth
deesix has quit [Ping timeout: 258 seconds]
dddddd has quit [Ping timeout: 260 seconds]
dddddd__ is now known as dddddd
dddddd_ has quit [Ping timeout: 246 seconds]
deesix_ has quit [Ping timeout: 264 seconds]
dddddd has quit [Ping timeout: 256 seconds]
dddddd has joined #forth
deesix has joined #forth
<clemens3>
crest: thanks.. does gforth kinda need gforth to compile itself?
<clemens3>
that would be .. kinda.. why not bootstrap instead..
<clemens3>
seems that was a short gforth journey
<crest>
clemens3: iirc it compiles a minimal forth system and uses it to bootstrap
<clemens3>
hope so, just it doesn't tell me yet how..
dys has joined #forth
<clemens3>
ah, it does
<clemens3>
need swig and the -forth
<clemens3>
well, well, hope is up
<crest>
clemens3: most linux distros should contain a ready to use gforth package
<clemens3>
well, mine doesn't
<clemens3>
but swig sounds fair
<MrMobius>
interesting
<MrMobius>
the thing I always find so ironic is when someone makes a new Forth because C is horrible then proceed to implement it in C
<MrMobius>
I always wondered why those people don't use another Forth to create their Forth
<jackdaniel>
(save-forth-and-die)
<boru>
I suspect it's something to do with the pervasiveness of register machines, and them not wanting to write swathes of assembly. Besides that, Forth compilers are comparably easy to write, and it's more fun, I guess. At least, ime.
<crest>
clemens3: because they use C as portable assembly
<clemens3>
well, if forth doesn't like c, fine, just base it on assembler for a minimal forth etc.
<clemens3>
or don't support linux or unix
<clemens3>
seems my swig doesn't offer --with-forth..
<clemens3>
so seems i also have to write my own forth..
<presiden>
always
TCZ has joined #forth
X-Scale has quit [Ping timeout: 240 seconds]
jedb_ has quit [Remote host closed the connection]
jedb has joined #forth
TCZ has quit [Quit: Leaving]
jedb has quit [Remote host closed the connection]
jedb has joined #forth
X-Scale has joined #forth
Croran has quit [Ping timeout: 260 seconds]
jedb has quit [Remote host closed the connection]
jedb has joined #forth
jedb has quit [Remote host closed the connection]
jedb has joined #forth
xek has quit [Ping timeout: 260 seconds]
TCZ has joined #forth
Zarutian_HTC1 is now known as Zarutian_HTC
jedb has quit [Ping timeout: 246 seconds]
Zarutian_HTC has quit [Quit: Bye]
TCZ has quit [Quit: Leaving]
dys has quit [Ping timeout: 244 seconds]
clemens3 has quit [Quit: WeeChat 2.7]
dys has joined #forth
jsoft has quit [Ping timeout: 260 seconds]
Zarutian_HTC has joined #forth
reepca` has quit [Ping timeout: 240 seconds]
reepca has joined #forth
crab1 has joined #forth
<crab1>
What's up #forth
gravicappa has quit [Ping timeout: 264 seconds]
<crest>
tabemann: did you do anything to implement ack/nak in swdcom for zeptoforth?
crab1 has quit [Quit: Connection closed]
jsoft has joined #forth
cantstanya has quit [Remote host closed the connection]