Solar's Development Home
About DEV
This is Solar's Development Home. Effectively a subdomain dedicated to all things related to programming and software engineering.
What's in here?
TEFKAPP
In April 2001, it became clear to me that my favourite computer OS / platform (Amiga) was going nowhere. The immediate future of operating systems would be divided between Windows and Linux, a dreary prospect.
Later that year I initiated a project somewhat presumptuously named "Project for a Perfect Operating System" (Pro-POS). It differed from many other hobbyist OS development projects in its ambitious goals and, ultimately, its very limited progress when I pulled the plug on Pro-POS mid-2004.
Only a few documents, concepts and ideas remain from that project, which I preserved here.
Note: None of these documents were quite finished when Pro-POS called quits, and they do not necessarily represent what I would write on these subjects today.
Misc. Source
There are many tiny scripts and mini-projects that have accumulated on my hard drive; I use the Subversion repository attached to this Trac to store them off-site in case my hard drive dies violently (and for the odd reference lookup - "how did I do that again?" - you know the kind).
Unless otherwise noted, all my sources are released under the PDCLib License (i.e., Public Domain for all practical purposes except in name due to a braindead restriction in German copyright law).
A tool to help organizing a project with many sub-components in a Subversion repository. Click the title for the project page, or check out via SVN here. Status: Concept Phase
A small cashier script to help my wife (or rather, the friends of the local kindergarten) with a large garage sale. Rather hack-ish, but will serve the purpose, and much better than any of the pen-and-paper or Excel stuff they were planning. I might polish this into general usefulness if boredom strikes. SVN repo is here. Status: Alpha
A frequently-used C++ macro that facilitates generating a std::string from anything that supports operator<<( ostream &, ... ). Including explanations as to why it has to be done this way and no other.
Being fed up with lots of different machines giving me lots of different default VIM configurations, I finally got my act together and started coming up with my own .vimrc file...
Something that makes product support really difficult is if the interesting output from the customer's script run doesn't end up in the logfile (or the logfile says something different from what the customer saw). Especially if the customer already closed the window and can only tell you what he saw from the back of his head. Fortunately, there's a very easy way to make sure you catch all of your script's output.
...under construction.
Rants and References
Some things I've written so often, in various contexts, that I felt I should write them up once in a central place and merely provide a link when the subject comes up again.
This is the place.
Web Links
Some useful links I want to keep.
- I/O Streams in Standard C++
- ''Easy'' Automated Snapshot-Style Backups with Linux and Rsync
- Everything you ever wanted to know about nullptr
- why GNU grep is fast / string searching algorithms
- Calling conventions for different C++ compilers and operating systems
- Unicode-processing issues in Perl and how to cope with it
- Jon Skeet: Inheritance tax
Can I join?
There's nothing to be joined here. Consider this a static personal homepage that happens to run on a dynamic backend (so I can better edit it).
