Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:120162 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 15683 invoked from network); 29 Apr 2023 12:56:27 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 29 Apr 2023 12:56:27 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id D0F771804D5 for ; Sat, 29 Apr 2023 05:56:26 -0700 (PDT) X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on php-smtp4.php.net X-Spam-Level: X-Spam-Status: No, score=0.6 required=5.0 tests=BAYES_50,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,FREEMAIL_FROM, RCVD_IN_DNSWL_NONE,RCVD_IN_MSPIKE_H3,RCVD_IN_MSPIKE_WL,SPF_HELO_NONE, SPF_PASS,T_SCC_BODY_TEXT_LINE autolearn=no autolearn_force=no version=3.4.2 X-Spam-ASN: AS15169 209.85.128.0/17 X-Spam-Virus: No X-Envelope-From: Received: from mail-oa1-f54.google.com (mail-oa1-f54.google.com [209.85.160.54]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by php-smtp4.php.net (Postfix) with ESMTPS for ; Sat, 29 Apr 2023 05:56:26 -0700 (PDT) Received: by mail-oa1-f54.google.com with SMTP id 586e51a60fabf-18f4a6d2822so7941973fac.1 for ; Sat, 29 Apr 2023 05:56:26 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1682772985; x=1685364985; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=UwlpEsr4x7KHhbpLeIM96O1NHThht/F/CaMsbMG42f0=; b=OkGT7+zkSi09PGulA0K6Wol0XKpP0CTwzVEXTeHJVNbdM8hY2JY1hyQVNAzU1/GMCR sOVnnIFp2ML+Rpw+Wo5tbIGokzhN48djtsTx3F0SNp+cxYImgRLsCyqSQzCHP1Fg0F5l MHldJi6jNJf4X4E25whF3UW4cr1ZcRclayl1bUyLdQyxb8egcgC7kupwA86NpO+z6bjU cv4a3Khrxkq7manunXRo7u2475m1jhOeU27bxf7R/9W4Wh7cs8TYpk3y3x7P+2kO4aVh OP8RTotnGrMkhX2bchcpYCKBd7K1Egtb0ZPVE7E+TM5mJyQyMRTD515/PwkRFpSDZr2e O+6w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1682772985; x=1685364985; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=UwlpEsr4x7KHhbpLeIM96O1NHThht/F/CaMsbMG42f0=; b=Kj3TidXoCuR4fxhyRS6hivZBSHZkGZenC3d/q3EFFSA6WgIeUlb5Hnj1n+J0XyZKCR YzjYdKMf7N4MgcLzZGAYLT31rah4ph5ptmzUGjsLA8+Q3BzSNWzJX2m6QHt9PC9NxhgK fsRHTRnn3vAbGdDrkaUTt1VSwJF+Ibvx4Q/uqhw+DiCThm++x7M0URbeRidTTUV6b91E GpSom037x3JV5FZlW7vUD1eiXUFuFnw45T7hR4or+pQuRcdrCUwaRDDIiJNSP9ulZo3f llgvUTK1z0/pLO769VplD8EJMgshjLdftYwDqIwiYlquxqGh/eiSRrKAjdVL3BJbpSrh ABug== X-Gm-Message-State: AC+VfDwUAA35VvCAwXbCj8Oi1hNNp/Foq4RFFhq4VSficDVBurDqdQh2 dkpvxdj5S/SfT1t12NSMn/R7Z97K4YKGeQHCpsc= X-Google-Smtp-Source: ACHHUZ7cWW4KjBKNcpsUFc/29SKSfVJmpKe+ijtE2E/3i9aqMWNCP+7tntPHf402vPx5t5Pf1a4JVN6CfnHPHs/Onwg= X-Received: by 2002:a54:4705:0:b0:38e:f305:3d40 with SMTP id k5-20020a544705000000b0038ef3053d40mr4135750oik.1.1682772985504; Sat, 29 Apr 2023 05:56:25 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: Date: Sat, 29 Apr 2023 14:56:13 +0200 Message-ID: To: Dan Liebner Cc: PHP Internals Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Subject: Re: [PHP-DEV] Moving a tmpfile()? From: landers.robert@gmail.com (Robert Landers) On Sat, Apr 29, 2023 at 9:33=E2=80=AFAM Dan Liebner wr= ote: > > Are there any inherent problems with moving a file created with tmpfile()= ? > In practice, it seems that it can be done and the file will not be delete= d > after being moved and the file handle closed. > > Thanks, > Dan I suspect it depends on the OS. For example, in Linux, you can delete a file you are writing to without issues, but you cannot in Windows.