-
Notifications
You must be signed in to change notification settings - Fork 87
Cleanup of API for reading and writing #397
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Labels
Comments
UDDTIO would be really nice. |
Why not just give users |
|
Perhaps the new API should be: json_file.print ! json_file_print_to_console (me )
! json_file_print_to_unit (me, iunit )
! json_file_print_to_filename(me, filename )
json_file.load ! json_file_load (me, filename, unit )
json_file.serialize ! json_file_load_from_string (me, str )
json_file.deserialize ! json_file_print_to_string (me, str )
json_core.print ! json_print_to_console (json, p )
! json_print_to_unit (json, p, iunit )
! json_print_to_filename(json, p, filename )
json_core.load ! json_parse_file (json, file, p, unit )
json_core.serialize ! json_parse_string (json, p, str )
json_core.deserialize ! json_value_to_string (json, p, str )
|
Closed
# for free
to join this conversation on GitHub.
Already have an account?
# to comment
I'm thinking of adding
read
andwrite
generic procedures to replace (or that could be used in addition to) the various routines:Or also maybe also consider UDDTIO?
The text was updated successfully, but these errors were encountered: