Re:Introduction to Compilers and Language Design (2021)
by dunefox on Wednesday May 18, 2022 @08:25AM
(#31421887)
Honestly, I think I'd prefer pseudocode that I can read to understand the idea and then work in my language of choice rather than C.
Re:Introduction to Compilers and Language Design (2021)
by ethanwillis on Wednesday May 18, 2022 @10:06AM
(#31422937)
Psuedocode means ambiguity which means misunderstandings. As soon as you remove all ambiguity any Pseudocode just becomes a language.
Re:Introduction to Compilers and Language Design (2021)
by dunefox on Wednesday May 18, 2022 @11:01AM
(#31423654)
Good point, although I think it should be doable when describing input and output well enough.
Re:Introduction to Compilers and Language Design (2021)
by setr on Wednesday May 18, 2022 @02:09PM
(#31425837)
That's been delegated to the diagrams and algebra -- and there's also the usual english-psuedocode interspersed throughout the chapters (presumably more so on the theoretical chapters e.g. chapter 4)
Re:Introduction to Compilers and Language Design (2021)
by arinlen on Wednesday May 18, 2022 @04:58PM
(#31427569)
> Honestly, I think I'd prefer pseudocode that I can read to understand the idea and then work in my language of choice rather than C.
What stops you from understanding the idea by reading C? It's a tried-and-true language whose K&R version fits entirely in an easy to read ~180pg book which has real world applications, unlike pseudocode.
What did you have in mind?