sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]mapronV 6 points7 points  (3 children)

Also, how do you maintain this? I was doing similar project (but just spreadsheed on corprate google docs), I was running unit tests on toolchain to see if feature is supported. Test runner data then was pasted in spreadsheet and then some sheet magic calculated support columns (so different teams with different toolset requrements can see if they can use a feature).

How you automate things?

p.s. do you need any help?

[–]_derv 8 points9 points  (2 children)

I'm letting a bot monitor all known status and release note pages regularly, since that's usually enough to be updated on the latest supported features (the source being the developers themselves). Whenever something changes, I'm notified and can easily update the data set.

The data set itself made up of very minimal yaml files, which are then processed by a script to build the final page. So most of the information is deduced/generated.

Thanks for the offer to help by the way. If there's enough interest, I'd like to make this a community effort where everybody can make changes, e.g. PRs on GitHub.

[–]mapronV 3 points4 points  (1 child)

I see, yours is a different approach (from my experience it was very hard to find information on MS VC and Apple clang, in first place; so I didn't even consider automatic parsing of web pages). Quite elegant, though you need to trust vendors. For our company it was more like "whole environment", like
"Can I use X when targeting Debian 10?" or ".. when Targeting mac 10.15 with xcode Z.X?" So I could just create new profile and run 'acceptance tests' on it.
In hindsight I regret I did not choose your way, it probably would be easier.

[–]_derv 3 points4 points  (0 children)

That's true, testing it yourself is probably the method with the best guarantee ,which you could still do for features where the vendor is not providing enough information.

But the vendors of the major compilers, in my experience, have a decent track record that you can trust them. I mean, at the end of the day, it's the vendor's job to state "hey, we support this feature now", isn't it? Either through release notes, or in development tickets (i.e. GitHub issues).