Edge Rewrite
// HTMLRewriter · presentation

This page was redesigned at the edge.

Cloudflare fetched the original article and streamed it through HTMLRewriter to apply an entirely new visual system without rebuilding the source page.

// request.cf · coarse context

A page that knows where it met you.

Only coarse request metadata is shown. This demo does not display or persist visitor IP addresses.

Country
US
Cloudflare location
CMH
Connection
HTTP/2
Language
Not provided

Ray ID: a21c586a5dd0f814

Jump to content

Talk:MBASIC

Page contents not supported in other languages.
Add topic
From Wikipedia, the free encyclopedia
Latest comment: 17 years ago by Madkaugh in topic Interpreter versus compiler

Interpreter versus compiler

[edit]

See Interpreter. MBASIC was never described as anything but an interpreter in any literature I recall. While some steps of compilation are similar to those of an interpreter, it needlessly confuses the article to rehash that here. Pragmatically, BASCOM was the compiler. Encyclopedias should never say things like "but that is not strictly true" unless it's a direct quote, or, possibly and exceptionally, followed by a good explanation. --Wtshymanski (talk) 13:42, 6 August 2008 (UTC)Reply

Interpreter_(computing) is the current link. See the Bytecode interpreters section: "There is a spectrum of possibilities between interpreting and compiling ...". MBASIC is a tokenized basic as is GWBASIC. This similar to JAVA being compiled for a JAVA virtual machine. If you save an MBASIC program and do not specify save as ASCII, you are saving the tokenized version.
You are correct about the description in the literature. The literature did not portray an accurate distinction, especially since it was widely recognized that UCSD Pascal "compiled to a P-machine". Madkaugh (talk) 21:40, 23 April 2009 (UTC)Reply