2011/8/13 Stéphane Ducasse <[email protected]>: >> >> The thing that upsets me most is auto-formatting of literals. >> >> 1) the formatter SHALL try to preserve the indenting of array literals >> A 256 elements table organised in a 16x16 fashion can be legible. >> A rough 256 element suit is not. >> 2) the formatter SHALL preserve the base used to specify a number literal >> If i write 2r1011 it's clearly not my intention to read 11. >> It's the same for number composing a literal array/byte array >> >> In other words, the literals shall better be left unchanged. >> >> The second thing that is annoying is that it can become hard to >> compare code and track evolutions. >> But this one is just a question of having the right tool to perform >> the comparison... >> I always thought that MC, change list and friends should propose an >> option that simply compares scanned tokens and optionnally ignore >> comments. > > 100% with you. > Marcus made progress on OPAL and once we have AST in the image (now we have > it) > we should really invest in bringing the tools to another level. > I hope that we will stop cleaning but really defining new tools. > > Stef >
IMO a lexical comparison with a Scanner should be enough. Nicolas
