#objectpascal — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #objectpascal, aggregated by home.social.
-
La version 13 de Delphi Community Edition et de C++Builder Community Editions sont sorties hier.
Si vous êtes utilisateur de cette version gratuite de Delphi ou C++Builder vous pouvez faire la mise à jour et bénéficier de leurs nouveautés dont la mise à niveau des SDK pour iOS et Android.
Un renouvellement de votre licence annuelle gratuite sera peut-être nécessaire. Ca se fera pendant le processus de téléchargement.
Pour en savoir plus consultez cette page : https://developpeur-pascal.fr/sortie-de-la-version-13-de-delphi-et-cbuilder-community-edition.html
#Delphi #CBuilder #RADStudio #CommunityEdition #DelphiFree #CBuilderFree #ObjectPascal #Pascal #CPP
-
However, in fixing this I found a different bug. But I don't think it's a problem with my code.
I think #FreePascal's
ParamStr()is using\as an escape character in DOS in certain situations, specifically before a space.For example:
ctran catfile.cat -e c:\sibosdk\include\ -x -c -g...will set the external cat path to
c:\sibosdk\include\ -x.It might also do this in Windows, but I haven't tested it yet.
I need to do more testing, but are any other #Pascal users finding this?
-
However, in fixing this I found a different bug. But I don't think it's a problem with my code.
I think #FreePascal's
ParamStr()is using\as an escape character in DOS in certain situations, specifically before a space.For example:
ctran catfile.cat -e c:\sibosdk\include\ -x -c -g...will set the external cat path to
c:\sibosdk\include\ -x.It might also do this in Windows, but I haven't tested it yet.
I need to do more testing, but are any other #Pascal users finding this?
-
Forget everything you know about Pascal. Blaise is a modern, self-hosting Object Pascal compiler that's taking a 'scorched-earth' approach to legacy, ditching decades of technical debt for a unified ARC memory model and reified generics. While technically sound and forward-thinking, this zero-legacy stance creates a massive chasm for existing Delphi/Free Pascal users, making it a compiler for new…
#technology #blaise #objectpascal
🤖 This post was AI-generated.
-
👏 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 -
👏 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
-
Blaise – A modern self-hosting zero-legacy Object Pascal compiler targeting QBE
https://github.com/graemeg/blaise
#HackerNews #Blaise #ObjectPascal #Compiler #SelfHosting #QBE #OpenSource
-
【Delphi】インターネットから DL したファイルを開こうとすると出る警告を消す
https://qiita.com/ht_deko/items/96d8fcda69701f1e75c1?utm_campaign=popular_items&utm_medium=feed&utm_source=popular_items -
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
-
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
-
vkcube running on 64-bit RISC-V Alpine Linux in my PasRISCV Emulator in turn with the Vulkan-based PasRISCVEmu UI backend. #riscv #vulkan #ObjectPascal #FreePascal #Delphi
@riscv @vulkan -
vkcube running on 64-bit RISC-V Alpine Linux in my PasRISCV Emulator in turn with the Vulkan-based PasRISCVEmu UI backend. #riscv #vulkan #ObjectPascal #FreePascal #Delphi
@riscv @vulkan -
#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
-
#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.
-
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!
-
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!
-
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 performanceSupports 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)
-
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 performanceSupports 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_itemwhich is a very un-Pascal identifier for many reasons. I'm thinking of usingPClassorPsiClassjust to get around it. -
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_itemwhich is a very un-Pascal identifier for many reasons. I'm thinking of usingPClassorPsiClassjust to get around it. -
MCP/Tool-Usage with PALM - Pascal-native LLM interference engine
-
MCP/Tool-Usage with PALM - Pascal-native LLM interference engine
-
【Delphi】Delphi 13 Florence について
https://qiita.com/ht_deko/items/44969a431f0ec8db970f?utm_campaign=popular_items&utm_medium=feed&utm_source=popular_items -
Delphi (Object Pascal) in the Age of AI
https://learndelphi.org/delphi-ai-ultimate-guide/
#HackerNews #Delphi #AI #ObjectPascal #Technology #Innovation
-
Delphi (Object Pascal) in the Age of AI
https://learndelphi.org/delphi-ai-ultimate-guide/
#HackerNews #Delphi #AI #ObjectPascal #Technology #Innovation
-
Découverte d'une BETA de Quartex Pascal IDE from scratch en 2023
-
Pour quelles raisons devrait-on utiliser Delphi et apprendre le Pascal ?
-
Pourquoi ne faut-il pas d'override sur les Create des classes ?
-
A short preview demonstration of PALM with llama3.2 1TB as base model - A Object-Pascal-native LLM engine with inline assembler AVX2 SIMD optimizations, running on the CPU with StreamingLLM-like "endlessly" context-windowing and 8-bit quantized weights and activations (W8A8), and multithreaded/parallelized with my PasMP library. But support for 4-bit weights (for W4A8) is also on the roadmap.
-
A short preview demonstration of PALM with llama3.2 1TB as base model - A Object-Pascal-native LLM engine with inline assembler AVX2 SIMD optimizations, running on the CPU with StreamingLLM-like "endlessly" context-windowing and 8-bit quantized weights and activations (W8A8), and multithreaded/parallelized with my PasMP library. But support for 4-bit weights (for W4A8) is also on the roadmap.
-
【Delphi】環境変数 (が指す先) を Explorer で開く【超初心者向け】
https://qiita.com/ht_deko/items/2b1485aa4f4965c56125?utm_campaign=popular_items&utm_medium=feed&utm_source=popular_items -
【Delphi】TStreamReader / TStreamWriter の使い方
https://qiita.com/ht_deko/items/19a719beac0625674cce?utm_campaign=popular_items&utm_medium=feed&utm_source=popular_items
