On 08/05/15 14:29, Stephan Müller wrote:
> It seems you implemented a subset of the functionality of 'od' or 'xxd'
 >from coreutils. I guess these are widely spread and there is no need for
 >another converter (albeit the cooler name). If hexed provides some extra
 >features, you can integrate those in the tools above.

xxd seems a perfect replacement for hexed :P


FWIW, I see a number of quirks in your tool, Hypsurus:
a) Options have to be provided *after* the string
Usually options always appear at the beginning (just after the program 
name) and -when _POSIXLY_CORRECT is not set- the gnu optlib then allows 
placing them at any position.

b) The program crashes if the string begins with a dash (str is NULL).


c) You program requires the string to be passed as parameter.
All programs like this have *filenames* as parameters. Consistency is 
even more important for a program like this, that mimics the interfaces 
of many other programs working the other way.
And receiving filenames makes much more sense. Do you really want to 
type the binary contents as a program parameter? Does your OS even allow 
that large? etc.

With a program that receives a filename, you can provide a string with
  echo string | hexed

with a program that receives the string, you need a construct like:
  hexed "$(</etc/passwd)"
and only if you use bash, the file is small enough to be passed as a 
parameter and it doesn't contain any NUL (which defeats the point of an 
hexer).


d) You have a number of signedness warnings, you are assgning a size_t 
to an int and, generally, it would have been much easier for 
hexed_hex_encode to work with unsigned char and hexed_hex_decode with 
chars. See attached patch.