[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: How to detect EOFs in SEQ-files using M/C?
- Subject: Re: How to detect EOFs in SEQ-files using M/C?
- From: "Glenn P.," <C128User@FVI.Net>
- Date: Mon, 9 Sep 2002 17:11:44 -0400
- Approved: "Glenn P.," <C128User@FVI.Net>
- Disposition-notification: "Glenn P.," <C128User@FVI.Net>
- Disposition-notification-to: "Glenn P.," <C128User@FVI.Net>
- Distribution: world
- Expires: 31 Dec 2002 23:59:59 -0500 (EST)
- Followup-to: comp.sys.apple2
- In-reply-to: <Pine.LNX.4.44.0209090019520.14611-100000@lab.oregonvos.net>
- Newsgroups: comp.sys.apple2, comp.sys.cbm
- Organization: Newsfeeds.com http://www.newsfeeds.com 100,000+ UNCENSORED Newsgroups.
- Receipt: "Glenn P.," <C128User@FVI.Net>
- Receipt-to: "Glenn P.," <C128User@FVI.Net>
- References: <3D7361C3.62826F2@t-online.de> <Fk0GujAfjOcO@ludens> <3D74EA44.8DB205DB@t-online.de> <al2qg1$1lvd8l$4@fu-berlin.de> <3D75D07C.F8DDD0CE@t-online.de> <Pine.LNX.4.44.0209041258460.10348-100000@lab.oregonvos.net> <al63i3$1n48k3$2@fu-berlin.de> <Pine.LNX.4.44.0209041941081.21085-100000@lab.oregonvos.net> <Pine.LNX.4.44.0209081905130.29418-100000@Oswego.FoxValley.net> <Pine.LNX.4.44.0209081656530.1830-100000@lab.oregonvos.net> <Pine.LNX.4.44.0209090048250.31763-100000@Oswego.FoxValley.net> <Pine.LNX.4.44.0209090019520.14611-100000@lab.oregonvos.net>
- Reply-to: "Glenn P.," <C128User@FVI.Net>
- Return-receipt: "Glenn P.," <C128User@FVI.Net>
- Return-receipt-to: "Glenn P.," <C128User@FVI.Net>
- Sender: c128user@FVI.Net
- Xref: archiver1.google.com comp.sys.apple2:22767 comp.sys.cbm:41679
On Mon., 09-Sep-2002, at 12:24am PDT (-0700 GMT), "Matthew Montchalin" wrote:
>> Since PI is frequently uses and would otherwise take up a lot of space,
>> Commodore, in a perfectly reasonable move, assigned it to a one-byte token.
>> That way, instead of saying 100 x=3.14159267, the programmer can save nine
>> bytes and write 100 x=[pi character] instead.
>> What's so strange about that???
> What's strange, is using $ff to represent pi, if memory serves me right.
Your memory serves you perfectly well. What's so strange about $FF (+255)?
It's just a byte value, like any other...
--_____
{~._.~} >>>>>>>> [ "Glenn P.," <C128User@FVI.Net> ] <<<<<<<<
_( Y )_ -----------------------------------
(:_~*~_:) [Disconsolate wail]: "I've got a BLUEBERRY for a daughter!"
(_)-(_) (From: "Willy Wonka And The Chocolate Factory")