Path: nntp.eternal-september.org!news.eternal-september.org!eternal-september.org!.POSTED!not-for-mail From: Paul Rubin Newsgroups: comp.lang.forth Subject: Re: Parsing timestamps? Date: Wed, 02 Jul 2025 12:02:01 -0700 Organization: A noiseless patient Spider Lines: 11 Message-ID: <87tt3uxvpy.fsf@nightsong.com> References: <1f433fabcb4d053d16cbc098dedc6c370608ac01@i2pn2.org> <0db20ddf954106bbca40d9e83630033f108b9a8e@i2pn2.org> <87bjq5yn8i.fsf@nightsong.com> MIME-Version: 1.0 Content-Type: text/plain Injection-Date: Wed, 02 Jul 2025 21:02:02 +0200 (CEST) Injection-Info: dont-email.me; posting-host="e8d0a5c2a6720a43a4ec6d7c3958633e"; logging-data="3865823"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1+tUOXNpCxD7Qqr6M7bLlm9" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.1 (gnu/linux) Cancel-Lock: sha1:7xNDMGiFaMuIMNSFWCZAG53W5E0= sha1:ps/soAnaxQiGb47MNy+hlBOiOT0= albert@spenarnc.xs4all.nl writes: > I had a beef with Andrew Tanenbaum, stating that it is hard to write a > c-compiler for the 6502. In reality the 6502 is a brilliant > design. You must realize that the 6502 has 128 16 bit registers on the > zero page. It's even hard to write compact assembly code, which is why Steve Wozniak wrote SWEET16. I briefly used Aztec C on the Apple II, IIRC. I think it generated bytecode for an interpreter, but am not sure.