Re: pgint.l

2019-01-17 Thread Abel Normand
Hi Michael, yeah you right, i will do it in general list at first, thanks for advice. чт, 17 янв. 2019 г. в 19:22, Michel Pelletier : > 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

Re: pgint.l

2019-01-17 Thread Michel Pelletier
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

Re: pgint.l

2019-01-17 Thread Alexander Burger
Hi Abel, > 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. I would also recommend namespaces. > It would be nice if someone would

Re: pgint.l

2019-01-17 Thread Alexander Burger
On Thu, Jan 17, 2019 at 04:29:17PM +0100, Danilo Kordic wrote: > IMHO (PicoLisp) Namespaces _are_ "name" prefixes, for example "pg~" > instead of "pg-". > > [de pg []] # Empty Namespace. > [de pg~sym ~...] No, they are not. "pg~" is not part of the name. For example, one symbol may

Re: pgint.l

2019-01-17 Thread Danilo Kordic
IMHO (PicoLisp) Namespaces _are_ "name" prefixes, for example "pg~" instead of "pg-". [de pg []] # Empty Namespace. [de pg~sym ~...] Unfortunately Namespaces are not Association Lists, or Property Lists. Therefore they can not be processed by predefined procedures. I must point out