The compiler maintains a database of caller information. The editor uses this information to let you edit each of the callers of a function. As a result, you don't need concordances, program listings, or separate CREF (cross-reference) programs. The compiler maintains a database of source location information, which the editor uses to let you edit functions by name. The Debugger uses the source location information to offer single key com- mands that invoke the editor on the function for the current stack frame. As a result, you are freed from awareness of the names of files or particular file structures involved in any software project. The compiler maintains a database of argument list information that the editor, Debugger, Lisp Listener, and other tools use to offer fast online help concerning arguments. You do not need to memorize details of call sequences since you can always check quickly when you need to know. The editor maintains a structured view of source code information, enabling it to offer commands for compiling only the definitions that have changed in any particular buffer. You can make a number of related source changes and then ask to compile only the definitions that have changed. During compilations, the compiler maintains a database of warnings and messages. The editor uses this database to offer a command for dealing with the warnings. It puts the message in one buffer and the relevant source code in another. That way, you are freed from the burden of writing down errors or having to find the relevant definitions manually. The configuration manager, SCT, maintains a database of the file names and file versions that constitute any software system and of the various compile- and load-time dependencies between the files. This database is used in full system compilations, in incremental patching, in system distribution, and so on. As a result, you are freed from manual operations and potential costly errors in shipping software products. In addition, many operations can be performed on "a system" without your needing to remember any of the files that it contains.
Lisp
SSS (Supreme Sexp System) releases a polished v3.3.22 after 9 months of continuous development ✨
https://codeberg.org/jjba23/sss
- #dracula palette has been added as shown in the #screenshot
- experimental help center 🧪 for SSS, tailor made #gtk4 #rust application
- many improvements and quality of life added to this #gnu #linux quasi - #distro on top of #guix
- much more ...
SSS is a #rice 🖥️ 🍙 worthy of #unixporn and uses #guile #scheme #emacs #hyprland and more
cross-posted from: https://lemmy.ml/post/34572963
SSS (Supreme Sexp System) releases a polished v3.3.22 after 9 months of continuous development ✨
https://codeberg.org/jjba23/sss
- #dracula palette has been added as shown in the #screenshot
- experimental help center 🧪 for SSS, tailor made #gtk4 #rust application
- many improvements and quality of life added to this #gnu #linux quasi - #distro on top of #guix
- much more ...
SSS is a #rice 🖥️ 🍙 worthy of #unixporn and uses #guile #scheme #emacs #hyprland and more
cross-posted from: https://lemmy.ml/post/33466232
Introducing Veritas v0.0.20: my new Lisp-powered (Guile Scheme) testing framework!
https://codeberg.org/jjba23/veritas
Born from my engineering experience and frustrations, I aim for incredible expressiveness. It is currently super early stages, also eager for other people to pitch in ideas before fully stabilizing the API. I also want to add many more capabilities for integration tests, containers and more.
veritas aims to be a simple and lightweight testing framework written in Scheme. Its main purpose is to help developers verify that their code behaves as expected. It achieves this by providing a clear structure for writing tests and producing easy-to-read feedback in various formats.
The framework is built around the concepts of "suites," which group related "tests," and "assertions," which perform the actual checks. I'd encourage you to peruse the test/ folder of this project to see real examples of how to use veritas.
The power of veritas lies in its simplicity, expressive embedded domain-specific language (EDSL), and some clever features that promote robust testing practices and correctness, like order randomization and concurrent testing.
cross-posted from: https://lemmy.ml/post/30485676
Generate SVG images for handy useful glyphs, org/markdown badges and more, from Lisp (Guile Scheme)
https://codeberg.org/jjba23/ggg
Be proud and appreciate technologies and techniques you use, distinguish clearly supported versions of things, etc. With flexible support for badges between one and three parts.
Through SVG generation from Lisp (Guile Scheme) we leverage a beautiful DSL and apply some mathematical knowledge to build pixel perfect badges. These SVG can then be easily converted without quality loss to any desired format.
With GGG, you have the power to create your own badges and images with a consistent and clean aesthetic.
als kruisbericht geplaatst vanaf: https://lemmy.ml/post/29897788
LucidPlan proudly announces version v0.4.0 of the project:
https://codeberg.org/jjba23/lucidplan
#foss #project #management for everyone ( #selfhosting )
work more #agile in your team thanks to a fast-paced no-nonsense-workflow and customizability, also thanks to being written in #lisp ( #guile #scheme ) and using #guix
This tool results of years of experience using proprietary systems like Jira/Trello, and experiencing the frustrations they bring.
find my live instance here:
