The Last Psion | Alex
Qiita - 人気の記事公式・準公式の Delphi 関連書籍を読んでみる
https://qiita.com/ht_deko/items/8ceac34e07eca0732e9f?utm_campaign=popular_items&utm_medium=feed&utm_source=popular_items
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.
The Eclectic Light CompanyText, strings and Unicode
https://fed.brid.gy/r/https://eclecticlight.co/2026/01/03/text-strings-and-unicode/
Présentations et conférences en lignePour quelles raisons devrait-on utiliser Delphi et apprendre le Pascal ?
Pour quelles raisons devrait-on utiliser Delphi et apprendre le Pascal ?
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!
【Delphi】RAD Studio コマンドプロンプトについて
https://qiita.com/ht_deko/items/f65e752d3f97257512c2?utm_campaign=popular_items&utm_medium=feed&utm_source=popular_items
Pourquoi ne faut-il pas d'override sur les Create des classes ?
Pourquoi ne faut-il pas d'override sur les Create des classes ?
Benjamin Rosseaux 
PasLLM is finally publicly released!
A high-performance LLM inference engine written in pure Object Pascal.
✨ No Python dependencies
🎯 Advanced 4-bit quantization
🖥️ Cross-platform (Delphi & FreePascal)
⚡ Native performance
Supports Llama 3.x, Qwen, Phi-3, Mixtral, DeepSeek R1 & more!
Open source (AGPL 3.0): https://github.com/BeRo1985/pasllm (synced from my private repo on my on server)
If you were writing a #compiler (or, in my case, a #preprocessor) and you had to think of a variable name for a "class" struct, but you can't use the keyword class... what would you call that variable?
Plot twist: The compiler/preprocessor is written in #ObjectPascal. (So it's actually a record, not a struct. Same difference.)
I'm currently using the variable name class_item which is a very un-Pascal identifier for many reasons. I'm thinking of using PClass or PsiClass just to get around it.