carlosgalvezp added a comment. > "C++14 Guidelines"? So it's always and definitely C++14 specific?
To my knowledge, AUTOSAR handed over the work to MISRA and the current direction is that MISRA will merge AUTOSAR C++14 and older MISRA revisions into a brand-new MISRA release, coming up 202x (The "x" is very unclear here, it could take years to get it in place). So I would be surprised if AUTOSAR released a new version after this. They way they are written they are targetting the use of C++14. I suppose we can change the description in the future + add configuration to select whether to choose C++14 or something else if that ever comes up, but I think it's a bit premature at this point. Would you agree? > What is the licencing approach of this guideline? Looking up with searchers > seems to turn up a few PDFs which say `--- AUTOSAR CONFIDENTIAL ---`, yet > they are up and out on the official-looking website. Yes, that's strange. The disclaimer says the following: > The material contained in this work is protected by copyright and other types > of > intellectual property rights. The commercial exploitation of the material > contained in > this work requires a license to such intellectual property rights. > This work may be utilized or reproduced without any modification, in any > form or by > any means, for informational purposes only. For any other purpose, no part > of the > work may be utilized or reproduced, in any form or by any means, without > permission > in writing from the publisher. I'm not a lawyer for I think we can be sure that this is not a commercial use case? I guess if we were a company selling an AUTOSAR C++14-compliant static analyzer then we would need a license. CHANGES SINCE LAST ACTION https://reviews.llvm.org/D112730/new/ https://reviews.llvm.org/D112730 _______________________________________________ cfe-commits mailing list cfe-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
