Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:124926 X-Original-To: internals@lists.php.net Delivered-To: internals@lists.php.net Received: from php-smtp4.php.net (php-smtp4.php.net [45.112.84.5]) by qa.php.net (Postfix) with ESMTPS id 7FCFE1A00B7 for ; Wed, 14 Aug 2024 09:35:37 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=php.net; s=mail; t=1723628243; bh=Q+bPLd530Nl5wHhKQwzr2xYPVqIfGJmsi/jUT6R5pjI=; h=Date:Subject:To:References:From:In-Reply-To:From; b=EN7nw7a16hndQVg0RDkjmXDqA52cmYHvGZfkKlD4gJvOqjD/Z1AHEvypxIImJnpMa 5No31a/Xfv4iwPWSCTUAcHXQdbQD7sKxHzfJXROccxKNadxx2ltcSBMT5BHys+Jcl6 QvFogUOOilzWUjwgiSq2mtMfy3K3QNPgGM+pPW/s7gx7cV7d78U4Hqyn7tDAo2ui2b L92UjpMRyvtKVg0KV3TVWK9f367hffTmtgHMvrYDuxgHgynN+Nm5R1WfwOPHMfJctz qmE5yLNLUMoYyDogDN5k8MCyhSVqjVX7zHvss8dhKpRvsTzZMhZK2ZXGbjgMUPHLNG VsakQyDPyj2cQ== Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id B613D180055 for ; Wed, 14 Aug 2024 09:37:20 +0000 (UTC) X-Spam-Checker-Version: SpamAssassin 4.0.0 (2022-12-13) on php-smtp4.php.net X-Spam-Level: X-Spam-Status: No, score=0.8 required=5.0 tests=BAYES_50,DMARC_MISSING, SPF_HELO_NONE,SPF_PASS autolearn=no autolearn_force=no version=4.0.0 X-Spam-Virus: No X-Envelope-From: Received: from franklin.smtp.mailx.hosts.net.nz (franklin.smtp.mailx.hosts.net.nz [43.245.52.180]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (prime256v1) server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by php-smtp4.php.net (Postfix) with ESMTPS for ; Wed, 14 Aug 2024 09:37:19 +0000 (UTC) Received: from 125-237-145-229-fibre.sparkbb.co.nz ([125.237.145.229] helo=[192.168.1.68]) by franklin.smtp.mailx.hosts.net.nz with esmtpsa authed as varteg.nz (TLS1.3:ECDHE_X25519__RSA_PSS_RSAE_SHA256__AES_128_GCM:128) (Exim 4.96) (envelope-from ) id 1seAPh-005jDb-04 for internals@lists.php.net; Wed, 14 Aug 2024 21:35:29 +1200 Message-ID: <7a17d804-4844-4a08-8d3a-53dab4b7dc46@varteg.nz> Date: Wed, 14 Aug 2024 21:35:21 +1200 Precedence: bulk list-help: list-post: List-Id: internals.lists.php.net x-ms-reactions: disallow MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: [PHP-DEV] [DISCUSSION] C++ Enhancements in Zend API To: internals@lists.php.net References: <89C901BF-DCEA-498E-93B0-750C49E6275B@getmailspring.com> <0BB4DB2D-62E1-40F9-91F3-7D48367D2CBE@edison.tech> Content-Language: en-GB In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Hosts-DKIM-Check: none From: weedpacket@varteg.nz (Morgan) On 2024-08-14 16:03, Lanre wrote: > > On Tue, Aug 13, 2024 at 4:28 PM Mike Schinkel > Well, there is this: > > https://media.defense.gov/2023/Dec/06/2003352724/-1/-1/0/THE-CASE-FOR-MEMORY-SAFE-ROADMAPS-TLP-CLEAR.PDF > > -Mike > > > The source mentions Python and Swift as "memory-safe languages," both of > which are implemented in C and C++. How does that work if C and C++ > aren't memory-safe? > > > Cheers, > Lanre. The same way Legolas can be called an elf even when the character is being played by a human actor: by not making category errors. Even if the compiler of a Swift program has a memory management failure, that is not the fault of the Swift program, but of the compiler (and the language it is written in that allowed it).