On Fri, 4 Apr 2014, Sergei Gavrikov wrote: > On Fri, 4 Apr 2014, Jan Nijtmans wrote: > > > An additional issue is that binary/octal/hex numbers cannot contain > > dots, so they must be handled separately anyway. Done here: > > <http://fossil-scm.org/index.html/info/a306f771d8> > > [the issues went away] > > Thank you very much! Now we have the comfortable way to manage any > numbers on embedded targets.
Hi Jan I found one exception, if there is digit 'b' (only) on the second position (only) in a hexadecimal number % fossil test-th-eval 'expr 0+0xb' 11 % fossil test-th-eval 'expr 0+0x0b' 0 % fossil test-th-eval 'expr 0+0x00b' 11 % fossil test-th-eval 'expr 0+0xbc' 188 % fossil test-th-eval 'expr 0+0x0bc' TH_ERROR: expected number, got: "0x0bc" % fossil test-th-eval 'expr 0+0x00bc' 188 First, I thought that (0b) somehow shadows (0x), but this expressions also fail % fossil test-th-eval 'expr 0+0xab' 0 % fossil test-th-eval 'expr 0+0xabc' TH_ERROR: expected number, got: "0xabc" Could you, please, take a look on this puzzle? Sergei _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
