From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id D6E3243F34; Sun, 28 Apr 2024 09:46:13 +0200 (CEST) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 52D0540265; Sun, 28 Apr 2024 09:46:13 +0200 (CEST) Received: from mail.lysator.liu.se (mail.lysator.liu.se [130.236.254.3]) by mails.dpdk.org (Postfix) with ESMTP id A3BCE40263 for ; Sun, 28 Apr 2024 09:46:12 +0200 (CEST) Received: from mail.lysator.liu.se (localhost [127.0.0.1]) by mail.lysator.liu.se (Postfix) with ESMTP id D33EB1C873 for ; Sun, 28 Apr 2024 09:46:11 +0200 (CEST) Received: by mail.lysator.liu.se (Postfix, from userid 1004) id C7A1C1C96D; Sun, 28 Apr 2024 09:46:11 +0200 (CEST) X-Spam-Checker-Version: SpamAssassin 4.0.0 (2022-12-13) on hermod.lysator.liu.se X-Spam-Level: X-Spam-Status: No, score=-1.3 required=5.0 tests=ALL_TRUSTED,AWL, T_SCC_BODY_TEXT_LINE autolearn=disabled version=4.0.0 X-Spam-Score: -1.3 Received: from [192.168.1.59] (unknown [62.63.215.114]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by mail.lysator.liu.se (Postfix) with ESMTPSA id 77DBB1C96C; Sun, 28 Apr 2024 09:46:10 +0200 (CEST) Message-ID: <4d5510d1-bdc6-43de-abbc-749eaa3c75a4@lysator.liu.se> Date: Sun, 28 Apr 2024 09:46:09 +0200 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Content-Language: en-US To: "dev@dpdk.org" Cc: =?UTF-8?Q?Mattias_R=C3=B6nnblom?= , "Richardson, Bruce" From: =?UTF-8?Q?Mattias_R=C3=B6nnblom?= Subject: Run unit tests with C++ too Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV using ClamSMTP X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org It would be great if the unit test suite (app/test/*) was compiled (and run) using a C++ (C++11) compiler as well. At least, if such is available. With the current state of affairs, header file macros or functions are not verified to be functional (or even valid) C++. "C is a subset of C++", which was never true, is becoming less and less so. If all unit tests aren't valid C++, maybe one could start with an "opt in" model. A drawback of this is that the unit tests need to be both valid C and valid C++.