Live data from Hacker News

Why I use Object Pascal

dubst3pp4.github.io

61–70 of 235 posts

Re: Why I use Object Pascal

#61
post #9

Turbo Pascal and Forth were my first languages past Assembly on C64. They were so much better then Basic and Assembly for a young teenagers. Delphi is now $1,200 to $4,400 a user!!! WOW more then the $75 in 1983 https://www.embarcadero.com/app-development-tools-store/delp...

THere is a crippled version of Delphi that is free but limit is only targeting 32 Bit Windows. That may be enough for some but not if you wanted to do cross platform (which is what Emberacardo is providing now).

Re: Why I use Object Pascal

#62

Weird anyone still uses this, I first saw Object Pascal on a Apple Lisa in 1983.

FWIW Apple's Object Pascal and modern Object Pascal have little common. Although i think Free Pascal does have a Mac Pascal mode so that it can understand Apple's Object Pascal dialect.

From what I've read Object Pascal is just another name for Delphi but without the trademark hassle.

Re: Why I use Object Pascal

#63
To my limited experience, everything Pascal had of its own is unusable. Everything usable in the language comes imported from C.

However I can see how one would prefer Object Pascal over C++.

Re: Why I use Object Pascal

#64
post #21

"You can also define your own types" , "classes can also inherit other classes" , "Pascal is modular" ... Not to say these are not valid reasons, or expectations one may have from a language, but - what exactly is Pascal being compared to? I mean, it's 2017.

> Not to say these are not valid reasons, or expectations one may have from a language, but - what exactly is Pascal being compared to? I mean, it's 2017.

I have been searching for it for 15 min now, but last month or so on hn there was a article comparing programming languages and compilers. fpc performance was comparable to c.

Also a mvp production exe will be 2.5 MB, no stdlib/.net/qt needed.

Re: Why I use Object Pascal

#66
post #55

Earlier quoted context omitted.

C has no classes, and everything's in one global namespace. Scheme & LISP have no built-in classes, and one can argue that CLOS isn't what we normally describe as OOP. Both normally have a global namespace. Inheritance in JavaScript is possible but very hard to implement correctly before ES6. Node has namespaces (sort of) but client-side JavaScript generally doesn't. PHP in theory has namespaces, but the standard lib…

I'm not saying these are features provided by every modern programming language - obviously eg. there are FP languages that are not object-oriented, as you pointed out. Still, the selection of languages that do is so vast that such reasons hardly answer the question "why Pascal, of all the options".

There are only a few "popular" languages that have both, many that don't; those are not mandatory features for everyone.

I care about performance (ruling out any GC language), multi-platform native binaries, language readability, dev community, and a bundle of other factors. Pascal turns out to hit most of my needs and not annoy me too much.

Of the thousands of more obscure languages, I'm sure there's one that'd be perfect, except I'd have a worse time with libraries.

Re: Why I use Object Pascal

#67
post #62

Earlier quoted context omitted.

FWIW Apple's Object Pascal and modern Object Pascal have little common. Although i think Free Pascal does have a Mac Pascal mode so that it can understand Apple's Object Pascal dialect.

From what I've read Object Pascal is just another name for Delphi but without the trademark hassle.

No need to speculate[0]. The name "object pascal" was firstly used by apple for their dialect of pascal. Then Borland came and evolved Turbo Pascal into Object Pascal(and brand it Delphi) and then fpc came and branded them a open source object pascal implementation.

As for Pascal vs Object Pascal, Procedural vs OOP, Think C vs C++(not that I'm saying c++ is better).

[0]: https://en.wikipedia.org/wiki/Object_Pascal

Re: Why I use Object Pascal

#68
I've tried picking up Free Pascal and, for me, the documentation is lacking. I come from C# where Microsoft has amazing documentation and small examples on how to use just about every single class in the .NET framework. I guess I'm just spoiled with the documentation I have had and need to get used to it.

Re: Why I use Object Pascal

#69

Earlier quoted context omitted.

C has no classes, and everything's in one global namespace. Scheme & LISP have no built-in classes, and one can argue that CLOS isn't what we normally describe as OOP. Both normally have a global namespace. Inheritance in JavaScript is possible but very hard to implement correctly before ES6. Node has namespaces (sort of) but client-side JavaScript generally doesn't. PHP in theory has namespaces, but the standard lib…

> PHP in theory has namespaces, but the standard libraries are just dumped in global. Modern PHP development almost exclusively uses Composer libraries rather than the standard libraries, which overwhelmingly use namespaces in Vendor\Project format. There's going to be a push to clean up the standard library in the coming years. The plan is to introduce a namespaced alternative to the standard library in the global n…

Namespaces by 2020? That'd be nice. The \ syntax still makes my eyes bleed a bit, when most others use . or :

Re: Why I use Object Pascal

#70
post #68

I've tried picking up Free Pascal and, for me, the documentation is lacking. I come from C# where Microsoft has amazing documentation and small examples on how to use just about every single class in the .NET framework. I guess I'm just spoiled with the documentation I have had and need to get used to it.

Borland/Delphi set the standard for documentation that MS then copied to .NET (no wonder Delphi and C# creator is the same person). FPC likely assumes you have access to Delphi help files.
Post reply on HN