Refresh of README's

[cary-ilm]

• revised the info in the top-level README
• condensed the info in the module README's
• removed the project-specific AUTHORS, NEWS, ChangeLog, etc, so they're not confused with the top-level files.

[kdt3rd]

Thanks for updating all this!

[kdt3rd]

as of 2.3 we also support c++11 threads and such, whatever that implementation may be... I guess we never got to updating those documents. Should we say that this may be the last release with specific thread library support and will switch to c++11 in the next version?

[cary-ilm]

Sure. Also, the IlmBase/OpenEXR README.md's had wording about building on Windows. There's not much in the top-level INSTALL.md. Can someone check to confirm the Windows build instructions are sufficient?

…

On Wed, Jul 24, 2019 at 2:20 AM Kimball Thurston ***@***.***> wrote: ***@***.**** approved this pull request. Thanks for updating all this! ------------------------------ In IlmBase/README.md <#489 (comment)>: > -#### Public/User Library Namespace - -The ``--enable-customusernamespace`` option can override the namespace -into which will the internal namespace will be exported. This takes an -argument that sets the name of the custom user namespace. In the -example above, ``IMATH_NAMESPACE`` could be resolved into something -other than Imath, say ``Imath_MySpecialNamespace``. - -In nearly all cases, this will not be used as per the above discussion -regarding code compatibility. Its presence is to provide a mechanism -for not prohibiting the case when the application must pass objects -from two different versions of the library. - -Tests ------ +* **IlmThread** - a thread abstraction library for use with OpenEXR and as of 2.3 we also support c++11 threads and such, whatever that implementation may be... I guess we never got to updating those documents. Should we say that this may be the last release with specific thread library support and will switch to c++11 in the next version? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#489>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AFC3DGJ3HTKWJFZCX3TOPBDQBANHLANCNFSM4IGKSNZQ> .