Re: Is the Documentation In a spec File Usually Enough For You ?

["Randy Brukardt" <randy@rrsoftware.com>]

"AdaMagica" <christ-usch.grein@t-online.de> wrote in message 
news:80e23f09-06ac-4112-9b7f-e765266a952d@googlegroups.com...
...
> If I were looking for password generators, I would not waste my time
>in trying some that don't claim to produce good ones; instead I'd pick
>one with such a claim and test it thoroughly.

I'd also want some documentation as to what the author considers a "good" 
password, as the advice for that seems to change every few years. I'd guess 
that this package was based on some advice from a few years ago, so it might 
not even be "good" anymore. (That's certainly the case with a lot of Ada 
libraries, which haven't been modified for a long time as no one has seen a 
need to do so.)

After all, "good" is not a technical term, in any field that I'm aware of.

Certainly, you don't need to put this sort of documentation on individual 
subprograms; it belongs to the library as a whole. But without it, you 
really can't judge fitness.

                                        Randy.