Hi Cédric,
Le 8 juil. 2019 à 12:39, Cédrick Béler <cdrick65@gmail.com> a écrit :
Hi,
Really nice Christophe.
I wonder then if OSSubProcess shroud be « renamed » OSUnixSubProcess ?
In my vision, I would like to see OsWinSubprocess merged into OSSubprocess once we have full support (e.g. std input/outputs).
A related question is the the limitation of LibC, iow. When to use LibC or the couple OSSubProcess/OSWinSubProcess ?
Basically, OSSubprocess uses LibC and OSWinSubprocess uses the windows equivalent of LibC (Kernel32 and msvcrt). I would say it is easier to use a more high level library like OSSubprocess or OSWinSubprocess but it is still possible to use LibC directly. They can be used independently. On Windows, to workaround std input/output support you could just make the launched program write into a file and read it afterwards from Pharo. Also I think OSWinSubprocess is the only process library working on 64-bit images. HTH, Christophe.