cfbolz changed the topic of #pypy to: #pypy PyPy, the flexible snake https://pypy.org | IRC logs: https://quodlibet.duckdns.org/irc/pypy/latest.log.html#irc-end and https://libera.irclog.whitequark.org/pypy | the pypy angle is to shrug and copy the implementation of CPython as closely as possible, and staying out of design decisions
_whitelogger has joined #pypy
jcea has quit [Ping timeout: 248 seconds]
_whitelogger has joined #pypy
BarrensZeppelin has joined #pypy
alice has quit [Quit: *disappears* U_U]
otisolsen70 has joined #pypy
nimaje has quit [Ping timeout: 255 seconds]
nimaje has joined #pypy
nimaje has quit [Ping timeout: 256 seconds]
alice has joined #pypy
nimaje has joined #pypy
otisolsen70 has quit [Quit: Leaving]
BarrensZeppelin has quit [Quit: BarrensZeppelin]
jcea has joined #pypy
jcea has quit [Ping timeout: 248 seconds]
BarrensZeppelin has joined #pypy
BarrensZeppelin has quit [Quit: BarrensZeppelin]
BarrensZeppelin1 has joined #pypy
BarrensZeppelin1 is now known as BarrensZeppelin
BarrensZeppelin has quit [Quit: BarrensZeppelin]
<antilisp-dev> hi, which RPython documentation is the most up to date ? I built the sphinx documentation in the github repository, but it doesn't seem more up to date than the ones online and even has dead links to a bitbucket repository
<antilisp-dev> (i was looking for information on rlib.libffi, rlib.jit_libffi and rlib.clibffi to know which one to use and how)
<antilisp-dev> thanks, but i was looking for dynamic linking (rffi compiles to statically linked, i think)
<antilisp-dev> i found what i needed by tinkering with the source code of clibffi.py
<korvo> Excellent! I'm glad that you made progress. FWIW rffi can handle dynamic linking without any problem. In Typhon, the Monte reference interpreter, we link libsodium and libuv, and we use whatever libraries are available on the host. This usually means dynamic libuv and static libsodium, although apparently today on NixOS I get dynamic libsodium.
<korvo> You can check out the ECI for those here: https://github.com/monte-language/typhon/blob/master/typhon/ruv.py and https://github.com/monte-language/typhon/blob/master/typhon/rsodium.py. Also ping me if you want either of these broken out into their own repository for separate use, or for rpypkgs.
<korvo> Don't be afraid to crib ECI and compiler information. Just make sure that you look up what each thing does first. I know that it's not fun to spend an hour with rffi_platform.py and rffi.py open in multiple tabs, but the good news is that usually bindings only have to be written once. (And if you want to reuse existing bindings but they have sharp edges, ping me and we'll set up a new repo, etc.)
<antilisp-dev> thank you very much. I already used rffi before (with sdl2/3, it's actually pretty nice to use rpython as a C replacement with C libraries). In this case i wanted to expose the ffi features to a custom language interpreted by rpython (so the eci and llexternal functions have to be defined at runtime), so i think libffi is more suited to the task
<antilisp-dev> rpython makes it very fun to play with new PL ideas. I am currently just playing a bit with a smalltalk-inspired image-based object-oriented lisp before i get back to my main project (antilisp), but with rpython i feel like i could finish both if i wanted
jcea has joined #pypy
<korvo> Yeah! I agree. RPython is such a great tool for quick prototyping.
<korvo> BTW I have a repo for the classic SDL bindings, as used in PyGirl or Spy: https://github.com/rpypkgs/rsdl This is just the classic rsdl but with some patches to make newer PyGirl build again.