@Steve_The_Cynic
See my edits above. From the Slackware archives, you can still get the full
Slackware 3.1 install set, including manual pages and source code. The
source for the supplied cron is "Dillon's cron", and the crontab(1) manpage
definitely includes the layout and example crontab I mentioned.
Posts made by toodle
-
RE: Argh, phpDocumentor 3!
-
RE: Argh, phpDocumentor 3!
@Steve_The_Cynic
Slackware 3.1 doesn't use GNU cron or Vixie cron.As far as I can tell, Slackware has always (for some largish value of "always") used Dillon's cron.
Neither the Slackware 3.1 UPGRADE.TXT nor the ChangeLog.txt mention a move to
"Dillon's cron" from any other cron manager. As for the crontab(1) manpage, in 3.1 it included both
a crontab file layout description, and an annotated example of a valid crontab.Perhaps you are thinking of some other distribution?
(edited to reflect found information about Slackware 3.1)
-
RE: Denial of Senses
@GuyWhoKilledBear said in Denial of Senses:
But thinking through a problem algorithmically, and then writing sufficiently detailed/explicit instructions, and how to recognize gaps in instructions and places where they are vague, is a useful skill in other endeavors as well.
It's probably possible to teach this skill to schoolchildren by having them do computer programming exercises.
But then thing you're teaching them isn't "programming" in the sense that most people understand the term, and certainly not in the sense that the article means when it claims to refute that "programming is hard."
Ironically, algorithmic thinking is the hardest part of being a software engineer. It's certainly harder than actually programming.
This! Exactly this!
Coding is relatively easy, once you catch on to the syntax of the language you are working in. Most languages follow common paradigms, with minor variations as to syntax. If you can express an algorithm, you can code it. The hard part is in expressing that algorithm.
There's a vast difference between what people now call "programming" (but I would call "coding") and programming of old: we oldsters were, by circumstance and lack of the all-helpful toolkits now available, forced to learn how to think through a problem "algorithmically".
-
RE: Anyone want to decrypt this SQL Server installation error?
The error seems simple enough, but TRWTF is why SQL Server Setup shows it to you rather than a much simpler and easier to understand message.
If I understand correctly, the error message is telling you that the programmer tried to call a function (Invoke of BeginInvoke) that requires some Windows environment setup, without first performing that setup. This function apparently needs a window handle before it can be invoked, and the program hasn't yet established one.
TRWTF is that the error message isn't helpful to the end-user. It should read something like:
"Because of a failure in communicating with Windows, this program cannot continue.
Please call the helpdesk at 1-800-BAD-CODE and inform them that error 9334-242 has occurred. They will assist in remediation of the error."