[fossil-users] [fossil all close]

It occurred to me that a good exercise for reacquainting myself with the Fossil source tree (it's been awhile since DRH's presentation on same) would be to add a [fossil all close] command. Plus I actually could use such a thing right about now since I'm reorganizing repositories and checkouts

Re: [fossil-users] TH1: support for octal and hexadecimal numbers in expressions

I think th1 "happens" to basically be a subset of Tcl, but is not "designed" to strictly be a subset of Tcl, fwiw. On 4/4/14, Jan Nijtmans wrote: > 2014-04-04 10:54 GMT+02:00 Mark Janssen : >> Why can't n-ary numbers have dots? 0b1.11 is a perfectly valid >> representation of 1.75. > > $ tcls

Re: [fossil-users] TH1: support for octal and hexadecimal numbers in expressions

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: > [the issues went away] Thank you very much! Now we have the comfo

Re: [fossil-users] TH1: support for octal and hexadecimal numbers in expressions

2014-04-04 11:06 GMT+02:00 Jan Nijtmans : > Since th1 is supposed to be a subset of Tcl, I don't think > that th1 should invent any syntax which Tcl doesn't support. > (Feel free to write a Tcl TIP, but I don't think it has a high > chance to be accepted.) Noted that the floating point format acce

Re: [fossil-users] TH1: support for octal and hexadecimal numbers in expressions

2014-04-04 10:54 GMT+02:00 Mark Janssen : > Why can't n-ary numbers have dots? 0b1.11 is a perfectly valid > representation of 1.75. $ tclsh8.6 % expr 0+0b1.1 missing operator at _@_ in expression "0+0b1_@_.1" % Since th1 is supposed to be a subset of Tcl, I don't think that t

Re: [fossil-users] TH1: support for octal and hexadecimal numbers in expressions

On Fri, Apr 4, 2014 at 10:54 AM, Mark Janssen wrote: > Why can't n-ary numbers have dots? 0b1.11 is a perfectly valid > representation of 1.75. > i would argue that in the context of fossil, which rarely uses floating point numbers and never uses binary numbers, such a feature is YAGNI[1]. Maybe

Re: [fossil-users] TH1: support for octal and hexadecimal numbers in expressions

On Fri, Apr 4, 2014 at 10:28 AM, Jan Nijtmans wrote: > > > An additional issue is that binary/octal/hex numbers cannot contain > dots, so they must be handled separately anyway. Done here: > > > > Why can't n-ary numbers have dots? 0b1.11 is

Re: [fossil-users] TH1: support for octal and hexadecimal numbers in expressions

2014-04-03 23:23 GMT+02:00 Sergei Gavrikov : > It seems that should not reload isdigit validator for octal and binary > numbers, otherwise early break on illegal digit returns bad tokens: for > example, for "0b2" sequence thNextNumber() will return "0b" token, for > "0o8" sequence it will return "0