| Deutsch English Français Italiano |
|
<87zfdvyo0m.fsf@nightsong.com> View for Bookmarking (what is this?) Look up another Usenet article |
Path: news.eternal-september.org!eternal-september.org!.POSTED!not-for-mail From: Paul Rubin <no.email@nospam.invalid> Newsgroups: comp.lang.forth Subject: Re: Parsing timestamps? Date: Thu, 26 Jun 2025 00:12:41 -0700 Organization: A noiseless patient Spider Lines: 16 Message-ID: <87zfdvyo0m.fsf@nightsong.com> References: <1f433fabcb4d053d16cbc098dedc6c370608ac01@i2pn2.org> <bdc732e87e38233e9e23f254b2326cf2@www.novabbs.com> <nnd$1a4144e5$43cad09f@b57c0b5013a1f2ab> <6ea4ccd1cb6ae8c828144444fe51fea9@www.novabbs.com> <70a3014f99baf5e43b32e1320d7b8cd482be04c1@i2pn2.org> <bfc6dc31af5bcbe4b4b0a2ccba8167e3@www.novabbs.com> <a8647abe1ce54c9c55c558f571761214a7c9d0f0@i2pn2.org> <61ff078b04e03c7b65b6dff98f58b80b@www.novabbs.com> <nnd$15d62a05$79f87aeb@2d18b2c67eb1f6e0> <f3fbac3a6e57ccf7465fff66180ac9e1@www.novabbs.com> <2025Jun23.071834@mips.complang.tuwien.ac.at> <a004d0f4acf945e054db77d86a4544fc@www.novabbs.com> <nnd$0d7645ea$11a210a3@2cd6ffa4d9a3008a> <4a4c38c99d22d97314ed5750af38430d@www.novabbs.com> <765bd244e1368b5691f18c748102470e8de1a30d@i2pn2.org> <nnd$0deda869$2559e613@c251414cde7edbe7> <d82938e7a98984ff66ded29fed23e5594c228aea@i2pn2.org> <87h6041iue.fsf@nightsong.com> <cc98bb3dffab9c5b6232794b908f75be77bb05de@i2pn2.org> MIME-Version: 1.0 Content-Type: text/plain Injection-Date: Thu, 26 Jun 2025 09:12:46 +0200 (CEST) Injection-Info: dont-email.me; posting-host="bf6dace3f096446cc570f527f1357dec"; logging-data="3512158"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1+xr2XyQEoU5yNnj3Znsq6E" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.1 (gnu/linux) Cancel-Lock: sha1:iazGelCHyznonOc8xfb5H/Pk74k= sha1:4g8TdOWS8gzytH24sxm2YHH8i9g= dxf <dxforth@gmail.com> writes: > Define 'unreadable'. In general I don't need to understand the nitty > gritty of a routine. But should I and no stack commentary exists, I've > no objections to creating it. It's par for the course in Forth. If it > bugged me I wouldn't be doing Forth. Unreadable = I look at the code and have no idea what it's doing. The logic is often obscured by stack manipulation. The values in the stack are meaningful to the program's operation, but what is the meaning? In most languages, meaningful values have names, and the names convey the meaning. In Forth, you can write comments for that purpose. Years after cmForth was published, someone wrote a set of shadow screens for it, and that helped a lot. With no named values and no explanatory comments, the program becomes opaque.