[fpc-pascal] RIP: Software design pioneer and Pascal creator Niklaus Wirth

2024-01-05 Thread Tony Whyman via fpc-pascal
"Swiss computer scientist Professor Niklaus Wirth died on New Year's Day, roughly six weeks before what would have been his 90th birthday." https://www.theregister.com/2024/01/04/niklaus_wirth_obituary/?utm_source=daily_medium=newsletter_content=top-article

Re: [fpc-pascal] RIP: Software design pioneer and Pascal creator Niklaus Wirth

2024-01-05 Thread Michael Van Canneyt via fpc-pascal
On Fri, 5 Jan 2024, Tony Whyman via fpc-pascal wrote: "Swiss computer scientist Professor Niklaus Wirth died on New Year's Day, roughly six weeks before what would have been his 90th birthday."

Re: [fpc-pascal] RIP: Software design pioneer and Pascal creator Niklaus Wirth

2024-01-05 Thread Rainer Stratmann via fpc-pascal
Misconstruing complexity as sophistication: According to Wirth, “people seem to misinterpret complexity as sophistication.” The more complicated a product is, the more polished or knowledgeable the user would appear. Hence, software vendors create complex software and send this marketing

[fpc-pascal] Does the varargs specifier behave differently on 32 and 64 bit platforms?

2024-01-05 Thread Thomas Kurz via fpc-pascal
Hello, I'm using a declaration like this TYPE TRSMControl = FUNCTION (AData: PtrInt): PtrInt; CDECL; VARARGS; VAR RSMControl: TRSMControl; to make calls to a DLL function which expects a variable number of arguments. For example: RSMControl (PtrInt(1), PtrInt(2), PtrInt(3)) On win32, this

Re: [fpc-pascal] Does the varargs specifier behave differently on 32 and 64 bit platforms?

2024-01-05 Thread Jonas Maebe via fpc-pascal
On 05/01/2024 14:38, Thomas Kurz via fpc-pascal wrote: The CDECL calling convention should pass all arguments on the stack It does not do that in all (or even most) cases. The CDECL calling convention passes arguments according to what the platform's ABI prescribes. For Windows/x64, that