Re: POpen en PClose

Michael Van Canneyt via fpc-pascal <[email protected]> Mon, 20 Jul 2026 12:07:34 +0200 (CEST)
Newsgroups gmane.comp.compilers.free-pascal.general
Message-ID <[email protected]>
  This message is in MIME format.  The first part should be readable text,
  while the remaining parts are likely unreadable without MIME-aware tools.

--8323329-1456726836-1784542054=:3604459
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8BIT



On Mon, 20 Jul 2026, Marco van de Voort via fpc-pascal wrote:

>
> Op 20-7-2026 om 11:57 schreef Michael Van Canneyt via fpc-pascal:
>>>>
>>>> I am looking at the implementation of POpen and PClose in the 
>>>> runtime-library for Darwin (or more general for UNIX). It seems like 
>>>> it doesn't call into libc popen and pclose, but instead follows its 
>>>> own implementation in unix.pp in POpen_internal. I am just curious 
>>>> to know the reason.
>>>>
>>> Phew, that was over twenty years ago, but afaik the reason is that 
>>> libc popen and pclose us C FILE descriptors, which the RTL in general 
>>> doesn't use to avoid a mix of functions with pascal and C file types.
>>>
>>> So popen/pclose are a more high level (FILE * using) part of libc, 
>>> while we tend to only use the basis.
>>
>> Glad our memories agree on this :-) 
>
> Well aside from the fact that FreeBSD was the architecture where the 
> baseunix/unix RTLĀ  was done. The port to Linux was only done later :-)

Correct, but popen/pclose existed before that in the linux unit.
Pretty sure about that, because I implemented it there.

Michael.
--8323329-1456726836-1784542054=:3604459
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
fpc-pascal maillist  -  [email protected]
https://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-pascal

--8323329-1456726836-1784542054=:3604459--