-
-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
regex_dat: the order of the overrides is not specified in the spec #19
Comments
Can be fixed "simply" if we ignore repeat overrides (ie: Original regexr"""=?(?P<prefix>[a-zA-Z0-9/]+)
(?:\((?P<cq>\d+)\))?
(?:\[(?P<itu>\d+)\])?
(?P<latlong>
<(?P<lat>[+-]?\d+(?:\.\d+)?)
\/
(?P<long>[+-]?\d+(?:.\d+)?)>
)?
(?:\{(?P<continent>\w+)\})?
(?:~(?P<tz>[+-]?\d+(?:\.\d+)?)~)?""" Fixed(?) regexr"""=?(?P<prefix>[a-zA-Z0-9/]+)
(?:
(?:\((?P<cq>\d+)\))
| (?:\[(?P<itu>\d+)\])
| (?P<latlong>
<(?P<lat>[+-]?\d+(?:\.\d+)?)
\/
(?P<long>[+-]?\d+(?:.\d+)?)>
)
| (?:\{(?P<continent>\w+)\})
| (?:~(?P<tz>[+-]?\d+(?:\.\d+)?)~)
)*""" The main problem is that the regex complexity then jumps upwards dramatically |
oof damn. good catch |
We need to choose how we approach this. Note on the "fixed" regex: it's unclear how it would handle a case where multiple overrides of the same types are present for a since call/prefix. |
Other question: Do we decide of that before or after release of 2.0.0? |
I think decide later |
It isn't specified in neither the country-files page or the CT9 manual.
The text was updated successfully, but these errors were encountered: