Re: [Firebird-devel] Current handling of precision in syntax

2019-07-27 Thread Mark Rotteveel
On 27-7-2019 14:35, Mark Rotteveel wrote: On 27-7-2019 14:16, Adriano dos Santos Fernandes wrote: On 27/07/2019 07:57, Mark Rotteveel wrote: When working on my pull request for FLOAT, I noticed that the way that the precision fragments (ie precision_opt and precision_opt_nz) works in the gramma

Re: [Firebird-devel] Current handling of precision in syntax

2019-07-27 Thread Mark Rotteveel
On 27-7-2019 14:16, Adriano dos Santos Fernandes wrote: On 27/07/2019 07:57, Mark Rotteveel wrote: When working on my pull request for FLOAT, I noticed that the way that the precision fragments (ie precision_opt and precision_opt_nz) works in the grammar yields non-intuitive error messages. For

Re: [Firebird-devel] Current handling of precision in syntax

2019-07-27 Thread Adriano dos Santos Fernandes
On 27/07/2019 07:57, Mark Rotteveel wrote: > When working on my pull request for FLOAT, I noticed that the way that > the precision fragments (ie precision_opt and precision_opt_nz) works in > the grammar yields non-intuitive error messages. > > For example, a negative precision just yields an unc

[Firebird-devel] Current handling of precision in syntax

2019-07-27 Thread Mark Rotteveel
When working on my pull request for FLOAT, I noticed that the way that the precision fragments (ie precision_opt and precision_opt_nz) works in the grammar yields non-intuitive error messages. For example, a negative precision just yields an unclear """ Token unknown - line 10, column 20 - """