7Units/src/test/java/sevenUnits/utils, branch stableA unit converter made in Java, inspired by GNU Units
https://git.ahopkins.ca/7units.git/atom?h=stable2025-06-16T00:37:19ZBump version number to 1.0.02025-06-16T00:37:19ZAdrien Hopkinsadrien.p.hopkins@gmail.com2025-06-16T00:37:19Zurn:sha1:bccb5b5e3452421c81c1fb58f83391ba6584807cFormat & clean up source code2025-06-16T00:26:12ZAdrien Hopkinsadrien.p.hopkins@gmail.com2025-06-16T00:26:12Zurn:sha1:da740edd3972fa049c4c8d0e43448c10a6a65dceAdd version numbers to all @since tags2025-06-05T00:45:37ZAdrien Hopkinsadrien.p.hopkins@gmail.com2025-06-05T00:45:37Zurn:sha1:79e1653caf5c30667877a158433cbcd766a135af
Specifically, for every @since tag with a date, I added another that
contains the correspending version. I did not add date @since tags to
comments that do not have them, as that would be too tedious for what
it's worth. These dates could still be found by using git bisect
though.
Update copyright notices' years2025-06-05T00:40:14ZAdrien Hopkinsadrien.p.hopkins@gmail.com2025-06-04T23:58:15Zurn:sha1:d80b80857e739eb32afd7625789944abd3afe376
I used the Git history for years after 2019, and only included 2019 or
2018 if they were already there. I also added copyright notices to all
code files that don't already have them.
ExpressionParser: use correct operand order2025-05-31T00:54:17ZAdrien Hopkinsadrien.p.hopkins@gmail.com2025-05-21T23:23:35Zurn:sha1:4cb7e4eb4a9213304ee5b83c9aaa0427e9a8fe31
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).
Add tests for submethods of ExpressionParser2025-05-21T23:20:44ZAdrien Hopkinsadrien.p.hopkins@gmail.com2025-05-21T22:59:40Zurn:sha1:779bf983226f9799dc19d84a3f2cb9a3e26cd540
These tests fail right now, because ExpressionParser has a bug. They
should help me fix it.
Add tests for NameSymbol2025-03-21T20:26:01ZAdrien Hopkinsadrien.p.hopkins@gmail.com2025-03-21T20:26:01Zurn:sha1:99ef729b27377b440b15757b789101c7ed87aec1Correct encoding of ±2024-08-15T22:26:34ZAdrien Hopkinsadrien.p.hopkins@gmail.com2024-08-15T21:47:24Zurn:sha1:fbb2f4a997e7e7043a2bdf15303b88907f6bcbc6Format source code & set explicit UTF-82024-03-24T18:14:11ZAdrien Hopkinsadrien.p.hopkins@gmail.com2024-03-24T18:14:11Zurn:sha1:26291e672b0e683edc9d57710a9a9d96ca199c45Added documentation to undocumented tests2022-07-09T18:53:26ZAdrien Hopkinsahopk127@my.yorku.ca2022-07-09T18:53:26Zurn:sha1:8b124b2437d53d70444f31ef52e00b8d7463c636