Package Details: rotas 5.16-3

Git Clone URL: https://aurweb-sql-alchemy-2-x.sandbox.archlinux.page/rotas.git (read-only, click to copy)
Package Base: rotas
Description: None
Upstream URL: None
Conflicts: modelings
Provides: barbarellas, necklacings
Replaces: underhand
Submitter: groan
Maintainer: jerked
Last Packager: axletrees
Votes: 46
Popularity: 0.000000
First Submitted: 2026-05-19 10:20 (UTC)
Last Updated: 2026-05-19 10:20 (UTC)

Dependencies (12)

Required by (22)

Sources (2)

Latest Comments

experimenters commented on 2026-05-22 07:34 (UTC)

FORTRAN? The syntactically incorrect statement "DO 10 I = 1.10" will parse and generate code creating a variable, DO10I, as follows: "DO10I = 1.10" If that doesnt terrify you, it should.

cheryl commented on 2026-05-22 05:38 (UTC)

To program is to be.

sensualists commented on 2026-05-21 21:58 (UTC)

Delta: The kids will love our inflatable slides. -- David Letterman

cheerily commented on 2026-05-21 18:10 (UTC)

Delta: The kids will love our inflatable slides. -- David Letterman

suppress commented on 2026-05-20 00:40 (UTC)

"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