Re: Proposed patch to marker.fs for allowing custom clean up.

Bernd Paysan <[email protected]> Mon, 11 May 2026 14:58:18 +0200
Newsgroups gmane.comp.lang.forth.gforth
Message-ID <[email protected]>
--nextPartgDLhtA2lRSOcPa1H_rYjKw
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="utf-8"; protected-headers="v1"
From: Bernd Paysan <[email protected]>
To: "gforth-mXXj517/[email protected]" <gforth-mXXj517/[email protected]>
Cc: colossus <[email protected]>, Bernd Paysan <[email protected]>
Subject: Re: Proposed patch to marker.fs for allowing custom clean up.
Date: Mon, 11 May 2026 14:58:18 +0200
Message-ID: <[email protected]>
In-Reply-To: <[email protected]>
MIME-Version: 1.0

Am Montag, 11. Mai 2026, 10:34:22 Mitteleurop=C3=A4ische Sommerzeit schrieb=
 Bernd=20
Paysan:
> Am Montag, 11. Mai 2026, 05:32:51 Mitteleurop=C3=A4ische Sommerzeit schri=
eb
>=20
> colossus via Gforth discussion and announcements:
> > I have from time to time wanted to perform clean up actions when a mark=
er
> > is run, often close files. Win32Forth allowed this by having MARKER-CHA=
IN
> > run and I found it quite useful. The other advantage of this arrangement
> > is that it is possible to localize the clean up actions in the same file
> > as the data structure is defined.
> >=20
> > I have attached a proposed patch. It is pretty simple and only affects =
the
> > marker.fs file.
>=20
> Maskes sense. While we have chains.fs in Gforth, we usually have a deferr=
ed
> word where you can put your chained code in.

Looking at this concept, we should probably have two chains, one for creati=
ng=20
the marker, one for restoring it.  A typical marker functionality comes in=
=20
pairs, like SECTION-MARKER, and SECTION-MARKER!.

=2D-=20
Bernd Paysan
"If you want it done right, you have to do it yourself"
net2o id: kQusJzA;7*?t=3Duy@X}1GWr!+0qqp_Cn176t4(dQ*
https://net2o.de/

--nextPartgDLhtA2lRSOcPa1H_rYjKw
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: This is a digitally signed message part.
Content-Transfer-Encoding: 7Bit

-----BEGIN PGP SIGNATURE-----

iQJPBAABCAA5FiEERJ1NDqPQRwYnwBjr9y2Uk5MtoGcFAmoB0mobFIAAAAAABAAO
bWFudTIsMi41KzEuMTIsMiwyAAoJEPctlJOTLaBnRPsQAIrFYb17OEXDRj4lgnY+
2E/vc3c5SwWqfdWrWpQ1RfjiiGkQRm2g1t5ZwwriWeq5radtm7nHr3VU3oxqBACx
6ppVxfIxO+KRpVezu1vSL2i2KLuEd/MchGKIBw2n6w5uMlhCLMrNbhv9Sai9gpm4
QWQlPt4M9mNur1oo9WpA2PF/t3VV/lPQEQeGXK9d2qg8xAADuz2ZP3tk90djAoWJ
YHXRhZVTB7Dvmkh62D/kjtqrHvHdlYp6fnZoRv+RrTSYoaGbvNmLtspLcA+gOvcB
7wHBOTRp2eMP7tS5AsPiZULdJsQdf+uqI0Y+iDHVa1RGlAjspPyR3c+CTMFmNjex
nQ4Tx115pFBKof+nGPVohbeRQq0MMWOF9jNN2qRfTXeMpyAumvL1OH+Ln0mFNcEJ
B5SsjJxl6QmXKkbOq9WhpKNjjMaOs3edxJ//+yquoZ8G7PVJ6osXVMWz6yY9YYIC
XnU4AJno80NG7a5N0wPFcYk9XECSbhc2IE6lKcZQvgJGHbLj5h6F8F42yNCQ0gjV
siLV3InZSqyQCULnpt2pnenv0dgfAGJ+B+ifuocsAl5rdpwebV3nBn5V1UFLTz0l
i6la4QBT51t5KdhGieRFkSCmDN4ULkblb0SSXL3oN/8e1a2If3soMb6ouDb6osl+
QlMJN5t083FW7ELh+fWMD5FL
=Ttv5
-----END PGP SIGNATURE-----

--nextPartgDLhtA2lRSOcPa1H_rYjKw--