Lexer -> ID Rules

Hello,

are there any hard reasons why account names must not start with numerical values? Tackler uses the following definitions:

ID: NameStartChar (NameChar)*;

The above ANTLR fragment 'NameStartChar' excludes numbers.

In my usecase the account names uses numbers and I have no control or way to avoid that - they look like '4zifortyz64av'. A kind of mapping (x -> account) would be of course possible but would add additional complexity.

I also have to admit that I tested my accounting schema with 'hledger' until now and I'm about automating the process on the JVM and therefore Tackler is of course the first choice.

Thank you.

Regards, Jiri

Edited Mar 11, 2019 by Jiri Jetmar
Assignee Loading
Time tracking Loading