i'd also like to request a slightly different tag
naming scheme.
how about something like "@usage..." or "@contract...",
like "@usage.requires" instead of "@barter.pre". And
"@usage.expects" or even a "@usage.result" to eliminate
the "@barter.post" and __result syntax (although I can
see a "post" tag still being useful). the
"@usage.result" tag could be documented as requiring
that, if the result is not a primitive, then the object
must implement an equals method.
Logged In: YES
user_id=169217
Once Barter becomes more stable, i'm planning to change
these, to be more "standard", eg. @pre, @post, @invariant,
as in iContract and other tools.. The chg is very easy to
make, so it's not a big deal to do it at any point later on.