home.social

#object_pascal — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #object_pascal, aggregated by home.social.

  1. #SimSEE is an open platform for the #Simulation of Electric Power Systems.

    With SimSEE, one can analyse the evolution of e.g., volumes of energy, money exchanged by participants in the market, and risk calculations for contracts.

    It is developed in #Object_Pascal with the #Lazarus_IDE.

    simsee.org

  2. is an open platform for the of Electric Power Systems.

    With SimSEE, one can analyse the evolution of e.g., volumes of energy, money exchanged by participants in the market, and risk calculations for contracts.

    It is developed in with the .

    simsee.org

  3. #SimSEE is an open platform for the #Simulation of Electric Power Systems.

    With SimSEE, one can analyse the evolution of e.g., volumes of energy, money exchanged by participants in the market, and risk calculations for contracts.

    It is developed in #Object_Pascal with the #Lazarus_IDE.

    simsee.org

  4. #MEGA is a global project and widely used software for molecular evolutionary and phylogenetic analyses. Originally developed in C++, it has been ported to #Object_Pascal for cross-platform compatibility on #macOS, #Windows, and #Linux.

    doi.org/10.1007/s00239-025-102
    pubmed.ncbi.nlm.nih.gov/412474

  5. is a global project and widely used software for molecular evolutionary and phylogenetic analyses. Originally developed in C++, it has been ported to for cross-platform compatibility on , , and .

    doi.org/10.1007/s00239-025-102
    pubmed.ncbi.nlm.nih.gov/412474

  6. #MEGA is a global project and widely used software for molecular evolutionary and phylogenetic analyses. Originally developed in C++, it has been ported to #Object_Pascal for cross-platform compatibility on #macOS, #Windows, and #Linux.

    doi.org/10.1007/s00239-025-102
    pubmed.ncbi.nlm.nih.gov/412474

  7. The irony: the entire RISC-V base ISA (RV64GC) is beautifully RISC: simple opcodes, fixed 32-bit instructions (+ compressed), load/store architecture, no flags, no implicit state. Then RVV comes along and throws all those principles out the window: global implicit state, microcode-like behavior, variable semantics of the same instruction.

    Because vsetvli changes the semantics of all subsequent V-instructions based on the current VLEN configuration. For a JIT compiler in an Emulator and for an Emulator in general, this means having to continuously track the vtype state and react to any changes, a fundamental contradiction to the principle of statically analyzable instructions. It feels like the RISC-V Foundation sacrificed the simplicity and elegance of the RISC principle to create a powerful but extremely complex "super-SIMD" that is difficult to efficiently map in a JIT. A more traditional SIMD extension with fixed vector widths and clearly defined instruction semantics would have been much more JIT-friendly. The upcoming P extension does go in that direction, but it is primarily targeted at embedded and low-power applications rather than high-performance computing.

    #riscv #riscv64 #emulation #pasriscv #object_pascal #delphi #free_pascal

  8. The irony: the entire RISC-V base ISA (RV64GC) is beautifully RISC: simple opcodes, fixed 32-bit instructions (+ compressed), load/store architecture, no flags, no implicit state. Then RVV comes along and throws all those principles out the window: global implicit state, microcode-like behavior, variable semantics of the same instruction.

    Because vsetvli changes the semantics of all subsequent V-instructions based on the current VLEN configuration. For a JIT compiler in an Emulator and for an Emulator in general, this means having to continuously track the vtype state and react to any changes, a fundamental contradiction to the principle of statically analyzable instructions. It feels like the RISC-V Foundation sacrificed the simplicity and elegance of the RISC principle to create a powerful but extremely complex "super-SIMD" that is difficult to efficiently map in a JIT. A more traditional SIMD extension with fixed vector widths and clearly defined instruction semantics would have been much more JIT-friendly. The upcoming P extension does go in that direction, but it is primarily targeted at embedded and low-power applications rather than high-performance computing.

    #riscv #riscv64 #emulation #pasriscv #object_pascal #delphi #free_pascal

  9. The irony: the entire RISC-V base ISA (RV64GC) is beautifully RISC: simple opcodes, fixed 32-bit instructions (+ compressed), load/store architecture, no flags, no implicit state. Then RVV comes along and throws all those principles out the window: global implicit state, microcode-like behavior, variable semantics of the same instruction.

    Because vsetvli changes the semantics of all subsequent V-instructions based on the current VLEN configuration. For a JIT compiler in an Emulator and for an Emulator in general, this means having to continuously track the vtype state and react to any changes, a fundamental contradiction to the principle of statically analyzable instructions. It feels like the RISC-V Foundation sacrificed the simplicity and elegance of the RISC principle to create a powerful but extremely complex "super-SIMD" that is difficult to efficiently map in a JIT. A more traditional SIMD extension with fixed vector widths and clearly defined instruction semantics would have been much more JIT-friendly. The upcoming P extension does go in that direction, but it is primarily targeted at embedded and low-power applications rather than high-performance computing.

    #riscv #riscv64 #emulation #pasriscv #object_pascal #delphi #free_pascal

  10. The irony: the entire RISC-V base ISA (RV64GC) is beautifully RISC: simple opcodes, fixed 32-bit instructions (+ compressed), load/store architecture, no flags, no implicit state. Then RVV comes along and throws all those principles out the window: global implicit state, microcode-like behavior, variable semantics of the same instruction.

    Because vsetvli changes the semantics of all subsequent V-instructions based on the current VLEN configuration. For a JIT compiler in an Emulator and for an Emulator in general, this means having to continuously track the vtype state and react to any changes, a fundamental contradiction to the principle of statically analyzable instructions. It feels like the RISC-V Foundation sacrificed the simplicity and elegance of the RISC principle to create a powerful but extremely complex "super-SIMD" that is difficult to efficiently map in a JIT. A more traditional SIMD extension with fixed vector widths and clearly defined instruction semantics would have been much more JIT-friendly. The upcoming P extension does go in that direction, but it is primarily targeted at embedded and low-power applications rather than high-performance computing.

    #riscv #riscv64 #emulation #pasriscv #object_pascal #delphi #free_pascal

  11. The irony: the entire RISC-V base ISA (RV64GC) is beautifully RISC: simple opcodes, fixed 32-bit instructions (+ compressed), load/store architecture, no flags, no implicit state. Then RVV comes along and throws all those principles out the window: global implicit state, microcode-like behavior, variable semantics of the same instruction.

    Because vsetvli changes the semantics of all subsequent V-instructions based on the current VLEN configuration. For a JIT compiler in an Emulator and for an Emulator in general, this means having to continuously track the vtype state and react to any changes, a fundamental contradiction to the principle of statically analyzable instructions. It feels like the RISC-V Foundation sacrificed the simplicity and elegance of the RISC principle to create a powerful but extremely complex "super-SIMD" that is difficult to efficiently map in a JIT. A more traditional SIMD extension with fixed vector widths and clearly defined instruction semantics would have been much more JIT-friendly. The upcoming P extension does go in that direction, but it is primarily targeted at embedded and low-power applications rather than high-performance computing.

    #riscv #riscv64 #emulation #pasriscv #object_pascal #delphi #free_pascal

  12. #Trndi is a #glucose monitoring application written in #Object_Pascal. It fetches interstitial sugar readings from continuous glucose monitors (CGM) via different APIs and shows them on the desktop. It also presents a trend over time, colouring, and JavaScript extensions.

    trndi.app

  13. is a monitoring application written in . It fetches interstitial sugar readings from continuous glucose monitors (CGM) via different APIs and shows them on the desktop. It also presents a trend over time, colouring, and JavaScript extensions.

    trndi.app

  14. #Trndi is a #glucose monitoring application written in #Object_Pascal. It fetches interstitial sugar readings from continuous glucose monitors (CGM) via different APIs and shows them on the desktop. It also presents a trend over time, colouring, and JavaScript extensions.

    trndi.app

  15. #Trndi is a #glucose monitoring application written in #Object_Pascal. It fetches interstitial sugar readings from continuous glucose monitors (CGM) via different APIs and shows them on the desktop. It also presents a trend over time, colouring, and JavaScript extensions.

    trndi.app

  16. A Hill Cypher modulo 95 #cryptography method generates a matrix-based key with a quantifiable randomisation algorithm. In a recent paper, the use of random matrices is implemented in an app written in #Object_Pascal with the #Lazarus_IDE.

    doi.org/10.26554/integrajimcs.

  17. A Hill Cypher modulo 95 method generates a matrix-based key with a quantifiable randomisation algorithm. In a recent paper, the use of random matrices is implemented in an app written in with the .

    doi.org/10.26554/integrajimcs.

  18. A Hill Cypher modulo 95 #cryptography method generates a matrix-based key with a quantifiable randomisation algorithm. In a recent paper, the use of random matrices is implemented in an app written in #Object_Pascal with the #Lazarus_IDE.

    doi.org/10.26554/integrajimcs.

  19. PasRISCV now has its own local CLI debugger alongside the GDB remote server. It supports breakpoints, single-stepping, register & memory inspection, and allows simultaneous local CLI and remote GDB sessions. A public debugger API enables future graphical debugger frontends.

    youtu.be/yznijHMKj_0

    #riscv64 #riscv #emulation #pascal #object_pascal #debugger

  20. PasRISCV now has its own local CLI debugger alongside the GDB remote server. It supports breakpoints, single-stepping, register & memory inspection, and allows simultaneous local CLI and remote GDB sessions. A public debugger API enables future graphical debugger frontends.

    youtu.be/yznijHMKj_0

    #riscv64 #riscv #emulation #pascal #object_pascal #debugger

  21. PasRISCV now has its own local CLI debugger alongside the GDB remote server. It supports breakpoints, single-stepping, register & memory inspection, and allows simultaneous local CLI and remote GDB sessions. A public debugger API enables future graphical debugger frontends.

    youtu.be/yznijHMKj_0

    #riscv64 #riscv #emulation #pascal #object_pascal #debugger

  22. PasRISCV now has its own local CLI debugger alongside the GDB remote server. It supports breakpoints, single-stepping, register & memory inspection, and allows simultaneous local CLI and remote GDB sessions. A public debugger API enables future graphical debugger frontends.

    youtu.be/yznijHMKj_0

    #riscv64 #riscv #emulation #pascal #object_pascal #debugger

  23. PasRISCV now has its own local CLI debugger alongside the GDB remote server. It supports breakpoints, single-stepping, register & memory inspection, and allows simultaneous local CLI and remote GDB sessions. A public debugger API enables future graphical debugger frontends.

    youtu.be/yznijHMKj_0

    #riscv64 #riscv #emulation #pascal #object_pascal #debugger

  24. This cross-platform RPN calculator has been written in #Object_Pascal with the #Lazarus IDE for the #Free_Pascal compiler. Source code has been made available.

  25. This cross-platform RPN calculator has been written in with the IDE for the compiler. Source code has been made available.

  26. Issue #126 of the Blaise Pascal Magazine: ZIP puzzle solver in #Pascal, Resizing images, shaped buttons and sprites with #Lazarus and #Object_Pascal, multiple articles on AI and infos to the upcoming Pascal Conference 2025.

    www.blaisepascalmagazine.eu

  27. Issue #126 of the Blaise Pascal Magazine: ZIP puzzle solver in , Resizing images, shaped buttons and sprites with and , multiple articles on AI and infos to the upcoming Pascal Conference 2025.

    www.blaisepascalmagazine.eu

  28. Issue #126 of the Blaise Pascal Magazine: ZIP puzzle solver in #Pascal, Resizing images, shaped buttons and sprites with #Lazarus and #Object_Pascal, multiple articles on AI and infos to the upcoming Pascal Conference 2025.

    www.blaisepascalmagazine.eu

  29. Issue 123/124 of Blaise Pascal Magazine released: #Geocoding with #Pascal, a die-cast simulator for teaching statistics in #Object_Pascal, QUEENS puzzle in Pascal, threading #Free_Pascal code via #WebAssembly in the browser, RTTI in #PAS2JS etc.

    blaisepascalmagazine.eu

  30. Issue 123/124 of Blaise Pascal Magazine released: with , a die-cast simulator for teaching statistics in , QUEENS puzzle in Pascal, threading code via in the browser, RTTI in etc.

    blaisepascalmagazine.eu

  31. Issue 123/124 of Blaise Pascal Magazine released: #Geocoding with #Pascal, a die-cast simulator for teaching statistics in #Object_Pascal, QUEENS puzzle in Pascal, threading #Free_Pascal code via #WebAssembly in the browser, RTTI in #PAS2JS etc.

    blaisepascalmagazine.eu

  32. Issue 123/124 of Blaise Pascal Magazine released: #Geocoding with #Pascal, a die-cast simulator for teaching statistics in #Object_Pascal, QUEENS puzzle in Pascal, threading #Free_Pascal code via #WebAssembly in the browser, RTTI in #PAS2JS etc.

    blaisepascalmagazine.eu

  33. Issue 123/124 of Blaise Pascal Magazine released: #Geocoding with #Pascal, a die-cast simulator for teaching statistics in #Object_Pascal, QUEENS puzzle in Pascal, threading #Free_Pascal code via #WebAssembly in the browser, RTTI in #PAS2JS etc.

    blaisepascalmagazine.eu

  34. MRIcron, a powerful visualisation tool for neuroimaging research, has been written in #Object_Pascal with the #Lazarus_IDE to support platform-sensitive development and to provide a processor-native high-performance software system.

    pubmed.ncbi.nlm.nih.gov/397618

    doi.org/10.1016/j.neuropsychol

  35. MRIcron, a powerful visualisation tool for neuroimaging research, has been written in with the to support platform-sensitive development and to provide a processor-native high-performance software system.

    pubmed.ncbi.nlm.nih.gov/397618

    doi.org/10.1016/j.neuropsychol

  36. For a completely different task, simulating biological feedback loops, #Object_Pascal generates the fastest code. It is not only faster than that of interpreted languages (S/R and Python) but even outperforms fast compiled languages (C++ and Swift).

    #Pascal #programming

    doi.org/10.14201/adcaij.31762

  37. For a completely different task, simulating biological feedback loops, generates the fastest code. It is not only faster than that of interpreted languages (S/R and Python) but even outperforms fast compiled languages (C++ and Swift).

    doi.org/10.14201/adcaij.31762

  38. For a completely different task, simulating biological feedback loops, #Object_Pascal generates the fastest code. It is not only faster than that of interpreted languages (S/R and Python) but even outperforms fast compiled languages (C++ and Swift).

    #Pascal #programming

    doi.org/10.14201/adcaij.31762

  39. #Intracranial pressure is vital for decisions in #neurointensive care. Its dynamics are only partly understood. Computer simulations in #Object_Pascal with Emparcadero #Delphi provide new insights by clarifying the role of the intersitial fluid. doi.org/10.1016/j.bas.2024.102

  40. pressure is vital for decisions in care. Its dynamics are only partly understood. Computer simulations in with Emparcadero provide new insights by clarifying the role of the intersitial fluid. doi.org/10.1016/j.bas.2024.102

  41. Как стать Delphi-программистом за час «для самых маленьких»

    Принято считать, что программирование это сложно, но это миф (все проще чем кажется), и все что нужно чтобы стать программистом это немного упорства и изобретательности. В этой статье мы получим все базовые навыки, которые нужны Delphi программисту (включая базовые знания RunTime, работу с Com-объектами и Canvas, вводом\выводом, файлами, парсингом, ооп, и тд), по окончании статьи. Окунутся в чудесный мир бесконечного скрол

    habr.com/ru/articles/779676/

    #delphi #lazarus #object_pascal #программирование #курс #курсы #десктопная_разработка #авторский_контент

  42. Как стать Delphi-программистом за час «для самых маленьких»

    Принято считать, что программирование это сложно, но это миф (все проще чем кажется), и все что нужно чтобы стать программистом это немного упорства и изобретательности. В этой статье мы получим все базовые навыки, которые нужны Delphi программисту (включая базовые знания RunTime, работу с Com-объектами и Canvas, вводом\выводом, файлами, парсингом, ооп, и тд), по окончании статьи. Окунутся в чудесный мир бесконечного скрол

    habr.com/ru/articles/779676/

    #delphi #lazarus #object_pascal #программирование #курс #курсы #десктопная_разработка #авторский_контент