comp.lang.forth

• Thread Index

---

• Re: gforth: SDL/OpenGL Graphics Part I
  • From: Marcel Hendrix
• gforth: SDL/OpenGL Graphics Part I
  • From: Tim Trussell
• Re: Big news from Green Arrays, Inc. (aka Chuck Moore and friends)
  • From: Wayne
• Re: Big news from Green Arrays, Inc. (aka Chuck Moore and friends)
  • From: Wayne
• Re: How should I structure this function?
  • From: Stephen Pelc
• Re: How should I structure this function?
  • From: Bernd Paysan
• Re: How should I structure this function?
  • From: Bruce McFarling
• Re: How should I structure this function?
  • From: Celime
• Re: How should I structure this function?
  • From: Bruce McFarling
• FREE Animations you can e-mail
  • From: fitz
• Re: How should I structure this function?
  • From: Aleksej Saushev
• Re: How should I structure this function?
  • From: Bruce McFarling
• Re: How should I structure this function?
  • From: Aleksej Saushev
• Re: Troublesome code
  • From: Bruce McFarling
• Re: Resolving overloading
  • From: Bruce McFarling
• Re: slide-rule.4th
  • From: Jerry Avins
• Bitwise 2010 ( IIT Kharagpur ) An Annual Algorithm Intensive Online Programing Contest
  • From: Bitwise 2010 <IIT Kharagpur>
• Re: How should I structure this function?
  • From: Stephen Pelc
• Re: Troublesome code
  • From: Hugh Aguilar
• Re: slide-rule.4th
  • From: Hugh Aguilar
• Re: slide-rule.4th
  • From: Hugh Aguilar
• Re: Resolving overloading
  • From: Bernd Paysan
• Re: Resolving overloading
  • From: Bernd Paysan
• Re: Resolving overloading
  • From: Bruce McFarling
• Re: Resolving overloading
  • From: Bruce McFarling
• Re: Resolving overloading
  • From: Bruce McFarling
• Re: Resolving overloading
  • From: Anton Ertl
• Re: Resolving overloading
  • From: Anton Ertl
• Re: Resolving overloading
  • From: J Thomas
• Re: Resolving overloading
  • From: Bruce McFarling
• Re: Resolving overloading
  • From: Bruce McFarling
• Re: Troublesome code
  • From: Bruce McFarling
• Re: Resolving overloading
  • From: J Thomas
• Re: bug in gforth
  • From: Anton Ertl
• Re: bug in gforth
  • From: Anton Ertl
• Re: Troublesome code
  • From: Coos Haak
• Re: Resolving overloading
  • From: Anton Ertl
• Re: DOES> improvement
  • From: Ed
• Re: Troublesome code
  • From: MarkWills
• Re: slide-rule.4th
  • From: Jerry Avins
• Re: slide-rule.4th
  • From: Jerry Avins
• Re: slide-rule.4th
  • From: Hugh Aguilar
• Re: slide-rule.4th
  • From: Hugh Aguilar
• Re: slide-rule.4th
  • From: Hugh Aguilar
• Re: How should I structure this function?
  • From: Aleksej Saushev
• Re: slide-rule.4th
  • From: Thomas ***in
• Re: Troublesome code
  • From: Stephen Pelc
• Re: slide-rule.4th
  • From: J Thomas
• Re: slide-rule.4th
  • From: Jerry Avins
• Re: Troublesome code
  • From: Hugh Aguilar
• Re: slide-rule.4th
  • From: Hugh Aguilar
• Re: slide-rule.4th
  • From: Hugh Aguilar
• Re: slide-rule.4th
  • From: Hugh Aguilar
• Re: How should I structure this function?
  • From: Hugh Aguilar
• Re: slide-rule.4th
  • From: Jerry Avins
• Re: Troublesome code
  • From: Elizabeth D Rather
• Re: How should I structure this function?
  • From: Coos Haak
• Re: slide-rule.4th
  • From: W. James
• Re: Resolving overloading
  • From: Bruce McFarling
• Re: Troublesome code
  • From: Bruce McFarling
• Re: Resolving overloading
  • From: Bruce McFarling
• Re: Resolving overloading
  • From: Bruce McFarling
• Re: Troublesome code
  • From: Anton Ertl
• Re: Resolving overloading
  • From: Anton Ertl
• Re: Resolving overloading
  • From: Bruce McFarling
• Re: Resolving overloading
  • From: J Thomas
• Re: Resolving overloading
  • From: J Thomas
• Re: Resolving overloading
  • From: J Thomas
• Re: Troublesome code
  • From: Elizabeth D Rather
• Re: Troublesome code
  • From: MarkWills
• Re: Troublesome code
  • From: Elizabeth D Rather
• Re: Resolving overloading
  • From: Elizabeth D Rather
• Re: Resolving overloading
  • From: Bruce McFarling
• Troublesome code
  • From: MarkWills
• Re: Resolving overloading
  • From: Bruce McFarling
• Re: slide-rule.4th
  • From: Jerry Avins
• Re: slide-rule.4th
  • From: Jerry Avins
• Re: Resolving overloading
  • From: J Thomas
• Re: Resolving overloading
  • From: Bruce McFarling
• Re: Resolving overloading
  • From: Bruce McFarling
• Re: Resolving overloading
  • From: J Thomas
• Re: Resolving overloading
  • From: Elizabeth D Rather
• Re: bug in gforth
  • From: Bruce McFarling
• Re: bug in gforth
  • From: Bruce McFarling
• Re: bug in gforth
  • From: Albert van der Horst
• Re: bug in gforth
  • From: Albert van der Horst
• Re: bug in gforth
  • From: Hugh Aguilar
• Re: Resolving overloading
  • From: Bruce McFarling
• Re: slide-rule.4th
  • From: Hugh Aguilar
• Re: DOES> improvement
  • From: Hugh Aguilar
• Re: bug in gforth
  • From: Anton Ertl
• Re: bug in gforth
  • From: Hugh Aguilar
• Re: slide-rule.4th
  • From: Hugh Aguilar
• Re: How should I structure this function?
  • From: Hugh Aguilar
• Re: bug in gforth
  • From: George Hubert
• Re: Philosphical Forth Musing
  • From: Elizabeth D Rather
• Re: How should I structure this function?
  • From: Celime
• Re: How should I structure this function?
  • From: Celime
• Re: bug in gforth
  • From: Anton Ertl
• Re: Philosphical Forth Musing
  • From: Graham Smith
• Re: relative-to-source file names
  • From: Bernd Paysan
• Re: bug in gforth
  • From: Bernd Paysan
• Re: relative-to-source file names
  • From: David Thompson
• Re: Resolving overloading
  • From: J Thomas
• Re: Resolving overloading
  • From: Albert van der Horst
• Re: How should I structure this function?
  • From: Stephen Pelc
• Re: Resolving overloading
  • From: Bruce McFarling
• Re: How should I structure this function?
  • From: CuppoJava
• Re: Resolving overloading
  • From: J Thomas
• Re: How should I structure this function?
  • From: Stephen Pelc
• Re: Resolving overloading
  • From: Stephen Pelc
• Re: bug in gforth
  • From: Coos Haak
• Re: DOES> improvement
  • From: Coos Haak
• Re: slide-rule.4th
  • From: John Passaniti
• Re: DOES> improvement
  • From: Ed
• Re: relative-to-source file names
  • From: Bruce McFarling
• Re: relative-to-source file names
  • From: Bruce McFarling
• Re: How should I structure this function?
  • From: CuppoJava
• Re: Resolving overloading
  • From: Bruce McFarling
• Re: DOES> improvement
  • From: Hugh Aguilar
• Re: Resolving overloading
  • From: Stephen Pelc
• Re: Resolving overloading
  • From: Stephen Pelc
• Re: bug in gforth
  • From: Hugh Aguilar
• Re: relative-to-source file names
  • From: Stephen Pelc
• Re: bug in gforth
  • From: Coos Haak
• Re: bug in gforth
  • From: Coos Haak
• Re: Resolving overloading
  • From: J Thomas
• Re: relative-to-source file names
  • From: Andrew Haley
• Re: bug in gforth
  • From: Anton Ertl
• Re: relative-to-source file names
  • From: Elizabeth D Rather
• bug in gforth
  • From: Hugh Aguilar
• Re: How should I structure this function?
  • From: Hugh Aguilar
• Re: relative-to-source file names
  • From: Elizabeth D Rather
• Re: Resolving overloading
  • From: Elizabeth D Rather
• Re: relative-to-source file names
  • From: Anton Ertl
• Re: Resolving overloading
  • From: Anton Ertl
• Re: relative-to-source file names
  • From: Anton Ertl
• Re: relative-to-source file names
  • From: Andrew Haley
• Re: Resolving overloading
  • From: Anton Ertl
• Re: Resolving overloading
  • From: J Thomas
• Re: RfD - Enhanced local variable syntax, v5b
  • From: Anton Ertl
• Re: Resolving overloading
  • From: Bruce McFarling
• Re: Resolving overloading
  • From: Bruce McFarling
• Re: relative-to-source file names
  • From: Bruce McFarling
• Re: relative-to-source file names
  • From: Bruce McFarling
• Re: relative-to-source file names
  • From: Anton Ertl
• Re: How should I structure this function?
  • From: CuppoJava
• Re: relative-to-source file names
  • From: Bruce McFarling
• Re: relative-to-source file names
  • From: Bruce McFarling
• Re: slide-rule.4th
  • From: Jerry Avins
• Re: relative-to-source file names
  • From: Andrew Haley
• Re: >ORDER ORDER> ORDER@
  • From: Anton Ertl
• Re: Resolving overloading
  • From: J Thomas
• Re: Resolving overloading
  • From: J Thomas
• Re: relative-to-source file names
  • From: Anton Ertl
• Re: relative-to-source file names
  • From: J Thomas
• Re: Resolving overloading
  • From: Andrew Haley
• Re: Resolving overloading
  • From: Bernd Paysan
• Re: Resolving overloading
  • From: Anton Ertl
• Re: relative-to-source file names
  • From: Andrew Haley
• Re: slide-rule.4th
  • From: idknow
• Re: How should I structure this function?
  • From: Celime
• Re: Big news from Green Arrays, Inc. (aka Chuck Moore and friends)
  • From: Ray St. Marie
• Re: How should I structure this function?
  • From: Bruce McFarling
• Re: Philosphical Forth Musing
  • From: MarkWills
• How should I structure this function?
  • From: CuppoJava
• Re: Resolving overloading
  • From: Coos Haak
• Re: DOES> improvement
  • From: Coos Haak
• Re: slide-rule.4th
  • From: Hugh Aguilar
• Re: Resolving overloading
  • From: Stephen Pelc
• Re: Philosphical Forth Musing
  • From: kenney
• Re: Philosphical Forth Musing
  • From: Thomas ***in
• Re: slide-rule.4th
  • From: Richard Owlett
• slide-rule.4th
  • From: Hugh Aguilar
• Re: Resolving overloading
  • From: Bernd Paysan
• Re: DOES> improvement
  • From: Hugh Aguilar
• Re: DOES> improvement
  • From: Hugh Aguilar
• Re: Resolving overloading
  • From: J Thomas
• Re: relative-to-source file names
  • From: Bruce McFarling
• Re: Resolving overloading
  • From: Bruce McFarling
• Re: Resolving overloading
  • From: Bruce McFarling
• Re: Resolving overloading
  • From: Bruce McFarling
• Re: Philosphical Forth Musing
  • From: Jerry Avins
• Re: relative-to-source file names
  • From: Anton Ertl
• Re: relative-to-source file names
  • From: Anton Ertl
• Re: relative-to-source file names
  • From: Anton Ertl
• Re: >ORDER ORDER> ORDER@
  • From: Anton Ertl
• Re: Philosphical Forth Musing
  • From: Marcel Hendrix
• Re: Resolving overloading
  • From: Jerry Avins
• Re: Resolving overloading
  • From: Anton Ertl
• Re: Resolving overloading
  • From: Jerry Avins
• Re: Resolving overloading
  • From: Jerry Avins
• Re: Big news from Green Arrays, Inc. (aka Chuck Moore and friends)
  • From: Mux
• Re: Philosphical Forth Musing
  • From: Celime
• Re: Big news from Green Arrays, Inc. (aka Chuck Moore and friends)
  • From: Dennis
• Re: Philosphical Forth Musing
  • From: Stephen Pelc
• Re: Philosphical Forth Musing
  • From: Celime
• Re: Resolving overloading
  • From: J Thomas
• Re: Resolving overloading
  • From: Thomas ***in
• Re: Resolving overloading
  • From: Anton Ertl
• Re: Resolving overloading
  • From: Andrew Haley
• Re: Philosphical Forth Musing
  • From: ar
• Re: Philosphical Forth Musing
  • From: ar
• Re: Resolving overloading
  • From: Anton Ertl
• Re: Resolving overloading
  • From: Andrew Haley
• Re: Philosphical Forth Musing
  • From: MarkWills
• Re: Philosphical Forth Musing
  • From: Celime
• Re: Philosphical Forth Musing
  • From: John Passaniti
• Re: Philosphical Forth Musing
  • From: John Passaniti
• Re: Philosphical Forth Musing
  • From: Elizabeth D Rather
• Re: Big news from Green Arrays, Inc. (aka Chuck Moore and friends)
  • From: John Passaniti
• Re: Philosphical Forth Musing
  • From: MarkWills
• Re: Philosphical Forth Musing
  • From: John Passaniti
• Re: Philosphical Forth Musing
  • From: John Passaniti
• Re: Resolving overloading
  • From: Bruce McFarling
• Re: Resolving overloading
  • From: Bruce McFarling
• Re: Resolving overloading
  • From: J Thomas
• Re: DOES> improvement
  • From: Ed
• Re: DOES> improvement
  • From: Bruce McFarling
• Re: Resolving overloading
  • From: J Thomas
• Re: Resolving overloading
  • From: Jerry Avins
• Re: Resolving overloading
  • From: J Thomas
• Re: DOES> improvement
  • From: crc
• Re: Philosphical Forth Musing
  • From: J Thomas
• Re: Philosphical Forth Musing
  • From: idknow
• Re: DOES> improvement
  • From: idknow
• Re: DOES> improvement
  • From: Bruce McFarling
• Re: Resolving overloading
  • From: Stephen Pelc
• Re: Resolving overloading
  • From: Anton Ertl
• Re: Philosphical Forth Musing
  • From: Hugh Aguilar
• Re: DOES> improvement
  • From: Hugh Aguilar
• Re: Resolving overloading
  • From: Elizabeth D Rather
• Re: Resolving overloading
  • From: Bruce McFarling
• Re: Resolving overloading
  • From: Bernd Paysan
• Re: Resolving overloading
  • From: J Thomas
• Re: Resolving overloading
  • From: J Thomas
• Re: DOES> improvement
  • From: Bruce McFarling
• Re: DOES> improvement
  • From: crc
• Re: relative-to-source file names
  • From: Bruce McFarling
• Re: Big news from Green Arrays, Inc. (aka Chuck Moore and friends)
  • From: Ray St. Marie
• Re: Resolving overloading
  • From: Bruce McFarling
• Re: Resolving overloading
  • From: Stephen Pelc
• Re: Resolving overloading
  • From: Andrew Haley
• Re: DOES> improvement
  • From: Jerry Avins
• Re: Resolving overloading
  • From: Andrew Haley
• Re: Resolving overloading
  • From: Bernd Paysan
• Re: DOES> improvement
  • From: idknow
• Re: Resolving overloading
  • From: J Thomas
• Re: Resolving overloading (was: relative-to-source file names)
  • From: Bernd Paysan
• Re: Resolving overloading
  • From: Andrew Haley
• Re: Resolving overloading (was: relative-to-source file names)
  • From: J Thomas
• Re: relative-to-source file names
  • From: Bruce McFarling
• Re: Resolving overloading (was: relative-to-source file names)
  • From: Stephen Pelc
• Re: relative-to-source file names
  • From: Stephen Pelc
• Re: Why bigForth is Linux only
  • From: Bernd Paysan
• Re: Resolving overloading (was: relative-to-source file names)
  • From: Bruce McFarling
• Re: Why bigForth is Linux only
  • From: pliz
• Re: Resolving overloading (was: relative-to-source file names)
  • From: Bernd Paysan
• Re: Resolving overloading (was: relative-to-source file names)
  • From: Bruce McFarling
• Re: relative-to-source file names
  • From: Bruce McFarling
• Re: Text substitution
  • From: Bruce McFarling
• Re: Text substitution
  • From: Josh Grams
• Re: Text substitution
  • From: Stephen Pelc
• Re: relative-to-source file names
  • From: Bernd Paysan
• Re: Resolving overloading (was: relative-to-source file names)
  • From: Bernd Paysan
• Re: Why bigForth is Linux only
  • From: Bernd Paysan
• Re: ANSI screen editor for GForth ?
  • From: Albert van der Horst
• Re: DOES> improvement
  • From: J Thomas
• Re: Text substitution
  • From: Bruce McFarling
• Re: >ORDER ORDER> ORDER@
  • From: Bruce McFarling
• Re: ANSI screen editor for GForth ?
  • From: Bruce McFarling
• Re: relative-to-source file names
  • From: Bruce McFarling
• Re: Philosphical Forth Musing
  • From: The Beez'
• Re: relative-to-source file names
  • From: Bruce McFarling
• Re: relative-to-source file names
  • From: Bruce McFarling
• Re: Novice - use of execute
  • From: Fanzo
• Re: Why bigForth is Linux only
  • From: pliz
• Resolving overloading (was: relative-to-source file names)
  • From: Anton Ertl
• Re: >ORDER ORDER> ORDER@
  • From: Anton Ertl
• Re: Text substitution
  • From: Anton Ertl
• Re: relative-to-source file names
  • From: Anton Ertl
• Re: ANSI screen editor for GForth ?
  • From: Carsten Strotmann
• Re: Why bigForth is Linux only
  • From: Bernd Paysan
• Re: relative-to-source file names
  • From: Bernd Paysan
• Re: DOES> improvement
  • From: Albert van der Horst
• Re: Text substitution
  • From: Albert van der Horst
• Make Money Rs. 1000 per day My Dear Friends, I tried a lot of works in online business, finally I find one guniune opportunity. That's www.time2rich.com/r9a9m9 At www.time2rich.com/r9a9m9 you will have international business, with just star
  • From: summa
• Re: relative-to-source file names
  • From: Marcel Hendrix
• Re: relative-to-source file names
  • From: Bruce McFarling
• Re: relative-to-source file names
  • From: Bernd Paysan
• Re: Novice - use of execute
  • From: Bruce McFarling
• Re: relative-to-source file names
  • From: Bruce McFarling
• Re: >ORDER ORDER> ORDER@
  • From: Bruce McFarling
• Re: Text substitution
  • From: Bruce McFarling
• Re: DOES> improvement
  • From: Elizabeth D Rather
• Re: Text substitution
  • From: Stephen Pelc
• Re: DOES> (again)
  • From: Elizabeth D Rather
• Re: DOES> improvement
  • From: Elizabeth D Rather
• Re: Text substitution
  • From: Josh Grams
• Re: DOES> improvement
  • From: J Thomas
• Re: Novice - use of execute
  • From: Celime
• Re: Big news from Green Arrays, Inc. (aka Chuck Moore and friends)
  • From: Ray St. Marie
• Re: DOES> (again)
  • From: J Thomas
• Re: >ORDER ORDER> ORDER@
  • From: Anton Ertl
• Re: DOES> improvement
  • From: Coos Haak
• Re: relative-to-source file names
  • From: Andrew Haley
• Re: DOES> (again)
  • From: MarkWills
• Re: >ORDER ORDER> ORDER@
  • From: Bruce McFarling
• Re: Text substitution
  • From: Bruce McFarling
• Re: Text substitution
  • From: Stephen Pelc
• Re: DOES> (again)
  • From: Bruce McFarling
• Re: Text substitution
  • From: Stephen Pelc
• Re: DOES> improvement
  • From: Bruce McFarling
• Re: DOES> improvement
  • From: John Rible
• Re: DOES> (again)
  • From: MarkWills
• Re: Text substitution
  • From: Bruce McFarling
• Re: Text substitution
  • From: Josh Grams
• Re: DOES> improvement
  • From: Bruce McFarling
• Re: DOES> (again)
  • From: Bruce McFarling
• Re: DOES> improvement
  • From: J Thomas
• DOES> improvement
  • From: Hugh Aguilar
• DOES> improvement
  • From: Hugh Aguilar
• Re: Text substitution
  • From: Bruce McFarling
• Re: Text substitution
  • From: Josh Grams
• Re: >ORDER ORDER> ORDER@
  • From: David N. Williams
• Re: Philosphical Forth Musing
  • From: Michael Haardt
• Re: >ORDER ORDER> ORDER@
  • From: Stephen Pelc
• Re: >ORDER ORDER> ORDER@
  • From: Bruce McFarling
• Re: Text substitution
  • From: Bruce McFarling
• Re: relative-to-source file names
  • From: J Thomas
• Re: relative-to-source file names
  • From: Bruce McFarling
• Re: DOES> (again)
  • From: Gerry
• Re: Philosphical Forth Musing
  • From: Paul E. Bennett
• Re: Novice - use of execute
  • From: Gerry
• Re: relative-to-source file names
  • From: J Thomas
• Re: >ORDER ORDER> ORDER@
  • From: J Thomas
• Re: >ORDER ORDER> ORDER@
  • From: David N. Williams
• Text substitution
  • From: Josh Grams
• Re: >ORDER ORDER> ORDER@
  • From: David N. Williams
• Re: >ORDER ORDER> ORDER@
  • From: Anton Ertl
• Re: >ORDER ORDER> ORDER@
  • From: David N. Williams
• Re: Novice - use of execute
  • From: Fanzo
• Re: >ORDER ORDER> ORDER@
  • From: Bruce McFarling
• Re: relative-to-source file names
  • From: Bruce McFarling
• Re: Whatever happened to Eric LaForest?
  • From: rickman
• Re: Whatever happened to Eric LaForest?
  • From: rickman
• Re: >ORDER ORDER> ORDER@
  • From: Coos Haak
• Re: relative-to-source file names
  • From: Bernd Paysan
• Re: Novice - use of execute
  • From: Anton Ertl
• >ORDER ORDER> ORDER@
  • From: David N. Williams
• Re: relative-to-source file names
  • From: Bruce McFarling
• Re: relative-to-source file names
  • From: Bruce McFarling
• Re: DOES> (again)
  • From: Bruce McFarling
• Re: DOES> (again)
  • From: Bruce McFarling
• Re: DOES> (again)
  • From: J Thomas
• Re: Philosphical Forth Musing
  • From: Dennis
• Re: Whatever happened to Eric LaForest?
  • From: Eric
• Re: Whatever happened to Eric LaForest?
  • From: Eric
• Re: DOES> (again)
  • From: MarkWills
• Re: www.forth.org wrong scan [was Re: www.forth.org is broken]
  • From: Rod Pemberton
• Re: Philosphical Forth Musing
  • From: Andrew Haley
• Re: Philosphical Forth Musing
  • From: Bernd Paysan
• Re: relative-to-source file names
  • From: Andrew Haley
• Re: relative-to-source file names
  • From: Bernd Paysan
• Re: relative-to-source file names
  • From: Andrew Haley
• www.world2015.org
  • From: www.world2015.org
• Re: Philosphical Forth Musing
  • From: Elizabeth D Rather
• Re: DOES> (again)
  • From: J Thomas
• Re: DOES> (again)
  • From: Bruce McFarling
• Philosphical Forth Musing
  • From: MarkWills
• Re: DOES> (again)
  • From: MarkWills
• Re: relative-to-source file names
  • From: Bruce McFarling
• Re: 4th RfD: Directories
  • From: Bruce McFarling
• Re: relative-to-source file names
  • From: Bruce McFarling
• Re: Novice - use of execute
  • From: Coos Haak
• Re: 4th RfD: Directories
  • From: idknow
• Re: 4th RfD: Directories
  • From: Bruce McFarling
• Re: Novice - use of execute
  • From: Jerry Avins
• Re: Novice - use of execute
  • From: Elizabeth D Rather
• Novice - use of execute
  • From: Fanzo
• Re: relative-to-source file names
  • From: J Thomas
• Re: DOES> (again)
  • From: J Thomas
• Re: 4th RfD: Directories
  • From: J Thomas
• Re: 4th RfD: Directories
  • From: J Thomas
• Re: Whatever happened to Eric LaForest?
  • From: Brad
• Re: relative-to-source file names (was: Small, understandable Forth)
  • From: Anton Ertl
• Re: relative-to-source file names
  • From: Anton Ertl
• Re: relative-to-source file names
  • From: Bruce McFarling
• Re: DOES> (again)
  • From: Elizabeth D Rather
• Re: 4th RfD: Directories
  • From: Bruce McFarling
• Re: 4th RfD: Directories
  • From: Bernd Paysan
• Re: 4th RfD: Directories
  • From: Anton Ertl
• Re: Whatever happened to Eric LaForest?
  • From: Eric
• Re: DOES> (again)
  • From: J Thomas
• Re: relative-to-source file names
  • From: Anton Ertl
• Re: DOES> (again)
  • From: Andrew Haley
• Re: 4th RfD: Directories
  • From: Stephen Pelc
• Re: DOES> (again)
  • From: Albert van der Horst
• Re: relative-to-source file names
  • From: Stephen Pelc
• Re: relative-to-source file names
  • From: Bernd Paysan
• Re: relative-to-source file names (was: Small, understandable Forth)
  • From: Bernd Paysan
• Re: relative-to-source file names
  • From: Andrew Haley
• Re: 4th RfD: Directories
  • From: Bruce McFarling
• Re: relative-to-source file names
  • From: Bruce McFarling
• Re: relative-to-source file names
  • From: Stephen Pelc
• Re: relative-to-source file names
  • From: Stephen Pelc
• Re: relative-to-source file names
  • From: Bruce McFarling
• Re: relative-to-source file names
  • From: Bruce McFarling
• Re: relative-to-source file names (was: Small, understandable Forth)
  • From: Bruce McFarling
• Re: relative-to-source file names
  • From: J Thomas
• Re: relative-to-source file names
  • From: Stephen Pelc
• Re: relative-to-source file names
  • From: Anton Ertl
• Re: relative-to-source file names (was: Small, understandable Forth)
  • From: Anton Ertl
• Re: relative-to-source file names (was: Small, understandable Forth)
  • From: J Thomas
• Re: relative-to-source file names
  • From: Anton Ertl
• Re: relative-to-source file names
  • From: Anton Ertl
• Re: relative-to-source file names (was: Small, understandable Forth)
  • From: Anton Ertl
• Re: relative-to-source file names (was: Small, understandable Forth)
  • From: Anton Ertl
• Re: relative-to-source file names (was: Small, understandable Forth)
  • From: Anton Ertl
• 4th RfD: Directories
  • From: Anton Ertl
• Re: relative-to-source file names
  • From: Bruce McFarling
• Re: DOES> (again)
  • From: J Thomas
• Re: DOES> (again)
  • From: foxchip
• Re: DOES> (again)
  • From: J Thomas
• Re: DOES> (again)
  • From: Andrew Haley
• Re: DOES> (again)
  • From: Andrew Haley
• Re: DOES> (again)
  • From: MarkWills
• Re: DOES> (again)
  • From: MarkWills
• Re: DOES> (again)
  • From: Andrew Haley
• Re: DOES> (again)
  • From: Andrew Haley
• Re: relative-to-source file names
  • From: Stephen Pelc
• Re: DOES> (again)
  • From: MarkWills
• Make Money Rs. 1000 per day
  • From: kum mia
• Re: relative-to-source file names
  • From: Bruce McFarling
• Re: relative-to-source file names (was: Small, understandable Forth)
  • From: Bruce McFarling
• Re: relative-to-source file names (was: Small, understandable Forth)
  • From: Bruce McFarling
• Re: relative-to-source file names
  • From: Bruce McFarling
• Re: DOES> (again)
  • From: Bruce McFarling
• Re: Whatever happened to Eric LaForest?
  • From: rickman
• Re: Whatever happened to Eric LaForest?
  • From: Eric
• Re: relative-to-source file names (was: Small, understandable Forth)
  • From: Albert van der Horst
• Re: Making vfxlin standard-compliant (was: relative-to-source file names)
  • From: Thomas ***in
• Re: relative-to-source file names
  • From: Bernd Paysan
• Re: relative-to-source file names (was: Small, understandable Forth)
  • From: Anton Ertl
• Re: DOES> (again)
  • From: MarkWills
• Re: relative-to-source file names
  • From: Stephen Pelc
• Re: relative-to-source file names
  • From: Bernd Paysan
• Re: relative-to-source file names
  • From: kenney
• Re: relative-to-source file names
  • From: Andrew Haley
• Re: relative-to-source file names
  • From: Andrew Haley
• Re: relative-to-source file names (was: Small, understandable Forth)
  • From: Bernd Paysan
• Re: SOURCE-ID
  • From: Gerry
• Re: relative-to-source file names (was: Small, understandable Forth)
  • From: Bruce McFarling
• Re: Making vfxlin standard-compliant (was: relative-to-source file names)
  • From: Bruce McFarling
• Re: SOURCE-ID
  • From: Bruce McFarling
• Re: relative-to-source file names (was: Small, understandable Forth)
  • From: Bruce McFarling
• Re: relative-to-source file names (was: Small, understandable Forth)
  • From: Bruce McFarling
• Re: relative-to-source file names (was: Small, understandable Forth)
  • From: Stephen Pelc
• Re: SOURCE-ID
  • From: Gerry
• Re: relative-to-source file names (was: Small, understandable Forth)
  • From: Josh Grams
• Re: relative-to-source file names (was: Small, understandable Forth)
  • From: Bruce McFarling
• Re: relative-to-source file names
  • From: Bruce McFarling
• Re: relative-to-source file names (was: Small, understandable Forth)
  • From: Bruce McFarling
• Re: relative-to-source file names (was: Small, understandable Forth)
  • From: Bruce McFarling
• Re: Making vfxlin standard-compliant
  • From: Robert Epprecht
• Re: relative-to-source file names (was: Small, understandable Forth)
  • From: Anton Ertl
• Re: Making vfxlin standard-compliant (was: relative-to-source file names)
  • From: Stephen Pelc
• Re: Why bigForth is Linux only
  • From: Bernd Paysan
• Re: relative-to-source file names (was: Small, understandable Forth)
  • From: Stephen Pelc
• Re: Why bigForth is Linux only
  • From: idknow
• Re: Making vfxlin standard-compliant (was: relative-to-source file names)
  • From: Bernd Paysan
• Re: relative-to-source file names (was: Small, understandable Forth)
  • From: Stephen Pelc
• Re: Making vfxlin standard-compliant (was: relative-to-source file names)
  • From: Stephen Pelc
• Re: relative-to-source file names
  • From: Andrew Haley
• Re: relative-to-source file names (was: Small, understandable Forth)
  • From: Anton Ertl
• Re: relative-to-source file names
  • From: Andrew Haley
• Re: relative-to-source file names (was: Small, understandable Forth)
  • From: Stephen Pelc
• Re: relative-to-source file names
  • From: Elizabeth D Rather
• Re: relative-to-source file names
  • From: Bruce McFarling
• Re: relative-to-source file names (was: Small, understandable Forth)
  • From: Bruce McFarling
• Re: relative-to-source file names (was: Small, understandable Forth)
  • From: Bruce McFarling
• Re: relative-to-source file names (was: Small, understandable Forth)
  • From: J Thomas
• Re: Making vfxlin standard-compliant (was: relative-to-source file names)
  • From: Bruce McFarling
• Re: relative-to-source file names
  • From: Bruce McFarling
• Re: relative-to-source file names (was: Small, understandable Forth)
  • From: Bruce McFarling
• Re: relative-to-source file names (was: Small, understandable Forth)
  • From: Stephen Pelc
• Re: relative-to-source file names
  • From: Albert van der Horst
• Re: relative-to-source file names
  • From: Anton Ertl
• Re: relative-to-source file names (was: Small, understandable Forth)
  • From: Anton Ertl
• Re: relative-to-source file names (was: Small, understandable Forth)
  • From: Anton Ertl
• Re: relative-to-source file names (was: Small, understandable Forth)
  • From: Anton Ertl
• Re: Making vfxlin standard-compliant (was: relative-to-source file names)
  • From: Bernd Paysan
• Re: relative-to-source file names (was: Small, understandable Forth)
  • From: Anton Ertl
• Re: relative-to-source file names (was: Small, understandable Forth)
  • From: Anton Ertl
• Making vfxlin standard-compliant (was: relative-to-source file names)
  • From: Anton Ertl
• Re: relative-to-source file names
  • From: Bernd Paysan
• Re: relative-to-source file names (was: Small, understandable Forth)
  • From: Josh Grams
• Re: Why bigForth is Linux only
  • From: Bernd Paysan
• Re: relative-to-source file names
  • From: Marcel Hendrix
• Re: relative-to-source file names (was: Small, understandable Forth)
  • From: Stephen Pelc
• Re: Why bigForth is Linux only
  • From: idknow
• Re: ANSI screen editor for GForth ?
  • From: Anton Ertl
• Re: relative-to-source file names (was: Small, understandable Forth)
  • From: Anton Ertl
• Re: relative-to-source file names (was: Small, understandable Forth)
  • From: Bruce McFarling
• Re: relative-to-source file names (was: Small, understandable Forth)
  • From: Albert van der Horst
• Re: ANSI screen editor for GForth ?
  • From: dbu
• Re: relative-to-source file names (was: Small, understandable Forth)
  • From: Josh Grams
• Re: SOURCE-ID
  • From: Bruce McFarling
• Re: ANSI screen editor for GForth ?
  • From: Bruce McFarling
• Re: ANSI screen editor for GForth ?
  • From: Albert van der Horst
• Re: ANSI screen editor for GForth ?
  • From: Elizabeth D Rather
• Re: ANSI screen editor for GForth ?
  • From: Bruce McFarling
• Re: ANSI screen editor for GForth ?
  • From: Stephen Pelc
• Re: ANSI screen editor for GForth ?
  • From: Shin
• Re: ANSI screen editor for GForth ?
  • From: Josh Grams
• Re: ANSI screen editor for GForth ?
  • From: Bernd Paysan
• Re: ANSI screen editor for GForth ?
  • From: Josh Grams
• Re: SOURCE-ID
  • From: Coos Haak
• Re: Why are there 2 sections: code and header?
  • From: Michael
• Re: ANSI screen editor for GForth ?
  • From: Thomas Braun
• Re: ANSI screen editor for GForth ?
  • From: Thomas Braun
• Re: ANSI screen editor for GForth ?
  • From: Bernd Paysan
• Re: Why bigForth is Linux only
  • From: Anton Ertl
• Re: relative-to-source file names
  • From: Bruce McFarling
• Re: Why bigForth is Linux only
  • From: Mat
• Re: relative-to-source file names (was: Small, understandable Forth)
  • From: Bruce McFarling
• Re: relative-to-source file names (was: Small, understandable Forth)
  • From: Bruce McFarling
• Re: relative-to-source file names
  • From: Bruce McFarling
• Re: Finding Forth host type
  • From: Bruce McFarling
• ANSI screen editor for GForth ?
  • From: Thomas Braun
• Re: Why are there 2 sections: code and header?
  • From: m_l_g3
• Re: SOURCE-ID
  • From: m_l_g3
• Re: Win32Forth - Possible error in floating point exp function
  • From: Dennis
• Re: relative-to-source file names
  • From: Andrew Haley
• Re: relative-to-source file names (was: Small, understandable Forth)
  • From: Albert van der Horst
• Re: SOURCE-ID
  • From: Albert van der Horst
• Re: SOURCE-ID
  • From: Albert van der Horst
• Re: relative-to-source file names
  • From: Anton Ertl
• Re: Why bigForth is Linux only
  • From: Bernd Paysan
• Re: Win32Forth - Possible error in floating point exp function
  • From: George Hubert
• Win32Forth - Possible error in floating point exp function
  • From: Dennis
• Re: relative-to-source file names
  • From: Marcel Hendrix
• Re: Why bigForth is Linux only
  • From: Aleksej Saushev
• Re: relative-to-source file names (was: Small, understandable Forth)
  • From: Bernd Paysan
• Re: relative-to-source file names (was: Small, understandable Forth)
  • From: Stephen Pelc
• Re: relative-to-source file names (was: Small, understandable Forth)
  • From: J Thomas
• Re: 64-bit gforth
  • From: MarkWills
• Re: SOURCE-ID
  • From: Anton Ertl
• Re: relative-to-source file names (was: Small, understandable Forth)
  • From: Anton Ertl
• Re: relative-to-source file names (was: Small, understandable Forth)
  • From: Bernd Paysan
• Re: 64-bit gforth
  • From: Bernd Paysan
• Re: Why bigForth is Linux only
  • From: Bernd Paysan
• Re: 64-bit gforth
  • From: gavino
• Re: Why bigForth is Linux only
  • From: Tarkin
• Re: SOURCE-ID
  • From: Marcel Hendrix
• SOURCE-ID
  • From: Albert van der Horst
• Re: Why are there 2 sections: code and header?
  • From: Ed
• Re: Why bigForth is Linux only
  • From: Aleksej Saushev
• Re: Why bigForth is Linux only
  • From: Aleksej Saushev
• Re: Why bigForth is Linux only
  • From: Bernd Paysan
• Re: Why bigForth is Linux only
  • From: Bernd Paysan
• Re: Why bigForth is Linux only
  • From: Bernd Paysan
• Re: Why bigForth is Linux only
  • From: Aleksej Saushev
• Re: Why bigForth is Linux only
  • From: Aleksej Saushev
• Re: Why bigForth is Linux only
  • From: Tarkin
• Re: relative-to-source file names (was: Small, understandable Forth)
  • From: Anton Ertl
• Re: relative-to-source file names
  • From: Anton Ertl
• Re: Why bigForth is Linux only
  • From: Tarkin
• Re: Why bigForth is Linux only
  • From: Bernd Paysan
• Re: Why bigForth is Linux only
  • From: Bernd Paysan
• Re: Why bigForth is Linux only
  • From: Bernd Paysan
• Re: Why bigForth is Linux only
  • From: Tarkin
• Re: Finding Forth host type
  • From: J Thomas
• Why bigForth is Linux only
  • From: Aleksej Saushev
• Re: relative-to-source file names
  • From: Albert van der Horst
• Re: relative-to-source file names (was: Small, understandable Forth)
  • From: Stephen Pelc
• Re: Small, understandable Forth
  • From: Elizabeth D Rather
• Re: Small, understandable Forth
  • From: Aleksej Saushev
• Re: relative-to-source file names
  • From: Andrew Haley
• Re: Finding Forth host type
  • From: idknow
• Re: relative-to-source file names
  • From: Bernd Paysan
• Re: Whatever happened to Eric LaForest?
  • From: Anton Ertl
• Re: relative-to-source file names
  • From: Anton Ertl
• Re: Why are there 2 sections: code and header?
  • From: Elizabeth D Rather
• Re: Why are there 2 sections: code and header?
  • From: Bernd Paysan
• Re: www.forth.org is broken
  • From: Rod Pemberton
• Re: Why are there 2 sections: code and header?
  • From: John Passaniti
• Re: Why are there 2 sections: code and header?
  • From: Helmut Giese
• Re: VFX Forth installation key needed
  • From: Stephen Pelc
• Re: relative-to-source file names
  • From: Bruce McFarling
• Re: Finding Forth host type
  • From: Bruce McFarling
• Re: Whatever happened to Eric LaForest?
  • From: rickman
• Re: Why are there 2 sections: code and header?
  • From: Michael
• Re: Why are there 2 sections: code and header?
  • From: Albert van der Horst
• Re: Finding Forth host type
  • From: Albert van der Horst
• Re: relative-to-source file names
  • From: Andrew Haley
• Re: Why are there 2 sections: code and header?
  • From: John Passaniti
• Re: Why are there 2 sections: code and header?
  • From: Ed
• Re: Whatever happened to Eric LaForest?
  • From: Eric
• Re: VFX Forth installation key needed
  • From: Dalamana
• Re: VFX Forth installation key needed
  • From: Coos Haak
• Re: Why are there 2 sections: code and header?
  • From: Coos Haak
• VFX Forth installation key needed
  • From: Dalamana
• Re: Why are there 2 sections: code and header?
  • From: Helmut Giese
• Re: Why are there 2 sections: code and header?
  • From: Anton Ertl
• Why are there 2 sections: code and header?
  • From: Helmut Giese
• Re: relative-to-source file names
  • From: Anton Ertl
• Re: Finding Forth host type
  • From: Anton Ertl
• Re: Finding Forth host type
  • From: idknow
• Re: Finding Forth host type
  • From: Bruce McFarling
• Re: Finding Forth host type
  • From: Brad
• Re: Online math-coding contest
  • From: The Beez'
• Re: Online math-coding contest
  • From: Hugh Aguilar
• Re: jonesforth "Killed" error
  • From: Eduardo Cavazos
• Re: relative-to-source file names
  • From: Bruce McFarling
• Re: Small, understandable Forth
  • From: Bruce McFarling
• Re: Small, understandable Forth
  • From: Bruce McFarling
• Re: Finding Forth host type
  • From: Bruce McFarling
• Re: relative-to-source file names
  • From: Albert van der Horst
• Re: Finding Forth host type
  • From: Albert van der Horst
• Re: What do forth people think about google go?
  • From: Mat
• Re: Finding Forth host type
  • From: Ed
• Updated Now : Watch ***y Star Aishwarya rai *** Bathing Videos In All Angles at http://blogcreationandhosting.blogspot.com/2009/11/play-with-internet.html < Due to high***content,I have hidden these videos inside an Image. In that website,
  • From: ranga...............
• Re: relative-to-source file names
  • From: Bruce McFarling
• Re: relative-to-source file names
  • From: J Thomas
• Re: relative-to-source file names
  • From: Bruce McFarling
• Re: Finding Forth host type
  • From: Bruce McFarling
• Re: www.forth.org is broken
  • From: John Passaniti
• Re: Finding Forth host type
  • From: David N. Williams
• Re: Finding Forth host type
  • From: Bernd Paysan
• Re: Finding Forth host type
  • From: The Beez'
• Re: relative-to-source file names
  • From: MarkWills
• Re: Finding Forth host type
  • From: MarkWills
• www.forth.org is broken
  • From: forther
• Re: Small, understandable Forth
  • From: Albert van der Horst
• Re: Calling C functions from Forth
  • From: Helmut Giese
• Re: Calling C functions from Forth
  • From: Helmut Giese
• Re: Finding Forth host type
  • From: Josh Grams
• Re: Calling C functions from Forth
  • From: Mat
• Re: Small, understandable Forth
  • From: Albert van der Horst
• Re: relative-to-source file names
  • From: aph
• Re: Small, understandable Forth
  • From: Bruce McFarling
• Re: FORTH DIMENSIONS Back issues
  • From: Ed
• Finding Forth host type
  • From: Brad
• Re: Small, understandable Forth
  • From: MarkWills
• Re: Small, understandable Forth
  • From: Marcel Hendrix
• Re: What do forth people think about google go?
  • From: Ian Osgood
• Re: Calling C functions from Forth
  • From: John Passaniti
• Re: Small, understandable Forth
  • From: Anton Ertl
• Re: Small, understandable Forth
  • From: Josh Grams
• Re: relative-to-source file names (was: Small, understandable Forth)
  • From: Bruce McFarling
• Re: Small, understandable Forth
  • From: Bruce McFarling
• Re: 22 year olds hate me
  • From: The Beez'
• Re: relative-to-source file names
  • From: Anton Ertl
• Re: relative-to-source file names (was: Small, understandable Forth)
  • From: Anton Ertl
• Re: relative-to-source file names (was: Small, understandable Forth)
  • From: Anton Ertl
• Re: Calling C functions from Forth
  • From: Anton Ertl
• Re: cell size portability (was: Small, understandable Forth)
  • From: Anton Ertl
• Re: Small, understandable Forth
  • From: Anton Ertl
• Re: jonesforth "Killed" error
  • From: aph
• Re: jonesforth "Killed" error
  • From: Rod Pemberton
• Re: 22 year olds hate me
  • From: Wayne
• Re: Small, understandable Forth
  • From: Josh Grams
• Online math-coding contest
  • From: dhashrath govindarajan
• Re: cell size portability (was: Small, understandable Forth)
  • From: Albert van der Horst
• Re: FORTH DIMENSIONS Back issues
  • From: MarkWills
• Calling C functions from Forth
  • From: Helmut Giese
• Re: relative-to-source file names
  • From: aph
• Re: relative-to-source file names (was: Small, understandable Forth)
  • From: J Thomas
• jonesforth "Killed" error
  • From: wayo.cavazos@xxxxxxxxx
• Re: FORTH DIMENSIONS Back issues
  • From: Ed
• Re: relative-to-source file names (was: Small, understandable Forth)
  • From: Bernd Paysan
• Re: relative-to-source file names (was: Small, understandable Forth)
  • From: Stephen Pelc
• Re: What do forth people think about google go?
  • From: Helmar
• Re: relative-to-source file names (was: Small, understandable Forth)
  • From: Anton Ertl
• Re: 22 year olds hate me
  • From: gavino
• Re: What do forth people think about google go?
  • From: gavino
• Re: What do forth people think about google go?
  • From: gavino
• Watch ***y Star Aishwarya rai *** Bathing Videos In All Angles .
  • From: jaagar
• Re: relative-to-source file names (was: Small, understandable Forth)
  • From: Anton Ertl
• Re: What do forth people think about google go?
  • From: Helmar
• Re: relative-to-source file names (was: Small, understandable Forth)
  • From: Anton Ertl
• Re: cell size portability (was: Small, understandable Forth)
  • From: Marcel Hendrix
• Re: Small, understandable Forth
  • From: Anton Ertl
• cell size portability (was: Small, understandable Forth)
  • From: Anton Ertl
• Re: FORTH DIMENSIONS Back issues
  • From: Anton Ertl
• Re: FORTH DIMENSIONS Back issues
  • From: David N. Williams
• Re: FORTH DIMENSIONS Back issues
  • From: Ed
• Re: FORTH DIMENSIONS Back issues
  • From: John Passaniti
• novice.4th
  • From: Hugh Aguilar
• Re: FORTH DIMENSIONS Back issues
  • From: Albert van der Horst
• Re: FORTH DIMENSIONS Back issues
  • From: David N. Williams
• Re: FORTH DIMENSIONS Back issues
  • From: David N. Williams
• Re: Small, understandable Forth
  • From: Josh Grams
• Re: FORTH DIMENSIONS Back issues
  • From: Albert van der Horst
• Re: FORTH DIMENSIONS Back issues
  • From: idknow
• Re: FORTH DIMENSIONS Back issues
  • From: Rod Pemberton
• Re: What do forth people think about google go?
  • From: billy
• Re: FORTH DIMENSIONS Back issues
  • From: John Passaniti
• Re: FORTH DIMENSIONS Back issues
  • From: Ed
• Re: Small, understandable Forth
  • From: Helmar
• Re: FORTH DIMENSIONS Back issues
  • From: MarkWills
• Re: FORTH DIMENSIONS Back issues
  • From: John Passaniti
• Re: Small, understandable Forth
  • From: Josh Grams
• Re: FORTH DIMENSIONS Back issues
  • From: Anton Ertl
• Re: Small, understandable Forth
  • From: Josh Grams
• Re: FORTH DIMENSIONS Back issues
  • From: Josh Grams
• Re: FORTH DIMENSIONS Back issues
  • From: Rod Pemberton
• Re: BUILDS>
  • From: MarkWills
• Re: BUILDS>
  • From: aph
• Re: FORTH DIMENSIONS Back issues
  • From: Rod Pemberton
• BUILDS>
  • From: MarkWills
• Re: FORTH DIMENSIONS Back issues
  • From: John Passaniti
• Re: FORTH DIMENSIONS Back issues
  • From: John Passaniti
• Re: FORTH DIMENSIONS Back issues
  • From: Rod Pemberton
• Re: Small, understandable Forth
  • From: Albert van der Horst
• Re: Small, understandable Forth
  • From: Albert van der Horst
• Re: The colorForth Movies: Ray's Glad to Accomodate
  • From: Ray St. Marie
• Re: FORTH DIMENSIONS Back issues
  • From: winston19842005@xxxxxxxxx
• Re: FORTH DIMENSIONS Back issues
  • From: John Passaniti
• Re: What do forth people think about google go?
  • From: John Passaniti
• Re: relative-to-source file names (was: Small, understandable Forth)
  • From: J Thomas
• Re: Small, understandable Forth
  • From: Marcel Hendrix
• Re: relative-to-source file names (was: Small, understandable Forth)
  • From: Bernd Paysan
• Re: Windows 7 64-bit issues
  • From: Stephen Pelc
• Re: relative-to-source file names (was: Small, understandable Forth)
  • From: Stephen Pelc
• Re: Windows 7 64-bit issues
  • From: Dennis
• Re: relative-to-source file names (was: Small, understandable Forth)
  • From: Josh Grams
• Re: relative-to-source file names (was: Small, understandable Forth)
  • From: Bernd Paysan
• Re: relative-to-source file names (was: Small, understandable Forth)
  • From: Anton Ertl
• Re: Small, understandable Forth
  • From: Anton Ertl
• Re: Small, understandable Forth
  • From: Anton Ertl
• Re: Small, understandable Forth
  • From: J Thomas
• Re: relative-to-source file names (was: Small, understandable Forth)
  • From: Bernd Paysan
• Re: Small, understandable Forth
  • From: Bruce McFarling
• Re: Small, understandable Forth
  • From: Bruce McFarling
• Re: Small, understandable Forth
  • From: Anton Ertl
• Re: Small, understandable Forth
  • From: Anton Ertl
• relative-to-source file names (was: Small, understandable Forth)
  • From: Anton Ertl
• Re: Small, understandable Forth
  • From: Anton Ertl
• Re: Windows 7 64-bit issues
  • From: Stephen Pelc
• Re: Small, understandable Forth
  • From: Robert Epprecht
• Re: FORTH DIMENSIONS Back issues
  • From: Rod Pemberton
• Re: FORTH DIMENSIONS Back issues
  • From: John Passaniti
• What do forth people think about google go?
  • From: gavino
• Re: Windows 7 64-bit issues
  • From: Dennis
• Re: Small, understandable Forth
  • From: Bruce McFarling
• Re: Small, understandable Forth
  • From: Bruce McFarling
• Re: Small, understandable Forth
  • From: Bruce McFarling
• Re: Small, understandable Forth
  • From: Bruce McFarling
• Re: Small, understandable Forth
  • From: Anton Ertl
• Re: Small, understandable Forth
  • From: Anton Ertl
• Re: Windows 7 64-bit issues
  • From: Albert van der Horst
• Re: Small, understandable Forth
  • From: Albert van der Horst
• Re: Small, understandable Forth
  • From: Josh Grams
• Re: Small, understandable Forth
  • From: Josh Grams
• Re: CASE...OF
  • From: Helmar
• Re: FORTH DIMENSIONS Back issues
  • From: Rod Pemberton
• Re: Small, understandable Forth
  • From: Bruce McFarling
• Re: Small, understandable Forth
  • From: Bernd Paysan
• Re: Small, understandable Forth
  • From: Elizabeth D Rather
• Re: Small, understandable Forth
  • From: Josh Grams
• Re: FORTH DIMENSIONS Back issues
  • From: John Passaniti

• Security
• UNIX
• Linux
• Coding
• Usenet

• Archive
• About
• Privacy
• Search
• Imprint

newsgroups.derkeiler.com  > Archive  > Comp  > comp.lang.forth  > 2010-01