lealanko

5 ms·

1.
by lealanko 11mo ago
This is a common problem with try-catch syntax. An alternative, and arguably more useful syntax would be try (File_handle fh {s, "r"}) { // use fh } unless (const File_error& e) { // handle er
2.
by lealanko 5y ago
For a more detailed look at the timeline of a programming language feature in the same vein, you may also enjoy the retrospective on Foozles: https://wiki.hh.se/wg211/images/5/58/Foozles.pdf
3.
by lealanko 6y ago
You (and the article) are ignoring smaller companies. In those, you often have the salary negotiations with the owner, or a partner. Your salary comes (effectively) out of their own pocket, and recruiting you is quite possibly a significant
4.
by lealanko 9y ago
Author here (of the plugin, not the page). This was my only tangible contribution to the Gimp, some twenty years ago. IIRC it was modelled after a similar feature in Paint Shop Pro, and it was easy enough an exercise for an aspiring program
5.
by lealanko 10y ago
Probably just a screen capture snafu. The final game (and even QTest1) had an adjustable gamma setting.
6.
by lealanko 10y ago
They also released some 640x480 screenshots. They are included in Romero's post (fourth row), but that may not be obvious due to scaling. See the originals at http://doomgate.gamers.org/games/quake/screens.htm
7.
by lealanko 11y ago
Do I understand correctly that the load-time code specialization described in this presentation is not inherent to the Mill hardware, but instead merely a proposed OS-level mechanism for supporting binaries that are portable across the mode
8.
by lealanko 11y ago
The problem with automatic daemonization is that there is no way to indicate startup failure: you just fire and forget the process in the background. If the process dies, there's no clear way of knowing whether it was due to an error i