[Nickle] User trap revisited---setjmp() at top level

[Bart Massey]

Good point.  I'm now extra-confused as to what I even want.
But something needs to be done.  I just noticed that putting
a namespace{} declaration around code potentially changes
its meaning, since the namespace encloses its statements in
a block.

Bleah.

	Bart

In message <1139799748.4183.80.camel at evo.keithp.com> you wrote:
> 
> --===============1272567500==
> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-XkVDsgPXy4PdMLtqiEAO"
> 
> 
> --=-XkVDsgPXy4PdMLtqiEAO
> Content-Type: text/plain
> Content-Transfer-Encoding: quoted-printable
> 
> On Sun, 2006-02-12 at 17:37 -0800, nickle at po8.org wrote:
> 
> > I think it should be possible to make setjmp() throw an
> > exception when called at top level, no?  And isn't this what
> > is wanted, given that it's going to behave in such a
> > surprising fashion?
> 
> that would be trivial, but not exactly a complete fix, any call sequence
> which terminates in setjmp and then exits back out the top has precisely
> the same issue.
>  =20
> 
> --=20
> keith.packard at intel.com
> 
> --=-XkVDsgPXy4PdMLtqiEAO
> Content-Type: application/pgp-signature; name=signature.asc
> Content-Description: This is a digitally signed message part
> 
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.2 (GNU/Linux)
> 
> iD8DBQBD7/bDQp8BWwlsTdMRAh3wAJ9vhnGDZns6nd3oENoRpkBAdT6nagCfcO7W
> uywdsb0dhhXKG8VhsepngcE=
> =oluA
> -----END PGP SIGNATURE-----
> 
> --=-XkVDsgPXy4PdMLtqiEAO--
> 
> --===============1272567500==
> Content-Type: text/plain; charset="us-ascii"
> MIME-Version: 1.0
> Content-Transfer-Encoding: 7bit
> Content-Disposition: inline
> 
> _______________________________________________
> Nickle mailing list
> Nickle at nickle.org
> http://nickle.org/mailman/listinfo/nickle
> 
> --===============1272567500==--