Just figured out that, when the spec says “type-bound procedure”, they mean “method”. And when they say “NOPASS”, that’s their way of saying
“static method”.
I prefer a more clear description over the typical cryptic language
design. "type-bound procedure" spells it out clearly. Fortran has
always leaned towards greater clarity, less obfuscation.
On Sun, 25 Feb 2024 08:48:52 -0600, Gary Scott wrote:LOL, if you understand english, it is quite explicit and clear.
I prefer a more clear description over the typical cryptic language
design. "type-bound procedure" spells it out clearly. Fortran has
always leaned towards greater clarity, less obfuscation.
“Type-bound procedure” is not a term used anywhere else, and has to be explained. Other languages adding OO features stick to well-known
terminology like “method”.
On 2/25/2024 2:23 PM, Lawrence D'Oliveiro wrote:
“Type-bound procedure” is not a term used anywhere else, and has to be >> explained. Other languages adding OO features stick to well-known
terminology like “method”.
LOL, if you understand english, it is quite explicit and clear.
"type-bound procedure" really tells what it is, much more than "method".
Le 01/03/2024 à 02:51, Lawrence D'Oliveiro a écrit :
On Fri, 1 Mar 2024 00:14:06 +0100, pehache wrote:
"type-bound procedure" really tells what it is, much more than
"method".
It’s a mouthful though, isn’t it. Unlike the concise, and common, term >> used by every other OO language out there.
Fortran is by far not an OO language, it just incorporates *some* OO
features on the top of a procedural language. C++ isn't either, by the
way.
That's the point : very few languages fully follow the OOP paradigm
without mixing it with the more classical procedural approach.
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 493 |
Nodes: | 16 (3 / 13) |
Uptime: | 186:39:41 |
Calls: | 9,707 |
Calls today: | 2 |
Files: | 13,737 |
Messages: | 6,179,689 |