#freepascal — Public Fediverse posts

RE: https://oldbytes.space/@thelastpsion/116345290344668595

And the results are in!

1. Pico C
2. Rust
3. Free Pascal
4. 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!

1. Pico C
2. Rust
3. Free Pascal
4. 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!

1. Pico C
2. Rust
3. Free Pascal
4. 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!

1. Pico C
2. Rust
3. Free Pascal
4. 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!

1. Pico C
2. Rust
3. Free Pascal
4. 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

AOC 2025 day 3 is when I start to realize that my usual tool sets in #Pascal or #Go have a lot of string handling functions that I just don't see in #Forth. I'm building up some tools and have a few competing versions of tfunctions that either take different approaches, use different parameter formats, and/or return formats. But I don't want to re-implement the left, right, mid string functions without being sure that's the way to go.

I'm getting a lot of "off by one" errors.

Some are caused by my Pascal "it's a subscript, damn it" bias, and others by not using the right looping constructs.

Strings in Forth are a beginning address and a length. The length can be a maximum size available or the length of the current string. There's no dynamism here, nothing like AnsiStrings in #FreePascal. There are some conventional buffers that the standard definitions will not touch (the PAD) and other transient buffers that can be used with care.

'Tis what I signed up for. It's fun. Kinda. :)

#programming

Has anyone managed to get #NeoVim with #DAP and #gdb working with #Pascal?

I'm using #LazyVim, so a lot of DAP is preconfigured using an Extra (dap.core). Unsurprisingly, Pascal is not one of the languages supported by default.

#ObjectPascal #FreePascal #debugger

Has anyone managed to get #NeoVim with #DAP and #gdb working with #Pascal?

I'm using #LazyVim, so a lot of DAP is preconfigured using an Extra (dap.core). Unsurprisingly, Pascal is not one of the languages supported by default.

#ObjectPascal #FreePascal #debugger

Has anyone managed to get #NeoVim with #DAP and #gdb working with #Pascal?

I'm using #LazyVim, so a lot of DAP is preconfigured using an Extra (dap.core). Unsurprisingly, Pascal is not one of the languages supported by default.

#ObjectPascal #FreePascal #debugger

Has anyone managed to get #NeoVim with #DAP and #gdb working with #Pascal?

I'm using #LazyVim, so a lot of DAP is preconfigured using an Extra (dap.core). Unsurprisingly, Pascal is not one of the languages supported by default.

#ObjectPascal #FreePascal #debugger

Has anyone managed to get #NeoVim with #DAP and #gdb working with #Pascal?

I'm using #LazyVim, so a lot of DAP is preconfigured using an Extra (dap.core). Unsurprisingly, Pascal is not one of the languages supported by default.

#ObjectPascal #FreePascal #debugger

A deep and wide exposure on internet and computing technologies in early 2000s left me with very specific design taste and UI choices

Yes, I am looking for small XM music for this little baby. If anyone wants to compose something fresh up to 50KB and working with uFMOD plz leave a comment

There will be a little gfx widget above with effects and scroller

Yes, it’s a real ~80KB executable running on actual Windows 7 (works on XP too). #FreePascal makes it a bit more bearable to work with WinAPI

Gedanken zu systemnaher Software, exotischen Programmiersprachen und warum nicht jedes Problem ein Framework braucht.

https://blog.jakobs.systems/micro/20260115-warum-purebasic-freebasic-lazarus/

#Developer #Purebasic #freepascal #lazarus #Framework #Software #Softwareentwickler

I've been working on an AD&D2e dungeon master toolkit gui application thingy in FreePascal/Lazarus this week. I'm using the Qt widget set, and documented a few obscure hacky things like loading embedded fonts and qss stylesheets baked into the executable, mapping LCL controls to their Qt equivalent, and accessing the underlying Qt bits of LCL components, etc....

There isn't much info about this on the wiki's (probably because it's hacky AF and not a particularly intended use case) - in any event, have at it:

gopher://gopher.linkerror.com:70/1/pascal

#freepascal #lazarus #dungeonsanddragons #dnd

How come the #Amiga has like 4 different „distributions” of #GCC (the infamous 2.95.3, bebbo's 8.x, the weird 13.x from Bartman/Abyss which is binary only and spits ELFs and whatever else I forgot) but each of these is so inconvenient to install and work with?

Yet, somehow, #FreePascal seems to built itself in crosscompiler mode for m68k/amiga on every host I put it on, not crying like a baby about everything.

Things I'd like to achieve next year

...with zero pressure - just stuff I'd like to do if I get the chance

• Get as many of the #Psion SIBO C SDK apps rewritten as possible. I really enjoy using #FreePascal for this! It's vastly underrated for writing cross-platform CLI apps.
• Make some code run on #EPOC16 from a tiny/toy #compiler of my own. Not an entire C compiler, just something where I've generated some 8086 (or NEC V30) assembly from something very basic that actually runs, including implementing the TopSpeed calling convention.
• Work out how the #MAME debugger works so that I can add 4MB RAM support to EPOC16. Maybe learn some things about the internals of EPOC16 along the way. Eventually write this updated EPOC16 ROM to flash and get it running on real hardware.
• Make a #PsiDrive PCB that can write to flash drives. Just needs a +16V boost converter added to the board.
• Get an #RP2350 to pretend to be a small Psion SSD, using the on-die RAM and PIO. Bonus if it uses a battery. Extra bonus if it can write to external RAM or Flash.
• Move #libsibo away from the Arduino libraries and over to the Pico SDK. This just feels like the right move, but means I'll need to learn cmake as well.
• Learn how to write good unit tests. It's not a problem with learning frameworks - both fptest and fpcunit are simple enough. My brain is freezing when trying to decide on what to test and why. I know my code will improve once I've grasped this.

There are a lot of moving parts to all of these. Some need me to learn multiple sub-skills, such as 8086 assembly. Like I said, this isn't a list of Things Alex Must Get Done Next Year. I'd be happy if I achieved just one of them.

I'm curious... Which one of these would you like to see the most?

#retrocomputing

Things I'd like to achieve next year

...with zero pressure - just stuff I'd like to do if I get the chance

• Get as many of the #Psion SIBO C SDK apps rewritten as possible. I really enjoy using #FreePascal for this! It's vastly underrated for writing cross-platform CLI apps.
• Make some code run on #EPOC16 from a tiny/toy #compiler of my own. Not an entire C compiler, just something where I've generated some 8086 (or NEC V30) assembly from something very basic that actually runs, including implementing the TopSpeed calling convention.
• Work out how the #MAME debugger works so that I can add 4MB RAM support to EPOC16. Maybe learn some things about the internals of EPOC16 along the way. Eventually write this updated EPOC16 ROM to flash and get it running on real hardware.
• Make a #PsiDrive PCB that can write to flash drives. Just needs a +16V boost converter added to the board.
• Get an #RP2350 to pretend to be a small Psion SSD, using the on-die RAM and PIO. Bonus if it uses a battery. Extra bonus if it can write to external RAM or Flash.
• Move #libsibo away from the Arduino libraries and over to the Pico SDK. This just feels like the right move, but means I'll need to learn cmake as well.
• Learn how to write good unit tests. It's not a problem with learning frameworks - both fptest and fpcunit are simple enough. My brain is freezing when trying to decide on what to test and why. I know my code will improve once I've grasped this.

There are a lot of moving parts to all of these. Some need me to learn multiple sub-skills, such as 8086 assembly. Like I said, this isn't a list of Things Alex Must Get Done Next Year. I'd be happy if I achieved just one of them.

I'm curious... Which one of these would you like to see the most?

#retrocomputing

Things I'd like to achieve next year

...with zero pressure - just stuff I'd like to do if I get the chance

• Get as many of the #Psion SIBO C SDK apps rewritten as possible. I really enjoy using #FreePascal for this! It's vastly underrated for writing cross-platform CLI apps.
• Make some code run on #EPOC16 from a tiny/toy #compiler of my own. Not an entire C compiler, just something where I've generated some 8086 (or NEC V30) assembly from something very basic that actually runs, including implementing the TopSpeed calling convention.
• Work out how the #MAME debugger works so that I can add 4MB RAM support to EPOC16. Maybe learn some things about the internals of EPOC16 along the way. Eventually write this updated EPOC16 ROM to flash and get it running on real hardware.
• Make a #PsiDrive PCB that can write to flash drives. Just needs a +16V boost converter added to the board.
• Get an #RP2350 to pretend to be a small Psion SSD, using the on-die RAM and PIO. Bonus if it uses a battery. Extra bonus if it can write to external RAM or Flash.
• Move #libsibo away from the Arduino libraries and over to the Pico SDK. This just feels like the right move, but means I'll need to learn cmake as well.
• Learn how to write good unit tests. It's not a problem with learning frameworks - both fptest and fpcunit are simple enough. My brain is freezing when trying to decide on what to test and why. I know my code will improve once I've grasped this.

There are a lot of moving parts to all of these. Some need me to learn multiple sub-skills, such as 8086 assembly. Like I said, this isn't a list of Things Alex Must Get Done Next Year. I'd be happy if I achieved just one of them.

I'm curious... Which one of these would you like to see the most?

#retrocomputing

Things I'd like to achieve next year

...with zero pressure - just stuff I'd like to do if I get the chance

• Get as many of the #Psion SIBO C SDK apps rewritten as possible. I really enjoy using #FreePascal for this! It's vastly underrated for writing cross-platform CLI apps.
• Make some code run on #EPOC16 from a tiny/toy #compiler of my own. Not an entire C compiler, just something where I've generated some 8086 (or NEC V30) assembly from something very basic that actually runs, including implementing the TopSpeed calling convention.
• Work out how the #MAME debugger works so that I can add 4MB RAM support to EPOC16. Maybe learn some things about the internals of EPOC16 along the way. Eventually write this updated EPOC16 ROM to flash and get it running on real hardware.
• Make a #PsiDrive PCB that can write to flash drives. Just needs a +16V boost converter added to the board.
• Get an #RP2350 to pretend to be a small Psion SSD, using the on-die RAM and PIO. Bonus if it uses a battery. Extra bonus if it can write to external RAM or Flash.
• Move #libsibo away from the Arduino libraries and over to the Pico SDK. This just feels like the right move, but means I'll need to learn cmake as well.
• Learn how to write good unit tests. It's not a problem with learning frameworks - both fptest and fpcunit are simple enough. My brain is freezing when trying to decide on what to test and why. I know my code will improve once I've grasped this.

There are a lot of moving parts to all of these. Some need me to learn multiple sub-skills, such as 8086 assembly. Like I said, this isn't a list of Things Alex Must Get Done Next Year. I'd be happy if I achieved just one of them.

I'm curious... Which one of these would you like to see the most?

#retrocomputing

Things I'd like to achieve next year

...with zero pressure - just stuff I'd like to do if I get the chance

• Get as many of the #Psion SIBO C SDK apps rewritten as possible. I really enjoy using #FreePascal for this! It's vastly underrated for writing cross-platform CLI apps.
• Make some code run on #EPOC16 from a tiny/toy #compiler of my own. Not an entire C compiler, just something where I've generated some 8086 (or NEC V30) assembly from something very basic that actually runs, including implementing the TopSpeed calling convention.
• Work out how the #MAME debugger works so that I can add 4MB RAM support to EPOC16. Maybe learn some things about the internals of EPOC16 along the way. Eventually write this updated EPOC16 ROM to flash and get it running on real hardware.
• Make a #PsiDrive PCB that can write to flash drives. Just needs a +16V boost converter added to the board.
• Get an #RP2350 to pretend to be a small Psion SSD, using the on-die RAM and PIO. Bonus if it uses a battery. Extra bonus if it can write to external RAM or Flash.
• Move #libsibo away from the Arduino libraries and over to the Pico SDK. This just feels like the right move, but means I'll need to learn cmake as well.
• Learn how to write good unit tests. It's not a problem with learning frameworks - both fptest and fpcunit are simple enough. My brain is freezing when trying to decide on what to test and why. I know my code will improve once I've grasped this.

There are a lot of moving parts to all of these. Some need me to learn multiple sub-skills, such as 8086 assembly. Like I said, this isn't a list of Things Alex Must Get Done Next Year. I'd be happy if I achieved just one of them.

I'm curious... Which one of these would you like to see the most?

#retrocomputing

@venelles the free pascal ide 😉

#freepascal

Gerade gestern wieder mit @me_ diskutiert¹:
mit dem ganzen Python überall² haben unsere Studies keine Ahnung mehr, was Pointer, Stack und Heap wirklich sind, und wie sie sich anfühlen.

Und ich komm da³ immer wieder zurück zu #FreePascal: ich hab starke⁴ statische Typisierung, Referenzen⁵, Call by Value und Call by Reference, Stack und Heap⁶, und bei Bedarf auch Klassen und Objekte.

__
¹der eine hardware-nähere Sicht drauf hat als ich
²nichts gegen dynamische Programmiersprachen, ich komm von Scheme (und Perl) und mach fast alles in Ruby, ich werd nur mit Python überhaupt nicht warm.
³didaktisch sinnvolle statisch typisierte Sprachen
⁴im Gegensatz zu C, was schwach typisiert ist
⁵kontrollierte Pointer
⁶sichtbar, in FP kann ich bei Bedarf meinen eigenen Memory Manager schreiben.

Dear Friends of ye olden days (well last year actually),

One of the things about the #Fediverse and the cyber-verse and other poems. Is with verse no one knows wot the poets are

About.

Are they in Devon are they in Hell
oberine
those dumbed elusive pimple-knickers

Well I am seeking They there and hear
and I can tell you
I am not a bot or AI in dis
guise.
AND I know Nothing. N O T H I N G!

Fortunately I have a cunning plan
as unusual as any quitter critter:

1) Be Tue or better still True 2 the best ideals and practices you know
2) Find your old HTML, programming even if unavailable
3) Deliberately make mistakes except in programming

For example:

Yesterday I programmed in #FreePascal #Python and #HTML
Today I will be looking for a python compiler. I am using Thonny IDE
for now

I did not know I was on this instance/server.
Thank the admins for all their work AND send them some monies.
Personally I am presently broke from whining, women and sung

Have a great day everyone and remember. Survival is our superpower.

❤️🎉🦞

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)

#ObjectPascal #Delphi #FreePascal #LLM #AI

Yesterday, in an attempt to avoid all sorts of responsibilities, I started pulling apart another #Psion SIBO C SDK tool.

ECOBJ.EXE takes an Intel OMF file (.OBJ) for a class and moves the class descriptor data into the code segment. Unlike #CTRAN, I have absolutely no docs on how it does this. I also have no experience with the object file format.

This has never stopped me before.

So, armed with a hex editor, a PDF documenting OMF (link below), and my beloved #Pascal, I've set to work.

So far, so good!

https://www.azillionmonkeys.com/qed/Omfg.pdf

#Pascal #FreePascal #16bit #DOSBox #DOSBoxStaging #RetroComputing #RetroDev

Yesterday, in an attempt to avoid all sorts of responsibilities, I started pulling apart another #Psion SIBO C SDK tool.

ECOBJ.EXE takes an Intel OMF file (.OBJ) for a class and moves the class descriptor data into the code segment. Unlike #CTRAN, I have absolutely no docs on how it does this. I also have no experience with the object file format.

This has never stopped me before.

So, armed with a hex editor, a PDF documenting OMF (link below), and my beloved #Pascal, I've set to work.

So far, so good!

https://www.azillionmonkeys.com/qed/Omfg.pdf

#Pascal #FreePascal #16bit #DOSBox #DOSBoxStaging #RetroComputing #RetroDev

Yesterday, in an attempt to avoid all sorts of responsibilities, I started pulling apart another #Psion SIBO C SDK tool.

ECOBJ.EXE takes an Intel OMF file (.OBJ) for a class and moves the class descriptor data into the code segment. Unlike #CTRAN, I have absolutely no docs on how it does this. I also have no experience with the object file format.

This has never stopped me before.

So, armed with a hex editor, a PDF documenting OMF (link below), and my beloved #Pascal, I've set to work.

So far, so good!

https://www.azillionmonkeys.com/qed/Omfg.pdf

#Pascal #FreePascal #16bit #DOSBox #DOSBoxStaging #RetroComputing #RetroDev

Yesterday, in an attempt to avoid all sorts of responsibilities, I started pulling apart another #Psion SIBO C SDK tool.

ECOBJ.EXE takes an Intel OMF file (.OBJ) for a class and moves the class descriptor data into the code segment. Unlike #CTRAN, I have absolutely no docs on how it does this. I also have no experience with the object file format.

This has never stopped me before.

So, armed with a hex editor, a PDF documenting OMF (link below), and my beloved #Pascal, I've set to work.

So far, so good!

https://www.azillionmonkeys.com/qed/Omfg.pdf

#Pascal #FreePascal #16bit #DOSBox #DOSBoxStaging #RetroComputing #RetroDev

Yesterday, in an attempt to avoid all sorts of responsibilities, I started pulling apart another #Psion SIBO C SDK tool.

ECOBJ.EXE takes an Intel OMF file (.OBJ) for a class and moves the class descriptor data into the code segment. Unlike #CTRAN, I have absolutely no docs on how it does this. I also have no experience with the object file format.

This has never stopped me before.

So, armed with a hex editor, a PDF documenting OMF (link below), and my beloved #Pascal, I've set to work.

So far, so good!

https://www.azillionmonkeys.com/qed/Omfg.pdf

#Pascal #FreePascal #16bit #DOSBox #DOSBoxStaging #RetroComputing #RetroDev

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.

#Pascal #FreePascal

Web Development in… Pascal? https://hackaday.com/2025/10/28/web-development-in-pascal/ #SoftwareDevelopment #webdevelopment #freepascal #Pascal #webdev

Web Development in… Pascal? - If you were asked to make an e-commerce website in 2025, what language would you r... - https://hackaday.com/2025/10/28/web-development-in-pascal/ #softwaredevelopment #webdevelopment #freepascal #pascal #webdev

SedaiBasic Interpreter Performance
#SedaiBasic #FreePascal #Commodore128 #BASICProgramming #OpenSource #RetroComputing #VirtualMachine
https://theoasisbbs.com/sedaibasic-interpreter-performance/?feed_id=6019&_unique_id=68fa2936dca14

MCP/Tool-Usage with PALM - Pascal-native LLM interference engine

https://youtu.be/lml0V0zooLM

#mcp #ai #llm #objectpascal #delphi #fpc #freepascal

@thelastpsion @zeitverschreib I haven't heard about even a single use of #FreePascal in commercial software. There are people using Embarcadero #Delphi (former Borland Delphi), but that result of keeping certain _tradition_ in the business. But #Embarcadero still sells licenses for it.

@thelastpsion @zeitverschreib I haven't heard about even a single use of #FreePascal in commercial software. There are people using Embarcadero #Delphi (former Borland Delphi), but that result of keeping certain _tradition_ in the business. But #Embarcadero still sells licenses for it.

@thelastpsion @zeitverschreib I haven't heard about even a single use of #FreePascal in commercial software. There are people using Embarcadero #Delphi (former Borland Delphi), but that result of keeping certain _tradition_ in the business. But #Embarcadero still sells licenses for it.

@thelastpsion @zeitverschreib I haven't heard about even a single use of #FreePascal in commercial software. There are people using Embarcadero #Delphi (former Borland Delphi), but that result of keeping certain _tradition_ in the business. But #Embarcadero still sells licenses for it.

@thelastpsion @zeitverschreib I haven't heard about even a single use of #FreePascal in commercial software. There are people using Embarcadero #Delphi (former Borland Delphi), but that result of keeping certain _tradition_ in the business. But #Embarcadero still sells licenses for it.

Adding the keyboard input routines to the emulator took a bit more work. Mostly trying to find the correct routines in #FreePascal (KeyPressed and ReadKey). (Read and Readln are both buffered - they read a line and only return when the user hits enter).

#quiche #quichelang #compiler #z80

I thought it might be a good idea to reach to the basics trying to debug that #FreePascal bug which makes even simplest programs fail to run on i8086/msdos (my #TP7 game port still “”works””, until it reaches #DOS API calls). So thought it might be possible to target the #8086 and run #MartyPC by @gloriouscow

While I pretty much know that the code jumps somewhere randomly and then goes along executing emptiness, I still need to find out why…
and how to set breakpoints on INTs :p

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.

https://www.youtube.com/watch?v=LnKCiIdWqvg

#llm #objectpascal #pascal #freepascal #delphi #llama #ai

@babble_endanger #FreePascal runs on #MSDOS, 9x, XP and up, #PowerPC MacOS and lots more. Heck, VisualBasic 6 #VB6 runs on 9x thru Win11 and is more stable an ABI on #Linux via Wine than Linux apps have. #Rust ’s problem is a matter of will; a turning up of the nose of anything that isn’t “current” — a moniker they haven’t realised they don’t control; that’s in the hands of Microsoft, Apple, Google etc.

Before I got sidetracked into the type system I was working to get the command line compiler fully up and running.

The sticking point was command line arguments. I tried using #FreePascal's built in parser but it didn't have the flexibility I needed. I've now written something which does and I can now set the platform and deployment options.

#quiche #quichelang #compiler #pascal #z80

1/n

Калькулятор из iPhone в ReactOS

Я продолжаю изучать программирование. В этот раз моей затеей стал перенос калькулятора из iPhone в ReactOS. В этой статье я расскажу о том, как я переносила калькулятор из iPhone на ReactOS.

https://habr.com/ru/articles/908530/

#freepascal #lazarus #lazarus_40 #lazarus_ide #reactos

The Lazarus IDE for Free Pascal has been launched in version 4.0. This major new release introduces multiple novel features, including new event types, extended support for Cocoa, optional docking, more debugger options and extended components.

#Lazarus_IDE #FreePascal

https://www.lazarus-ide.org

Vi aspetto sul canale "CompilaQuindiVa" per esplorare insieme #Lazarus, l'IDE open-source basato su #FPC (#FreePascal Compiler) e ispirato a #Delphi.
👉 https://twitch.tv/compilaquindiva

Cosa proveremo a fare di bello durante questa live?
✔ Download e installazione di Lazarus
✔ Configurazione dell’ambiente di sviluppo
✔ Creazione del primo progetto
✔ Design rapido della UI
✔ Compilazione, debugging e quant'altro

📣 Condividi questo post con amici e colleghi: più siamo, più ci divertiamo!

A presto! 👨‍💻✨

Finally - FINALLY - unit tests in #FreePascal make sense. As usual, it was a few tiny details that I couldn't quite grasp. Someone (@jbmorley) very kindly took the time to walk me though, and now I'm all set to test and refactor #CTRAN!

FYI: I'm using FPTest, which has a much nicer CLI output that FPCUnit.

#CTRAN 0.0.2 is out!

OK, I know no one is using this, but I'm going to shout about it anyway. For those who don't know, this is my rewrite of #Psion's proprietary OO C preprocessor. It takes class definition files and spits out "pure" C or TASM.

This release doesn't add much beyond a handful of bug fixes. However, it is significantly faster than 0.0.1 thanks to using more of #FreePascal's classes and generics.

#RetroComputing #RetroDev #Pascal #ObjectPascal

https://github.com/thelastpsion/ctran/releases/tag/0.0.2