Path: csiph.com!usenet.pasdenom.info!weretis.net!feeder4.news.weretis.net!ecngs!feeder2.ecngs.de!newsfeed.freenet.ag!news2.euro.net!postnews2.euro.net!news.wanadoo.nl!not-for-mail
From: mhx@iae.nl (Marcel Hendrix)
Subject: OOP (was: Forth as a polarising language)
Newsgroups: comp.lang.forth
Message-ID: <80071995948435@frunobulax.edu>
Date: Sat, 8 Sep 2012 16:28:55 +0200
References: <2012Sep8.133842@mips.complang.tuwien.ac.at>
X-Newsreader: iForth 2.0 console (October 21, 2006)
Lines: 22
Organization: Wanadoo
NNTP-Posting-Date: 08 Sep 2012 14:28:25 GMT
NNTP-Posting-Host: s529d937f.adsl.wanadoo.nl
X-Trace: 1347114505 dr4.euro.net 9194 82.157.147.127:50361
X-Complaints-To: abuse@wanadoo.nl
Xref: csiph.com comp.lang.forth:15528

anton@mips.complang.tuwien.ac.at (Anton Ertl) writes Re: continue equivalent in Forth?

> mhx@iae.nl (Marcel Hendrix) writes:
[..]
> My question about SECURE was actually meant as follows: If SECURE is
> on, iForth apparently does not accept some Forth-94-compliant control
> structures.  What does it offer that is worth that cost?

For that cost, you can compile code that other Forths won't.

Of course, it would be better to have gForth-like diagnostics with a
SECURE flag to disable them for exceptional cases. Maybe for the next 
redesign -- after my retirement, or when iForth goes open-source :-)

> BTW, your posting would have been easier to read if your newsreader
> also put quote characters in front of cited empty lines.

You actually notice uncited empted lines between all the 
quoted-printable crap that has become the standard lately?

-marcel