Talk:Pascal (programming language)

Macintosh Pascal compilers

I believe that the history of Pascal compilers is deficient in that it doesn't mention the Macintosh Pascals, some quite early.

Upon its release in the Spring of 1984, there was a beta version of Lightspeed Pascal for the Macintosh. (I saw and used this beta in probably April, 1984.) A completed, non-beta, version was soon available. This ran as an interpretter with a very capable IDE including GUI debugger assembly viewer. A terminal-like text window was provided as was a drawing window. Full access to the Macintosh Toolbox was available. This ran on a 128KB Mac with a single 400KB floppy disk drive.

By probably 1985 or 1986, this product was converted to a compiler, keeping and improving the IDE with expected speed increase. Floating point was emulated 96-bit IEEE type. At some point the product was renamed THINK Pascal and got object-oriented extensions, probably compatible with the Wirth-Apple model, mentioned in the main article.

Apple provided a Mac Pascal compiler with Macintosh Programmer's Workshop, MPW. It differed somewhat from the THINK and Codewarrior (see below) compiler. Of course, Macintosh was completely programmed in Pascal and assembler prior to System 7. (Some of us remember that transition, to System 7, as the beginning of an era of system crashes.)

In approximately 1998 or thereabouts a compiler called CodeWarrior became available on the Macintosh, along with a C compiler. It too had a full-function IDE and many found it to be a suitable replacement for THINK Pascal although it took more "know-how" to make work--the Lightspeed and THINK products were ridiculously easy to use.

174.17.221.250 (talk) 07:51, 4 September 2017 (UTC)

External links modified

Hello fellow Wikipedians,

I have just modified 4 external links on Pascal (programming language). Please take a moment to review my edit. If you have any questions, or need the bot to ignore the links, or the page altogether, please visit this simple FaQ for additional information. I made the following changes:

• Added archive https://web.archive.org/web/20101229090912/http://www.fscript.org/prof/javapassport.pdf to http://www.fscript.org/prof/javapassport.pdf
• Added archive https://web.archive.org/web/20150207194433/http://www.cs.berkeley.edu/~prabal/resources/osprelim/RAA+92.pdf to http://www.cs.berkeley.edu/~prabal/resources/osprelim/RAA+92.pdf
• Added archive https://web.archive.org/web/20101027073206/http://ts.fujitsu.com/products/bs2000/software/compiler/pascalxt.html to http://ts.fujitsu.com/products/bs2000/software/compiler/pascalxt.html
• Added archive https://web.archive.org/web/20050314152247/http://www.cs.inf.ethz.ch/~wirth/books/Pascal/ to http://www.cs.inf.ethz.ch/~wirth/books/Pascal/

When you have finished reviewing my changes, you may follow the instructions on the template below to fix any issues with the URLs.

Y An editor has reviewed this edit and fixed any errors that were found.

• If you have discovered URLs which were erroneously considered dead by the bot, you can report them with this tool.
• If you found an error with any archives or the URLs themselves, you can fix them with this tool.

Cheers.—InternetArchiveBot (Report bug) 21:59, 1 December 2017 (UTC)

"Pascal (programming langauge)" listed at Redirects for discussion

An editor has asked for a discussion to address the redirect Pascal (programming langauge). Please participate in the redirect discussion if you wish to do so. Steel1943 (talk) 18:29, 11 November 2019 (UTC)

"Bogged Down"

In the introduction, the article says that the ALGOL X process "Bogged down". I don't understand what this means. From my understanding, it could mean the process slowed down on its own, but also could mean that the process was slowed down by the introduction of ALGOL W. I think the article would benefit if someone corrected clarified this. Bepvte (talk) 00:10, 30 November 2019 (UTC); edited 00:53, 30 November 2019 (UTC)

I don't understand what happened either. Bubba73 ^{You talkin' to me?} 00:13, 30 November 2019 (UTC)

It's an informal and unreferenced phrase tht we're trying to interpret here, so maybe no really clear outcome is achievable. (And the phrase should probably be replaced, either way - with owt clearer if we can clarify usefully, and with owt less obscure, less vague, if not.)

The Algol X article tells a lot, via its links and references - mainly the November 2016 paper, ALGOL X and ALGOL Y, listed as an external link; the article's references 5 and 6 may be worth a look too. In summary, it seems tht the IFIP Working Group drew together all the right people, but they delegated to a small subcommittee which split and the work stalled: Wirth stepped away, continuing independently.

I remember reading much nearer the time tht Niklaus Wirth had shared his ideas, on an Algol-60 successor, with a colleague on (? ) the IFIP Group's subcommittee; and had been astonished (? putting it politely) when that colleague put forward proposals in a very different spirit at the subcommittee's next meeting.

A lovely story I also read was tht from time to time people would ask Wirth how to pronounce his name; and he would reply using Algol-60 terms: tht "in Europe they tend to call me by name [the correct form, tht one might spell in English as veert]; but in America people call me by value [worth]."

– SquisherDa (talk) 02:11, 30 November 2019 (UTC)

Yes, I love that quote. Bubba73 ^{You talkin' to me?} 02:19, 30 November 2019 (UTC)