lispmacs has quit [Remote host closed the connection]
lispmacs has joined #forth
boru` has joined #forth
boru has quit [Disconnected by services]
boru` is now known as boru
proteusguy has joined #forth
Zarutian_HTC has quit [Remote host closed the connection]
Gromboli has quit [Read error: Connection reset by peer]
Zarutian_HTC has joined #forth
actuallybatman has joined #forth
actuallybatman has quit [Quit: leaving]
lispmacs has quit [Remote host closed the connection]
gravicappa has joined #forth
actuallybatman has joined #forth
Zarutian_HTC has quit [Remote host closed the connection]
sts-q has quit [Ping timeout: 272 seconds]
WickedShell has quit [Remote host closed the connection]
dave0 has quit [Quit: dave's not here]
sts-q has joined #forth
wineroots has joined #forth
remexre has quit [Ping timeout: 272 seconds]
remexre has joined #forth
<siraben>
veltas: yeah the formality varies, I have a friend who is using Coq and model checking for VLSI designs and C code for use in a solar car
lispmacs has joined #forth
proteusguy has quit [Ping timeout: 272 seconds]
wineroots has quit [Remote host closed the connection]
wineroots has joined #forth
proteusguy has joined #forth
<veltas>
siraben: Car controller software uses these standards and techniques because they get sued and regulated more. But e.g. military only needs cert if they want to be able to fly through residential areas &c. rather than 'delivering' their aircraft near the field of battle.
<veltas>
And it's worth realising that using even the most sophisticated provers &c. doesn't guarantee the software works, you can still have bugs.
<veltas>
So you still need: good programmers first and foremost, a good process, and then last thing you want is all these tools and standards and people tend to use them based on requirements.
proteus-guy has joined #forth
proteusguy has quit [Read error: Connection reset by peer]
Zarutian_HTC has quit [Remote host closed the connection]
lispmacs has quit [Ping timeout: 240 seconds]
Zarutian_HTC has joined #forth
Zarutian_HTC has quit [Remote host closed the connection]
_whitelogger has joined #forth
gravicappa has joined #forth
<neuro_sys>
What Forth implementation do you use on a PC (if any?) I've been using gforth for learning, but was wondering if there's anything else that I could check.
gravicappa has quit [Ping timeout: 260 seconds]
<inode>
if you are prepared to consider 16-bit DOS programs, F-PC
Zarutian_HTC has joined #forth
dddddd has quit [Quit: dddddd]
<veltas>
neuro_sys: I'm using gforth at the moment, I have tried a couple others, gforth is the least weird one I've seen. I have barely touched the SwiftForth demo and that seems okay
<veltas>
I'm not really sure I understand what the licensing terms of the demo are, or if it's any different from full version
<veltas>
It comes with a really nice manual, and copies of different standards
<veltas>
I think a forth for PC that gets used quite a bit in here is retro because I see crc actually uses it as much as possible, a good benchmark for using it
dddddd has joined #forth
<veltas>
There's also 8th
<neuro_sys>
inode: 16-bit DOS is good/simple, I'll check
<neuro_sys>
Retro forth also seems good
<neuro_sys>
Also for later I'm curious what's used for embedded applications. Maybe they often roll their own Forth.
<veltas>
Mecrisp is used a lot by people who are/were in here
<veltas>
They have a channel on freenode: #mecrisp. There is also #retro