Timeline for Parsing XML, JSON, and newer data file formats in UNIX using command line utilities
Current License: CC BY-SA 2.5
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 4, 2011 at 21:33 | comment | added | Gilles 'SO- stop being evil' |
@kamaal: As the data format gets more sophisticated, descriptions of the operations to perform get longer. For example, perl -0777 -MJSON -e '$t=from_json(<STDIN>); do_something_with($t)' lets you process JSON with a minimum of fuss. You still have to tell the computer what to do with the data somehow.
|
|
| Mar 4, 2011 at 17:21 | comment | added | alex | @kamaal: dunno. Google? Docs for your scripting language of choice? CPAN comes to mind if you're using Perl. | |
| Mar 4, 2011 at 9:25 | comment | added | kamaal | I think I didn't understand you properly. Where can I get the 'program text'? | |
| Mar 4, 2011 at 8:48 | comment | added | alex |
Do you consider ruby -e 'program text' "writing a script"?
|
|
| Mar 4, 2011 at 8:47 | comment | added | kamaal | My whole point was to avoid writing a script and try to do it using a command instead. Writing the script will defeat the whole purpose of this question. | |
| Mar 4, 2011 at 7:10 | history | answered | alex | CC BY-SA 2.5 |