> If you choose not to use a phar, but instead, just loose PHP files, it
> extracts the sources to a random `/tmp` directory when executing. So,
> FFI and other things should "just work" without any shenanigans.
>
> Robert Landers
> Software Engineer
> Utrecht NL
Thank you for the suggestion.
The
On Tue, Dec 19, 2023 at 3:35 AM Vinicius Dias wrote:
>
> > > I suppose it'd be possible to improve FFI to call the PHP VFS layer to
> > > resolve a path, which would handle the phar:// scheme and other schemes.
> > > But, I would be worried about potential other downstream impacts - esp.
> > >
> > I suppose it'd be possible to improve FFI to call the PHP VFS layer to
> > resolve a path, which would handle the phar:// scheme and other schemes.
> > But, I would be worried about potential other downstream impacts - esp.
> > security implications - as this is a novel (to me at least) scen
Ah, that makes total sense. I was worried I was doing something very wrong. haha
Thank you very much for the detailed clarification.
This doesn't seem to be a "critical" feature, but I wonder if the
documentation shouldn't mention something about only "regular files"
being supported.
Vinicius Di
On Fri, Sep 8, 2023 at 2:33 PM Vinicius Dias wrote:
> I was playing around with some libraries using FFI and I wanted to
> share a .phar with the result, but to my surprise, it didn't work.
>
> Apparently we are not able to load shared libraries using FFI from
> within .phar files.
> Is that the
