Fix numpy-installed-p to work with case sensitive lisps

[LEHunter]

T never has to be quoted (it evaluates to itself), so get rid of the (quote ... ) in the numpy-installed-p file. Has the advantage or producing t in case sensitive lisps as well.

[digikar99]

The final goal is to be able to handle (asdf:load-system "py4cl2-cffi") with minimal warnings. Not quoting yields a warning about undefined variable t when the readtable case used to load the system is different from compile time. I had assumed quoting it would get rid of it, but quoting creates other issues. Perhaps, the best is to handle this outside of lisp.

The intention of making it a lisp file is to make use of asdf's autocompile mechanism. By changing numpy-installed-p, it would automatically trigger the recompilation of the lisp file shared-objects.lisp. But perhaps, it might be better to perform the recompilation manually.

Let me see if I can try something to see to solve both the issues.

[LEHunter]

On Apr 29, 2024, at 5:55 PM, Shubhamkar Ayare ***@***.***> wrote: Not quoting yields a warning about undefined variable t when the readtable case used to load the system is different from compile time. I had assumed quoting it would get rid of it, but quoting creates other issues. Perhaps, the best is to handle this outside of lisp.

If a user wants to install / compile the system with one readable case, and then expect to use it (unmodified) in another, I think that’s unreasonable. Although I think it’s important to support all choices of readable-case, I don’t think it’s incumbent on you to support changes between compile and run there… Hope we can get the load flags straightened out, too. Thanks again. Larry