| aida_2012 | VSS | |
|---|---|---|
| 2 | 3 | |
| 14 | 49 | |
| - | - | |
| 0.0 | 9.4 | |
| about 5 years ago | 11 days ago | |
| Ada | Ada | |
| - | GNU General Public License v3.0 or later |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
aida_2012
-
Simple JSON library with little or no dependencies?
Some years ago I wrote a JSON parser, see for example https://github.com/joakim-strandberg/aida_2012/blob/master/src/tests/aida-json_dom_parser_tests.adb. I've been thinking of refactoring but never gotten around to do it. One of the ideas for writing the code was minimizing external dependencies. The JSON parser is written in SPARK and at the time 2018 when the code was written SPARK did not allow heap allocations which means all the data-structures used are statically allocated. I can imagine onox json-ada has a nicer API.
-
New Ada Folks (<2 years), what made you pick up (or leave) Ada?
For getting UTF-8 support one can also use Dmitry Kazakovs Simple components (http://www.dmitry-kazakov.de/ada/components). Based on it have made a UTF-8 version which is Ada/Spark based (https://github.com/joakim-strandberg/aida_2012). Another one I have been toying with is cross-compiler: https://github.com/joakim-strandberg/portable_ada . To print to standard out using UTF-8 the easiest way is probably enabling "-gnatW8" in order for normal String types be interpreted as UTF-8 strings. Using the UTF-8 support in the links I would recommend making one's own Ada bindings to the OS. It should be easy to do on Mac OS X and Linux where UTF-8 is enabled by default but more of an issue on Windows where the UTF-8 encoded strings need to be converted to UTF-16 before being handed over to the OS.
VSS
-
Looking for feedback: ISO 3166-1 country Country Code Reference for Ada
But the most difficult decision here is not to use String. The library doesn't stay in a vacuum. Perhaps it will be used as part of some information system. Using String in a information system would be a pain. The user won't be able to have country name together with emoji! This not acceptable nowadays! Wide_(Wide_String) as well as other standard string types (Unbounded_*, Bouded_*) are not good too. Perhaps it's good time to switch to something else, like VSS.
-
New Ada Folks (<2 years), what made you pick up (or leave) Ada?
I plan on using VSS to handle UTF-8.
-
gnatdoc output improvements
if you like this style you can replace gnatdoc.css.
What are some alternatives?
portable_ada
trendy_terminal - A Windows/Linux library for enabling terminal settings and driving character-by-character input.
grpc-rust - Rust implementation of gRPC
prometheus - Prometheus.io Haskell client.
tokio - A runtime for writing reliable asynchronous applications with Rust. Provides I/O, networking, scheduling, timers, ...
tonic - A native gRPC client & server implementation with async/await support.
prometheus-client - Haskell client library for exposing prometheus.io metrics.
rust_iso3166 - ISO 3166 is a standard published by the International Organization for Standardization (ISO) that defines codes for the names of countries, dependent territories, special areas of geographical interest, and their principal subdivisions (e.g., provinces or states). The official name of the standard is Codes for the representation of names of countries and their subdivisions.
iso_3166 - ISO Standard references for Ada such as ISO 1366 country codes. [Moved to: https://github.com/ada-iso/ada_iso]