| 1 |
Revision history for Geo::LibProj::FFI |
| 2 |
|
| 3 |
1.01 2025-02-19 |
| 4 |
|
| 5 |
- Fix segmentation fault on armel and armhf. (GH #4) (Andreas Vögele) |
| 6 |
|
| 7 |
1.00 2024-05-12 |
| 8 |
|
| 9 |
- Documentation update: Future major changes are no longer expected for this |
| 10 |
module. The version number is incremented to reflect that the interface is |
| 11 |
now considered stable. |
| 12 |
|
| 13 |
- No functional changes. |
| 14 |
|
| 15 |
0.06 2023-12-05 |
| 16 |
|
| 17 |
- Fix compatibility with Perl v5.26 and older. (GH #3) |
| 18 |
|
| 19 |
0.05 2023-12-01 |
| 20 |
|
| 21 |
- Add new PJ_COORD struct member accessors. Instead of calling $c->xyz->x(), |
| 22 |
you can now simply call $c->xyz_x(), which is faster and more likely to |
| 23 |
remain stable with future updates. The old syntax is now discouraged, |
| 24 |
but there are currently no plans to remove it. |
| 25 |
|
| 26 |
- Deprecate creating PJ_COORD union member structs with new(). Unions are not |
| 27 |
well supported by FFI::Platypus. For best forward compatibility, creating |
| 28 |
new PJ_COORD values should only be done by using proj_coords(). |
| 29 |
|
| 30 |
- Internal change: The PJ_COORD implementation is now based on the vector |
| 31 |
union member. This means the fastest way to access coordinates is now |
| 32 |
via $c->v(...) instead of $c->xyzt->... |
| 33 |
|
| 34 |
0.04 2021-05-24 |
| 35 |
|
| 36 |
- Add area of interest functions |
| 37 |
- Add distances functions |
| 38 |
- Add error-state manipulation functions |
| 39 |
- Add info functions |
| 40 |
- Add lists functions |
| 41 |
- Add logging functions |
| 42 |
|
| 43 |
0.03 2021-05-21 |
| 44 |
|
| 45 |
- Address performance issues with PJ_COORD values |
| 46 |
- Add brief description of how to work with PJ_COORD values |
| 47 |
and other PROJ data types to the documentation |
| 48 |
|
| 49 |
0.02 2021-03-04 |
| 50 |
|
| 51 |
- Resolve failures reported in CPAN Testers (GH#1 and others) |
| 52 |
|
| 53 |
0.01 2021-03-03 |
| 54 |
|
| 55 |
- Release to CPAN |
| 56 |
- Only a few essential functions are available, just enough |
| 57 |
to support Geo::LibProj::cs2cs and a simple example |