Re: [Modeling-users] Raw Qualifiers

[Sebastien B. <sbi...@us...>]

  Thanks a lot Yannick for this nice clarification. I'll probably
include your message as-is in the documentation until I find some time
to rewrite it (I already have quite a bunch of doc. to write, and you
now know what happens when I have too much doc. to write: I had
features, which implies even more doc. to write, but well, that's my
delaying tactics ;).

    Little disgression: the very reason why I made the QualifierParser,
    then documented it only, is historically bound to the somewhat
    complex API for fetching objects; before we get the current
    ec.fetch(), fetching implied qualifierWithQualifierFormat,
    FetchSpecification and ec.objectsWithFetchSpecification(). People
    were not finding it that handy/friendly, imagine their groans if I
    had put on top of that step-by-step instructions to build
    qualifiers!

> So I hope this will help you all to get the best out of the framework.
> The best source of doc is not the doc, the doc may get a bit out of
> synch.  Dive into those sources up to the unit tests.  S=E9bastien works
> hard to get all of those working all the time so you're sure to find a
> lot of working example there.

Writing docs in very time-consuming, and writing *good* doc. is more
then that ;) Hopefully it's not that bad...

About unittests: yes, I maintain then very strictly. Mostly every bug
gets its unittests before being fixed (even if I rarely expose them in
patches), new features get unittests before I start coding, so you can
definitely rely on them.

-- S=E9bastien.