7 ms·
Introduction to the Theory of Programming Languages (1991)
- isaacfrond 4y agoLink to the book: https://bertrandmeyer.com/wp-content/upLoads/introduction_to_the_theory_of_programming_languages.pdf https://bertrandmeyer.com/wp-content/upLoads/introduction_to...
- ingve 4y agoNote the warning and request from the main book page: > (Please do not bookmark or share the above download link as it may change, but use the present page: https:/bertrandmeyer.com/ITPL.)
- throwaway81523 4y agoThis book is from 1991. I haven't looked at it, I will do so, it looks promising, but my favorite intro(?) PLT book is Robert Harper's somewhat idiosyncratic Practical Foundations of Programming Languages (PFPL). Some older editions were freely available in entirety, and the current edition has an abridged version online but they make you pay for the full version. I found that the older edition was enough to get a handle on the subject enough to read other sources. https://www.cs.cmu.edu/~rwh/pfpl/ https://www.cs.cmu.edu/~rwh/pfpl/
- oxff 4y agomy job here is done, was about to reco this too
- raspberry1337 4y agoAny place to read or get this that isn't a preview version?
- deleted 4y ago[deleted]
- deleted 4y ago[deleted]
- lioeters 4y agohttps://libgen.is/search.php?req=Practical+Foundations+of+Programming+Languages&lg_topic=libgen&open=0&view=simple&res=25&phrase=1&column=def https://libgen.is/search.php?req=Practical+Foundations+of+Pr...
- Sakos 4y agoI use this site too, but it's literally piracy. I don't think it should be linked directly on HN.
- kleiba 4y agoAmazingly, judging from the font rendering, it seems that this book was written in MS Word?!
- tengwar2 4y agotroff, but MS Word was available from 1983.
- Pinus 4y agoThe text mentions troff and PIC. I wonder whether the author still has the source code... Even if re-rendering with modern tools ("modern" meaning "actually runs on platforms readily available today, e.g. groff and gpic") is more work than he’s willing to put in (which I quite understand), there ought to be someone on the Internet who is enough of a compsci/typography nerd to do it...
- arjvik 4y agoI know nothing about typography, so could you share which aspects of the type specifically stood out to you as bad typography?
- LeonidasXIV 4y agoThe fact that it uses Times New Roman gives it a very (old) "MS Word" vibe.
- deleted 4y ago[deleted]
- eru 4y agoIn addition, the text is 'justified', but there's not a single hyphenation. That's what Word does. And it looks a bit ugly. It's probably worse than just going with left-alignment.
- layer8 4y agoWord actually supports automatic hyphenation, but you have to turn it on (it’s a property of paragraph styles IIRC).
- tailrecursion 4y agoWhat gave me the most perspective on programming language design was reading Leslie Lamport's papers on TLA+. His views on the necessary differences between a P.L. and a specification language gave me a clearer idea what programming languages really are. If I recall, Lamport has several papers on TLA+ for mere mortals that are very easy to read.
- cloogshicer 4y agoThis sounds really great - could you recommend/link some specific ones? Thanks in advance!
- tkhattra 4y ago[1] is a particular one regarding specification languages and types. its background description about a "rabidly pro-types" referee is quite interesting... [1] http://lamport.azurewebsites.net/pubs/pubs.html#lamport-types http://lamport.azurewebsites.net/pubs/pubs.html#lamport-type...
- cloogshicer 4y agoSo a bit of digging brought up this [1], which seems to be a list of all relevant papers. It's annotated with short summaries and historical background by Leslie Lamport himself. Seems like a great starting point! Still, I'd love to hear some specific recommendations for the topic you mentioned, it sounds super interesting. [1] https://lamport.azurewebsites.net/pubs/pubs.html https://lamport.azurewebsites.net/pubs/pubs.html
- bromuk 4y agoDid anyone else get taught Eiffel (by Bertrand) when they were at University? Such a cool little language for teaching object oriented paradigms. I think multiple inheritance was it's selling point, never seen it in industry though lol.
- zasdffaa 4y agoI didn't like it. It was too much theory based without enough recognition of practice. I and a very small company used it ~25 years ago. It wasn't good enough & we eventually dumped it. I can't give you reasons why as it was too long ago but I don't have a good memory of it. I do remember of the Eiffel book that Meyer was a bit too keen on emotive arguments over factual.
- bitL 4y agoThe zeal/tunnel vision of early OOP evangelists resembles the zeal of today's FP evangelists...
- zasdffaa 4y ago(Edited the following) I'm not talking about OOP. Meyer was hard on pre and postconditions (which were massively oversold), but these were functionally no more than assertions. He had holes in his object system. He had holes in other parts of the type system. He was not an object zealot IIRC.
- pjmlp 4y agoThis is great, must have a paper copy somewhere on my university boxes, but it nice that is now available to anyone.
- neebz 4y agoBertrand was one of my favorite people in the software field. I really wanted to do a Phd under his supervision.
- sambeau 4y agoThis was on one of my set texts at University in the 1990s. I still own it (somewhere) and a few others in this series. There was a companion book by David Watt which covered the implementation of interpreters and compilers and used a small functional language that looked a little bit like Pascal, called Triangle. It was written in very plain, easy-to-understand language (and the code was simple to understand, too). I have Peyton Jones's 'The Implementation of FunctionalProgramming Languages' sitting on a shelf beside me, and I often like to look back at Bird & Wadler which is a classic, though I think I lent it to someone and never got it back.
- amelius 4y agoThis title assumes that there is a single theory of programming languages, which is a bit strange.
- jonsen 4y agoNot at all: https://en.m.wikipedia.org/wiki/Programming_language_theory https://en.m.wikipedia.org/wiki/Programming_language_theory
- candyman 4y agoWe used Eiffel to build a funds transfer system way back when, Maybe 1990 or so. I met Bertrand a couple of times because my mentor was a huge fan. He built systems in banking using Modula-2 before Eiffel came along. Last I saw Bertrand he was in Santa Barbara. It feels like disciplined programming is not popular anymore in favor hacking, continuous releases, agile, scrum, etc.
- asib 4y agoWhat makes you say continuous deployment, agile, scrum are in contest with disciplined programming? Maybe I’m misinterpreting the meaning of that term.
- mindcrime 4y agodisciplined programming is not popular anymore in favor hacking, continuous releases, agile, scrum, etc. Wait what? Disciplined programming is not mutually exclusive with at least 3 of those 4 things (continuous releases, agile, scrum). If people treat those things as opposed to disciplined programming, it's because they don't understand the actual principles underlying them.
- rramadass 4y ago>It feels like disciplined programming is not popular anymore in favor hacking, continuous releases, agile, scrum, etc. Rightly said! I learnt "correct" OOD/OOP from his book Object-Oriented Software Construction (https://bertrandmeyer.com/oosc2/ https://bertrandmeyer.com/oosc2/). It was one of the few books which actually looked at "Programming in the Large" specifically through the Object-Oriented lens and also instituted "Design By Contract (DbC)" within the Eiffel language to support it. DbC is a "user-friendly" version of the correct programming techniques espoused by Floyd/Hoare/Dijkstra. One can also say that it subsumes other techniques like TDD since a post-condition is like a unit test in itself. It is a shame people no longer study Meyer's works with the seriousness they should (he maybe a pedant but it is the right sort of pedantry) but instead run after buzzwords/fad of the month. Here is Bertrand Meyer's take (the right one, imo) on Agile from his book Agile! The Good, the Hype and the Ugly - https://learning.acm.org/techtalks/agile https://learning.acm.org/techtalks/agile.
- siraben 4y agoFor those who are self-studying, I recommend Software Foundations[0] which uses the Coq proof assistant, since doing the exercises is far more engaging when Coq lets you finish the proof and you know for sure that you have understood the concepts involved. [0] https://softwarefoundations.cis.upenn.edu/ https://softwarefoundations.cis.upenn.edu/
- nudpiedo 4y agoI see it is mostly focused on semantics: operational, translational, denotational, axiomatic, complementary. I wish there were more books focused on that aspect. I will definitely take a look at it over the weekend.
- rramadass 4y ago1) Formal Syntax and Semantics of Programming Languages: A Laboratory Based Approach by Kenneth Slonneger and Barry Kurtz - https://homepage.divms.uiowa.edu/~slonnegr/ https://homepage.divms.uiowa.edu/~slonnegr/ (PDFs are available on the web). 2) You may also find Cliff B. Jones' book Understanding Programming Languages useful. Excerpt from the preface; Fortunately, there is a less expensive way of sorting out the meaning of a programming language than writing a compiler. This book is about describing the meaning (semantics) of programming languages. A major objective is to teach the skill of writing semantic descriptions because this provides a way to think out and make choices about the semantic features of a programming language in a cost effective way. In one sense a compiler (or an interpreter) offers a complete formal description of the semantics of its source language. But it is not something that can be used as a basis for reasoning about the source language; nor can it serve as a definition of a programming language itself since this must allow a range of implementations. Writing a formal semantics of a language can yield a far shorter description and one about which it is possible to reason. To think that it is a sensible engineering process to go from a collection of sample programs directly to coding a compiler would be naive in the extreme. What a formal semantic description offers is a way to think out, record and analyse design choices in a language; such a description can also be the basis of a systematic development process for subsequent compilers. To record a description of the semantics of a language requires a notation —a “meta-language”. The meta-language used in this book is simple and is covered in easy steps throughout the early chapters.
- mkehrt 4y agoFor a good look at type theory and its relationship to operational semantics in particular, Pierce's Types and Programming Languages is the classic. I suspect Harper's Practical Foundations for Programming Languages has a similar approach though I've not read it.