| Age | Commit message (Collapse) | Author |
|---|
|
The order will be determined by hashes, but it doesn't matter which one
goes where.
|
|
I ended up never using this code - it was simpler to just use lists of
units and values. Making a whole new object for lists of units, and an
abstract class for things that convert things other than doubles, is
needlessly complicated, and doesn't solve any major issues. For
example, I still need to store each Unitlike type in a different
collection, because it will have a different type.
|
|
|
|
Most of the internal problems with the expression parser happened
because I was accepting the arguments for binary operators in the wrong
order. For example, '2 - 1' became '1 2 -', not '2 1 -'.
The likely cause of this error is the following sequence of events:
- In commit 6dbd32cd, I created the code for interpreting RPN. I
accepted two arguments from the stack (o1 and o2), then performed o1
<op> o2. However, because stacks are in LIFO order, I should have
actually done o2 <op> o1.
- Later, in commit 94349688, I created the code for converting an infix
expression to RPN. Creating the expressions in the correct order did
not work, because my interpreter used the incorrect order. To 'fix'
this problem, I created the expressions in the incorrect order. I did
not notice any discrepancy, probably because I was not testing the
individual methods, only the two-step whole (which found no errors).
|
|
These tests fail right now, because ExpressionParser has a bug. They
should help me fix it.
|
|
./gradlew javadoc
|
|
|
|
|
|
|
|
|
|
I am not adding it to build yet since my javadoc has problems, but I
will once those are fixed.
|
|
This is a necessary precondition for the conversion methods used later
on in convertToMutliple, and it is simpler than the existing method.
I can also be sure it works, due to the tests I just wrote.
|
|
I specifically added tests for the methods that Jacoco says haven't been
tested:
- convertToMultiple
- equals
- equivalent
- hashCode
- operation methods
|
|
Compared to version 0.5.0, this release:
- allows conversion to sums of units (e.g. 4/3 ft → 1 ft + 4 in)
- allows non-integer exponents in expressions
- adds the ability to change the UI language
- gracefully handles datafile errors
- adds more information to the loading-success message, and adds it to
the About tab
- allows the user to not use the default datafiles
No new features will be added until the release of version 1.0.0.
|
|
|
|
This merge adds the internationalization features, the final required
feature for 7Units version 1.0.0.
|
|
This works with custom locales (by placing the text in
[config_dir]/about/[name].txt), but if such a file does not exist, it
will default to the default locale (en)'s about text.
|
|
If this option is deselected, the default unit, prefix, dimension and
metric exception data will not be loaded, and only custom data and the
few units that are not provided by files will be available.
The main rationale for this change is so that the data can be localized
by custom unit files.
|
|
|
|
|
|
|
|
|
|
This commit intentionally fails one test, since that is for
functionality I intend to add later.
|
|
|
|
|
|
|
|
Previously, any error in the unit or dimension file(s) crashes the
program. Instead, 7Units now ignores any invalid lines, still parsing
the correct ones, and shows a popup in case any errors happen.
|
|
This ensures that small errors from floor arithmetic will not, for
example, cause 2 feet to be converted to 1 foot + 12 in.
|
|
|
|
|
|
These values are guaranteed to be integers, so printing them without a
decimal point looks nicer and saves space.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| is like /, but with higher precedence. This feature is a part of GNU
Units, and was included in 7Units for compatibility.
|
|
|
|
|
|
Previously, you could only exponentiate individual dimensions in
expressions. For example, `Length^3` was valid, but `(Length / Time)^2`
was not. This is now fixed.
|
|
This was added to be consistent with the data file spec, which was
changed for consistency with unit expressions. It may not be a common
expression, but it's a bit weird that you can use +/- in units but not
prefixes, even though they're in the same file!
|
|
|
|
I will have to change a few things to fit this specification; all the
better that I made it instead of leaving behaviour unspecified!
|
|
|
|
|
|
|
|
|
|
These changes should reduce nesting and increase readability.
|
