Hi Abel, Great work, I'll give it a shot on pg 10 and 11 later today at work. As for the mailing lists, I'd start with pgsql-general mailing list before the -hackers list, the same core devs watch both lists so you'll get the same high grade advice. They'll let you know if you should promote the issue to -hackers. The main advantage is, you'll get many more eyeballs on -general and it's more appropriate given it's not a core dev issue.
-Michel On Wed, Jan 16, 2019 at 11:05 PM Abel Normand <abel.ze.norm...@gmail.com> wrote: > Thanks all for your suggestions, I will open respective issues for minor > improvements. > > Also mmamkin connected with me directly and also suggested to use prefix > "pg-" for whole library not only for public functions. I think that I > probably should to use namespaces to hide private functions. It would be > nice if someone would share with me best practice for using them bcs I > still do not have deep understanding in their usage. > > There is also a "postgresql-hackers" mailing list where devs discuss not > only DBMS development but also clients and adapters implementation. So I > think I should to share lib with them also, it probably will draw some > attention to language itself and devs from pg community will advice > something. What you think? > > Thanks. > *From:* r...@tamos.net > *Sent:* 16 January 2019 16:04 > *To:* picolisp@software-lab.de > *Reply to:* picolisp@software-lab.de > *Subject:* Re: pgint.l > > +1 for writing tests. > +1 for using aw-‘s test harness. > +1 for having a sane license. > > Huzzah! :) > > > > > On Tue, 15 Jan 2019 21:11 +0300, Abel Normand wrote: > > Hello everyone, > > > > I'm happy to announce that I released my small library to interfacing > with > > PostgreSQL -- https://gitlab.com/Abel-ze-Normand/pgint.l . I tried to > keep > > its implementation as simple as possible. > > > > I'm open to your suggestions for future improvements and your > > contributions. > > -- > > Best regards, Nail > >
