3 databases in 3 days
hga@xxxxxx
(30 Sep 2019 00:36 UTC)
|
Support for Scheme standards and implementations
Lassi Kortela
(30 Sep 2019 08:11 UTC)
|
Re: Support for Scheme standards and implementations
hga@xxxxxx
(30 Sep 2019 11:25 UTC)
|
Scheme implementations and portability Lassi Kortela (30 Sep 2019 13:14 UTC)
|
Re: Scheme implementations and portability
John Cowan
(30 Sep 2019 19:27 UTC)
|
Scheme implementations, portability, FFIs
Lassi Kortela
(30 Sep 2019 21:16 UTC)
|
Re: Scheme implementations, portability, FFIs
John Cowan
(30 Sep 2019 22:10 UTC)
|
JDBC
Lassi Kortela
(30 Sep 2019 13:15 UTC)
|
Re: JDBC
hga@xxxxxx
(30 Sep 2019 13:24 UTC)
|
Re: JDBC and subprocess protocol
Lassi Kortela
(30 Sep 2019 14:29 UTC)
|
Re: JDBC and subprocess protocol
hga@xxxxxx
(30 Sep 2019 15:16 UTC)
|
Re: JDBC and subprocess protocol
Lassi Kortela
(30 Sep 2019 15:47 UTC)
|
Re: JDBC and subprocess protocol
Lassi Kortela
(30 Sep 2019 15:55 UTC)
|
Re: JDBC
John Cowan
(30 Sep 2019 15:10 UTC)
|
Re: JDBC
Lassi Kortela
(30 Sep 2019 15:26 UTC)
|
Re: JDBC
Lassi Kortela
(30 Sep 2019 15:34 UTC)
|
sdbi design in detail and MariaDB CONNECT
hga@xxxxxx
(30 Sep 2019 16:14 UTC)
|
Re: sdbi design in detail and MariaDB CONNECT
Lassi Kortela
(30 Sep 2019 16:28 UTC)
|
Re: sdbi design in detail and MariaDB CONNECT
John Cowan
(30 Sep 2019 20:25 UTC)
|
Re: JDBC
John Cowan
(30 Sep 2019 16:44 UTC)
|
Re: JDBC
Lassi Kortela
(30 Sep 2019 20:52 UTC)
|
Re: JDBC
Alaric Snell-Pym
(01 Oct 2019 09:26 UTC)
|
Re: JDBC
hga@xxxxxx
(01 Oct 2019 09:55 UTC)
|
Re: JDBC
Alaric Snell-Pym
(01 Oct 2019 11:09 UTC)
|
sdbi supports "databases" with text query languages that return rectangular results
hga@xxxxxx
(01 Oct 2019 12:22 UTC)
|
Re: sdbi supports "databases" with text query languages that return rectangular results
John Cowan
(01 Oct 2019 16:10 UTC)
|
> It does look very nice, and the last point release was in June: > https://bitbucket.org/ktakashi/sagittarius-scheme/wiki/Home Yeah. It's one of the most actively maintained Schemes. People just don't know about it. > Chibi Scheme is simpler, follows the truth in advertising principle. > It's small and for me more comprehensible that the other currently > maintained, up to date with R7RS-small Schemes I've looked at like > Sagittarius or Chicken. Also uses Gnu Make vs. e.g. CMake, which > I'm not familiar with. A normal build is "cmake . && make && make install". It is quite a bit bigger than Chibi though, so they target different niches. That's what I like about Scheme. Any environment or deployment scenario you could possibly need to target, there's already an implementation for the job. Now it's just a matter of polishing the implementations and increasing portability to make it easier to share code and jump around as requirements change. > I will support R7RS in the fullness of time, and will be happy to > cooperate with R6RS porting. FFI porting will likely be a bigger > task, depending on how easy it is for an implementation. Chibi is perhaps the purest R7RS Scheme so you already have that :) It'd be nice to have more portable FFI. Every language eventually has that problem. I have some ideas but haven't had time to look at r6rs-pffi or implement anything yet. > Yes, the cond-expands for the PostgreSQL library are impressive, not > just for Scheme implementations but also for the presence or absence > of some other SRFIs it depends on. (chibi net) appears to be a > sufficient subset of SRFI 106 that little or nothing was needed there. Yes :) Portable Scheme is already easier than most people think. Many individuals are actively doing it but it's not much discussed, so people's general impression is that Scheme is not portable. Even R6RS<->R7RS converters are easy to write for a lot of real code. Here's one in 65 lines: <https://github.com/lassik/srfi-175/blob/master/srfi/r7rs-to-r6rs.scm>. Akku comes with a generic converter that can handle most/all of R7RS by now. The wildest cond-expands I've seen are in the SRFI 64 unit test framework implementation: <https://github.com/retroj/srfi-64-chicken/blob/master/srfi-64/srfi-64-port.scm>. It's nice to be able to do that but it also shows why standards and code portability are important :)