MISRA C++2008 Guidelines.pdf

发布时间：2022-05-30 发布人：admin 分类：说明书资料大小：2.55M 资料格式：pdf 举报版权申诉

liwenzhao-11275062-4744302543286304228.pdf-第1页.png

第1页 / 共220页

liwenzhao-11275062-4744302543286304228.pdf-第2页.png

第2页 / 共220页

liwenzhao-11275062-4744302543286304228.pdf-第3页.png

第3页 / 共220页

liwenzhao-11275062-4744302543286304228.pdf-第4页.png

第4页 / 共220页

liwenzhao-11275062-4744302543286304228.pdf-第5页.png

第5页 / 共220页

liwenzhao-11275062-4744302543286304228.pdf-第6页.png

第6页 / 共220页

liwenzhao-11275062-4744302543286304228.pdf-第7页.png

第7页 / 共220页

liwenzhao-11275062-4744302543286304228.pdf-第8页.png

第8页 / 共220页

文本预览

The Motor Industry Software Reliability Association MISRA C++:2008 Guidelines for the use of the C++ language in critical systems June 2008

First published June 2008 MIRA Limited Watling Street Nuneaton Warwickshire CV10 0TU UK www.misra-cpp.com © MIRA Limited, 2008. “MISRA”, “MISRA C” and the triangle logo are registered trademarks of MIRA Limited, held on behalf of the MISRA Consortium. All rights reserved. No part of this publication may be reproduced, stored in a retrieval system or transmitted in any form or by any means, electronic, mechanical or photocopying, recording or otherwise without the prior written permission of the Publisher. ISBN 978-1-906400-03-3 paperback ISBN 978-1-906400-04-0 PDF Printed by Hobbs the Printers Ltd British Library Cataloguing in Publication Data. A catalogue record for this book is available from the British Library This copy of MISRA C++:2008 - Guidelines for the use of the C++ language in critical systems is issued to Emmanuel DUFOUR of Silicomp-AQL at 195 Rue Lavoisier BP 1 ZIRST, Montbonnot Saint Martin, France, 38330. The file must not be altered in any way. No permission is given for distribution of this file. This includes but is not exclusively limited to making the copy available to others by email, placing it on a server for access by intra- or inter-net, or by printing and distributing hardcopies. Any such use constitutes an infringement of copyright. MISRA gives no guarantees about the accuracy of the information contained in this PDF version of the Guidelines. The published paper document should be taken as authoritative. Information is available from the MISRA web site on how to purchase printed copies of the document.

£========= The Motor Industry Software Reliability Association MISRA C++:2008 Guidelines for the use of the C++ language in critical systems June 2008 i

MISRA Mission Statement: To provide assistance to the automotive industry in the application and creation within vehicle systems of safe and reliable software. MISRA, The Motor Industry Software Reliability Association, is a collaboration between vehicle manufacturers, component suppliers and engineering consultancies which seeks to promote best practice in developing safety-related electronic systems in road vehicles and other embedded systems. To this end MISRA publishes documents that provide accessible information for engineers and management, and holds events to permit the exchange of experiences between practitioners. www.misra.org.uk Disclaimer Adherence to the requirements of this document does not in itself ensure error-free robust software or guarantee portability and re-use. Compliance with the requirements of this document, or any other standard, does not of itself confer immunity from legal obligations. ii

• • • • • Foreword “C makes it easy to shoot yourself in the foot; C++ makes it harder, but when you do it blows your whole leg off.” — Bjarne Stroustrup Few could have predicted the effect that MISRA C would have within embedded systems engineering. Since its launch in 1998, it has become the dominant coding standard used for the development of critical systems with the C programming language. Given this success, the fact that C++ is now being used within critical systems (e.g. the Joint Strike Fighter, jet-engine controllers and medical systems), and that there is currently no universally accepted set of guidelines for its use in these systems, MISRA committed itself to the development of a similar set of guidelines for C++. To that end, the MISRA C++ Working Group was established towards the end of September 2005. Its objectives were to: Produce, using techniques similar to those within MISRA C, a C++ subset suitable for use in critical systems; Gather existing C++ guidelines from many diverse sources into a single repository; Establish a single, generic set of guidelines for the use of C++ in critical systems; Produce guidelines that are understandable to the majority of programmers. Add new guidance so as to signiﬁcantly enhance the state-of-the-art; Handling, with these areas being speciﬁcally targeted as the existing state-of-the-art did not The work to produce the guidelines made a rapid start, and was greatly assisted by the many in- house coding standards that were made available to the group — thanks are due to all those who contributed. These, and the guidelines available from other sources, formed a solid foundation on which to base many rules. Focus then moved on to the production of guidelines for Templates, Inheritance and Exception provide adequate coverage. The issues associated with Unnecessary Constructs were also selected for investigation. This document contains the results of these activities. The group hopes that MISRA C++ will go on to become as successful and widely-adopted as MISRA C. Finally, I would like to give my personal thanks to all of those who sat on the Working Group. I have, as always, learnt a lot from them during the development process. I just hope I have managed to put enough back into the project to repay part of the debt I owe them all. Chris Tapp, BSc (Hons), MIEE MISRA C++ Chairman 15 April 2008 iii

Acknowledgements The MISRA consortium would like to thank the following individuals for their signiﬁcant contribution to the writing of this document: Richard Corden Mike Hennell Derek Jones Keith Longmore Clive Pygott Chris Tapp Programming Research Ltd LDRA Ltd Knowledge Software Ltd Lotus Cars Ltd QinetiQ Ltd Keylevel Consultants Ltd The MISRA consortium also wishes to acknowledge contributions from the following individuals during the development and review process: Al Grant Dave Banham Christopher Hall Martin Beeby Frank Haug Fergus Bolger Martin Bonner Stefan Heinzmann Michael R. Bossert Robert Hooper Elmar Hufschmid Antonio Cavallo Ian Chalinder Paul Jeary Kwok Chan Josef Kollar Albert Kreitmeyr Valéry Creux David Crocker Fred Long Thomas M. Galla Andreas Ludwig Frank Martinez Jason Masters Jürgen Mottok Chris Mycock Tadanori Nakagawa Hans Odeberg Charles Osborn Rob Pearce PremAnand M Rao Derek Reinhardt David Reversat John Ridgway Iris Rödder Walter Schilling Ben Smith Andreas Stangl Toshihiro Tajima David Ward Andrew Warren Andrew Watson Ashley Wise iv

Contents 1. 2. 3. 4. Background........................................................................................................................... 1 1.1 The use of C++ in critical systems .................................................................................. 1 1.2 Language insecurities and the C++ language.................................................................. 1 1.2.1 The developer makes mistakes............................................................................... 1 1.2.2 The developer misunderstands the language.......................................................... 2 1.2.3 The compiler does not do what the developer expects........................................... 2 1.2.4 The compiler contains errors.................................................................................. 2 1.2.5 Run-time errors ...................................................................................................... 2 1.3 The use of C++ for safety-related systems...................................................................... 2 1.4 C++ standardization......................................................................................................... 3 The vision............................................................................................................................. 4 2.1 Rationale for the production of MISRA C++.................................................................. 4 2.2 Objectives of MISRA C++.............................................................................................. 4 Scope.................................................................................................................................... 5 3.1 Base language issues........................................................................................................ 5 Issues not addressed......................................................................................................... 5 3.2 3.3 Applicability.................................................................................................................... 5 3.4 Prerequisite knowledge.................................................................................................... 5 3.5 Library issues................................................................................................................... 5 3.6 Auto-generated code issues ............................................................................................. 6 Using MISRA C++............................................................................................................... 7 4.1 The software engineering context.................................................................................... 7 4.2 The programming language and coding context ............................................................. 7 4.2.1 Training.................................................................................................................. 7 4.2.2 Style guide.............................................................................................................. 8 4.2.3 Tool selection and validation.................................................................................. 8 4.2.4 Source complexity metrics..................................................................................... 9 4.2.5 Test coverage.......................................................................................................... 9 4.3 Adopting the subset....................................................................................................... 10 4.3.1 Compliance matrix............................................................................................... 10 4.3.2 Deviation procedure............................................................................................. 10 4.3.3 Formalization within quality system.................................................................... 12 4.3.4 Introducing the subset.......................................................................................... 12 4.4 Claiming compliance..................................................................................................... 12 4.5 Continuous improvement............................................................................................... 12 v

Contents (continued) 5. Introduction to the rules...................................................................................................... 13 5.1 Rule classiﬁcation.......................................................................................................... 13 5.1.1 Required rules ...................................................................................................... 13 5.1.2 Advisory rules...................................................................................................... 13 5.1.3 Document rules .................................................................................................... 13 5.2 Organization of rules ..................................................................................................... 13 5.3 Exceptions to the rules................................................................................................... 13 5.4 Redundancy in the rules................................................................................................. 14 Presentation of rules ...................................................................................................... 14 5.5 5.6 Understanding the issue references ............................................................................... 15 5.7 Scope of rules ................................................................................................................ 16 Rules................................................................................................................................... 17 6.0 Language independent issues ........................................................................................ 17 6.0.1 Unnecessary constructs........................................................................................ 17 6.0.2 Storage.................................................................................................................. 25 6.0.3 Runtime failures................................................................................................... 26 6.0.4 Arithmetic............................................................................................................. 29 6.1 General ......................................................................................................................... 30 6.1.0 Language.............................................................................................................. 30 6.2 Lexical conventions....................................................................................................... 31 6.2.2 Character sets....................................................................................................... 31 6.2.3 Trigraph sequences............................................................................................... 31 6.2.5 Alternative tokens ................................................................................................ 32 6.2.7 Comments............................................................................................................. 32 Identiﬁers.............................................................................................................. 34 6.2.13 Literals.................................................................................................................. 37 6.3 Basic concepts ............................................................................................................... 40 6.3.1 Declarations and deﬁnitions................................................................................. 40 6.3.2 One Deﬁnition Rule ............................................................................................. 41 6.3.3 Declarative regions and scope.............................................................................. 44 6.3.4 Name lookup........................................................................................................ 45 6.3.9 Types .................................................................................................................... 46 Standard conversions..................................................................................................... 48 6.4.5 Integral promotions.............................................................................................. 48 6.4.10 Pointer conversions.............................................................................................. 50 6.2.10 6. 6.4 vi

分享到：

赞收藏

资料库

MISRA C++2008 Guidelines.pdf

相关推荐

开发技术

热门标签

最新资料