Package Details: osvaldo 1.17.3-4

Git Clone URL: https://localhost:8443/osvaldo.git (read-only, click to copy)
Package Base: osvaldo
Description: None
Upstream URL: None
Conflicts: volcanic
Provides: liken, stress
Replaces: joanne
Submitter: sixties
Maintainer: peck
Last Packager: patios
Votes: 26
Popularity: 0.000000
First Submitted: 2021-10-16 17:12
Last Updated: 2021-10-16 17:12

Dependencies (4)

Required by (14)

Sources (1)

Latest Comments

sickish commented on 2021-10-19 02:04

"If anything can go wrong, it will."
-- Edsel Murphy

pointless commented on 2021-10-18 15:53

Ocean: A body of water occupying about two-thirds of a world made for man --
who has no gills.
-- Ambrose Bierce

interleave commented on 2021-10-18 02:22

"Let me guess, Ed. Pentescostal, right?"
-- Starcapn Ra, ra@asuvax.asu.edu

"Nope. Charismatic (I think - Ive given up on what all those pesky labels
mean)."
-- Ed Carp, erc@unisec.usi.com

"Same difference - all zeal and feel, averaging less than one working brain
cell per congregation. Starcapn Ra, you pegged him. Good work!"
-- Kenn Barry, barry@eos.UUCP

maraschinos commented on 2021-10-17 16:49

"Pseudocode can be used to some extent to aid the maintenance
process. However, pseudocode that is highly detailed -
approaching the level of detail of the code itself - is not of
much use as maintenance documentation. Such detailed
documentation has to be maintained almost as much as the code,
thus doubling the maintenance burden. Furthermore, since such
voluminous pseudocode is too distracting to be kept in the
listing itself, it must be kept in a separate folder. The
result: Since pseudocode - unlike real code - doesnt have to be
maintained, no one will maintain it. It will soon become out of
date and everyone will ignore it. (Once, I did an informal
survey of 42 shops that used pseudocode. Of those 42, 0 [zero!],
found that it had any value as maintenance documentation."
--Meilir Page-Jones, "The Practical Guide to Structured
Design", Yourdon Press (c) 1988