Path: csiph.com!eternal-september.org!feeder.eternal-september.org!news.iecc.com!.POSTED.news.iecc.com!nerds-end From: Maury Markowitz Newsgroups: comp.compilers Subject: Re: Languages with optional spaces Date: Tue, 25 Feb 2020 06:13:23 -0800 (PST) Organization: Compilers Central Lines: 4 Sender: news@iecc.com Approved: comp.compilers@iecc.com Message-ID: <20-02-019@comp.compilers> References: <20-02-015@comp.compilers> <20-02-016@comp.compilers> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Injection-Info: gal.iecc.com; posting-host="news.iecc.com:2001:470:1f07:1126:0:676f:7373:6970"; logging-data="44281"; mail-complaints-to="abuse@iecc.com" Keywords: Basic Posted-Date: 25 Feb 2020 10:48:07 EST X-submission-address: compilers@iecc.com X-moderator-address: compilers-request@iecc.com X-FAQ-and-archives: http://compilers.iecc.com In-Reply-To: <20-02-016@comp.compilers> Xref: csiph.com comp.compilers:2457 Unless I'm mistaken, Integer BASIC is a "deep tokenizer", so is it not the case the spaces exist only at entry time? IE, if one types 'PRINT"HELLO"' that will actually be LISTed as 'PRINT "HELLO"? [That is my recollection. Storing tokens takes less space than storing the input text and on those tiny little micros, every byte counted. -John]