Re: [Firebird-devel] New BLR encoding

2017-02-11 Thread Alex Peshkoff
On 02/10/17 21:35, Adriano dos Santos Fernandes wrote: > On 10/02/2017 14:20, Dimitry Sibiryakov wrote: >> 10.02.2017 16:32, Adriano dos Santos Fernandes wrote: >>> Firebird BLR must be improved to be easier to read (the code), to be >>> easier to generate and parse and to be extensible. >> Why

Re: [Firebird-devel] New BLR encoding

2017-02-10 Thread Adriano dos Santos Fernandes
On 10/02/2017 14:20, Dimitry Sibiryakov wrote: > 10.02.2017 16:32, Adriano dos Santos Fernandes wrote: >> Firebird BLR must be improved to be easier to read (the code), to be >> easier to generate and parse and to be extensible. >Why to improve something that must die?.. > > I don't see C++, Ja

Re: [Firebird-devel] New BLR encoding

2017-02-10 Thread Alex Peshkoff
On 02/10/17 19:20, Dimitry Sibiryakov wrote: > 10.02.2017 16:32, Adriano dos Santos Fernandes wrote: >> Firebird BLR must be improved to be easier to read (the code), to be >> easier to generate and parse and to be extensible. > Why to improve something that must die?.. > Really - may be it sh

Re: [Firebird-devel] New BLR encoding

2017-02-10 Thread Dimitry Sibiryakov
10.02.2017 16:32, Adriano dos Santos Fernandes wrote: > Firebird BLR must be improved to be easier to read (the code), to be > easier to generate and parse and to be extensible. Why to improve something that must die?.. -- WBR, SD.

[Firebird-devel] New BLR encoding

2017-02-10 Thread Adriano dos Santos Fernandes
All, Firebird BLR must be improved to be easier to read (the code), to be easier to generate and parse and to be extensible. See now, to add to INSERT, we already have blr_store and blr_store2, both non extensible. It would require blr_store3/blr_store4 or blr_store3 with custom logic to have op