On 5/11/22 5:59 PM, William Linkmeyer via Boost wrote:
[Robert]
It's time to refactor the IOS committee.
a) redefine it's mission.
Such a committee should address issues of the core language only.
b) "standard" libraries may be provided by anyone. Venders, Open Source fanatics, high school students, etc. They may be given away, sold or what every.
Since the language is already overladen with too many arcane features, the job for the IOS committee can be considered mostly done. The committee can shrink down to a manageable size. Getting your pet idea into the "standard library" to have other people code won't give you the excitement it once did. Oh well.
With the exception of “paid” standard libraries, how is this not already the case?
WL
In a large sense it already is almost. The whole step of writing 100's of pages of text after negotiating every word would disappear. Library providers would provide their own documentation. If the library is poorly made, poorly specified, doesn't work, what ever. The library becomes "online" when the author releases it. The he promotes it. It becomes standard iff it meets all the conditions for a "standard" library. Vendors compiler, and the set of standard libraries they want to include. Its their each decision. Robert Ramey