Return data from modules

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



I see that data returned by modules is often non-formatted, like this example:
{'vm2': [['384.0 KiB', '216.0 KiB', '600.0 KiB', 'udevd'],
so the app using func would have to convert those strings with KiB MiB and so on in bytes.

Why did you choose to go this way instead of reporting absolute, ready-to-use values (like bytes in an integer value)?

While I see this form is good for human consumption, it is bad to script / automatization / embeddingfuncinsomethingelse. That's why classic unix userland tools have both forms of output.

How do you see a "global" switch to choose between human- and machine- readable outputs? The commandline interface could default to human and the API to machine. Something like:
func -m $host call $mymodules blah    ---> machine-readable output
func -h $host call... ---> human-readable output
func $host call.... ---> human-readable output

Thanks,
--
Luca Lesinigo
_______________________________________________
Func-list mailing list
Func-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/func-list

[Index of Archives]     [Fedora Users]     [Linux Networking]     [Fedora Legacy List]     [Fedora Desktop]     [Fedora SELinux]     [Big List of Linux Books]     [Yosemite News]     [KDE Users]

  Powered by Linux