Re: "I learned Pascal in uni and haven't touched it in ages, but…"

In: s/pascal

@clseibold -- I never thought I'd find myself defending C, and I won't. I hated it most of my life, but learned to appreciate that it's installed on everything, and after a few decades it almost doesn't matter what language I use -- unless it's Lisp, where I often write code in an entirely different way. Wirth really liked big syntax, which I don't appreciate, hence my favorite languages are Forth and Lisp (and even Smaltalk, with its syntax rules fitting on a business card). Pascal is OK, but if I'm going to use a blub language, C is a safer choice in terms of widespread support, etc. But there is no better language than the one you enjoy!

🚀 stack

2024-10-10 · 2 years ago

8 Later Comments ↓

🌲 greg · 2024-10-12 at 18:15:

If I might add a 3rd option: what about Fortran? It's reasonably close to Pascal on the "less punctuation soup" front, and it's possible to write _very_ efficient math code with it.

🚀 stack · 2024-10-12 at 18:19:

APL?

🦂 zzo38 · 2024-10-12 at 21:27:

There are several problems with the C programming language, but the alternatives seems to avoid many of the good features of C and add some things that also aren't very good, in my opinion. So, I use the C programming language; it is not quite really bad enough that I will not use it, I think.

(I have used Pascal as well, to modify ZZT. Turbo Pascal seems like it is a reasonable programming language for writing DOS programs.)

🐙 norayr [mod] · 2024-10-23 at 00:11:

freepascal is an amazing compiler. it supports turbo pascal dialect if one wants to have that limit. it supports iso mode if you happen to need it. it supports delphi object pascal mode.

it generates very fast code, and in some benchmarks i have shared here, it shares first place with go and c.

🐙 norayr [mod] · 2024-10-23 at 00:26:

horrible standard library

this is a comment left by andreas borchert in comp.lang.oberon in the middle of nineties:

 The libc is certainly not a good guide:

    * Buffer overruns are not ruled out by design: gets, sscanf etc.
    * Interface inconsistencies: gets vs fgets, fgets vs fscanf (note
    the position of the file stream parameter)
    * Bad interfaces like that of getchar() whose return code
    can be a character or an error code
    * Particularly bad buffering system which
    – ignores the block structure of underlying file systems, and
    – does not support bidirectional buffering
    * No provisions exist such that independent libraries can cooperate
    with each other in
    – signal handling,
    – setting up alarms, and
    – tracking childs.

    (Please note that I do not want to bash Ritchie, Kernighan etc. The
    libc is history and should be taken as such… It is time to abandon
    C and the libc and it does not help to place other systems on top of this historic relic.)

i save a link to the usenet post via google groups, it was available years ago, but not now:

— http://groups.google.am/group/comp.lang.oberon/browse_thread/thread/ffe11b45037375e0/e8b65d37114d4931?hl=hy&ie=UTF-8&oe=utf-8&q=andreas+borchert+c+interfaces#e8b65d37114d4931

🐻 TardisKun · 2024-12-01 at 19:04:

@norayr alternate link ;-)

— narkive.com

🐙 norayr [mod] · 2024-12-02 at 00:16:

TardisKun, thank you.

🦁 Houjimmy · 2024-12-03 at 18:44:

I've also learned Pascal have ages, both in school and university. Is it still relevant?

🌒 s/pascal

☯️ dragfyre:

I learned Pascal in uni and haven't touched it in ages, but I'm thinking of picking it up again after reading how much less computation-expensive than, say, Python. Does anyone have any suggestions on good ways to get started again? Also, any thoughts about the virtues of Pascal vs. its related languages like, e.g. Ada?

💬 11 comments · 1 like · 2024-10-10 · 2 years ago