#objectpascal — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #objectpascal, aggregated by home.social.
-
👏 Wow, finally! The world has been begging for yet another Object Pascal #compiler because, you know, the planet just can't function without one in 2023. 🚀 Let's celebrate the #reincarnation of a language most people haven't used since the 90s. #CuttingEdgeInnovation 🙄
https://github.com/graemeg/blaise #ObjectPascal #Innovation #TechNews #HackerNews #ngated -
Blaise – A modern self-hosting zero-legacy Object Pascal compiler targeting QBE
https://github.com/graemeg/blaise
#HackerNews #Blaise #ObjectPascal #Compiler #SelfHosting #QBE #OpenSource
-
RE: https://oldbytes.space/@thelastpsion/116345290344668595
And the results are in!
- Pico C
- Rust
- Free Pascal
- Joint with Pico C++, MicroZig and Yarg.
So, what am I going to do? Well, I'm leaning towards porting the existing Arduino C code to the Pico C SDK. I'm currently using one class for encapsulation and abstraction, but I could replace that with structs and static functions. I'm not a great C programmer, but I'm pretty comfortable with it, so it makes sense
However, before I do that, I see a bigger challenge of getting a good setup without using VS Code. I've been using #NeoVim for a while now, and I'd like to get a comfortable setup using that on #Linux.
So, I'm going to try to build Blinky projects for at least Pico C, Rust and Free Pascal, using Linux and NeoVim. Hopefully this will give me a better feel for how well these languages actually suit me. I've never done any Rust before, either, so that's going to be quite the learning curve!
If I have time, I'm going to give Yarg a go, too, because I think the premise is really cool. If I'm on a roll, I'll try #MicroZig too.
And if I really feel like I have the capacity, I'll port the code to one of these other languages.
I'm acutely aware of all the other projects I've given myself to do, such as the SIBO SDK and other small Psion-related projects, not to mention $dayjob and $reallife. So we'll see how things go!
#Pascal #FreePascal #ObjectPascal #RustLang #YargLang #RaspberryPiPico #PiPico #PiPico2 #RP2040 #RP2350
-
#Question
#DearInternet
#DearFediverse
#DearLazyWeb(1) Does the Apple MacBook Neo support virtualisation (Hypervisor)?
#HyperVisor #QEMU #VirtualMachine #Virtualisation
(2) Can you do macOS/iOS software development on an Apple MacBook Neo?
(3) Can you do software development on an Apple MacBook Neo?
#ObjectPascal #Delphi #Ada #Lisp #Scheme #Racket #SmallTalkLang #SelfLang
-
I've been musing on #OOP style. I have a question for the more experienced programmers out there.
How do you decide when a class's method doesn't actually need to be a method, but instead could just be a regular function?
I'm not talking about functions that need to be shared between classes. I'm talking about intentionally moving a method outside of a class, even though it will only ever be used by that class.
For example, if I've got a parser-related function that is only needed by the parser, I will normally just put it in the parser class as a method. It keeps things neat, I can make it private and lock down the class. But I've never before stopped to think whether this is the correct thing to do every time.
After all, #Pascal (my language of choice) has the concept of units. I could just have some functions just as functions, and only have methods for things that directly need to update the class's properties.
It would make things easier for testing, too. I wouldn't need to create an instance of a class just to test a specific function works as intended.
But I don't know if it's the "right" way to do things in OO, or #ObjectPascal for that matter.
-
If anyone wants to see some incredibly poor #ObjectPascal, here's a link to #ecobj in its current form.
It's very much at the "work out how any of this works" stage. Expect the code to change radically!
-
REPOST (JAN 2024): My first thoughts on #Psion's dialect of Object Oriented C for the Series 3 and related portable computers.
Includes the JPI/Clarion #TopSpeed #compiler, a proprietary preprocessor, the Eiffel programming language, and a handful of calling conventions.
Also, did somebody say Objective-C?
This is an old blog post from the beginning of the year. If you've been following my journey in recreating #CTRAN, this was written a week before I decided to take the plunge.
(Yes, I did say in the article that I definitely wouldn't be writing a compiler. I did say that.)
#RetroComputing #EPOC16 #CDECL #Clarion #TopSpeed #TopSpeedC #RetroProgramming #RetroDev #Smalltalk #ObjectPascal #preprocessor #Eiffel #OOP #ObjectiveC #compilers #ObjectOriented
-
Thoughts on 3 months of #ObjectPascal #FreePascal usage (in #NeoVim):
- Easy to pick up and read
- Good libraries
- Generics
- No closures
- Binaries aren't small
- LSP (pasls) isn't complete, but better than nothing; #Treesitter + #Periscope really help
- Docs are frustrating
- Good forums/community
- Targets SO MANY platforms (#HaikuOS, 32-bit #DOS, #Amiga, #Z80, #baremetal)! More than Rust, Go
- A *lot* of historic books and projectsWould I use #Pascal again? Absolutely yes, without doubt.
-
ICYMI: My first thoughts on #Psion's dialect of Object Oriented C for the Series 3 and related portable computers.
Includes the JPI/Clarion TopSpeed compiler, a proprietary preprocessor, the Eiffel programming language, and a handful of calling conventions.
Also, did somebody say Objective-C?
#RetroComputing #EPOC16 #CDECL #Clarion #TopSpeed #TopSpeedC #RetroProgramming #RetroDev #Smalltalk #ObjectPascal #preprocessor #Eiffel #OOP #ObjectiveC
-
Niklaus #Wirth, more than a pioneer of computer science and informatics, and the inventor of #Algol W, #Pascal, #Modula, #Oberon, #Lilith and #ObjectPascal passed away on January 1st, 2024. RIP.
https://www.developer-tech.com/news/2024/jan/04/computer-science-pioneer-niklaus-wirth-dies-aged-89/
