This is the mail archive of the
mailing list for the Cygwin project.
Re: types "quad_t" & "u_quad_t"
- From: Brian Dessent <brian at dessent dot net>
- To: 'Cygwin List' <cygwin at cygwin dot com>
- Date: Mon, 07 Mar 2005 14:49:27 -0800
- Subject: Re: types "quad_t" & "u_quad_t"
- Organization: My own little world...
- References: <422CCEE0.firstname.lastname@example.org>
- Reply-to: cygwin at cygwin dot com
Linda W wrote:
> I was lamenting the lack of the simple "hexdump" facility
> I have on linux. I figured -- how difficult would it be
> to port that.
Cygwin already has the 'od' utility (in coreutils) which has the same
functionality. For example, "od -A x -v -t x1z filename" will give a
nice side-by-side hex/ascii output of a file.
> Well...not too, turns out, though, that it needs a type
> quad_t and u_quad_t defined.
As far as I know, and I could be wrong, the quad_t and u_quad_t types
are BSD-isms and not actually part of any standard. POSIX defines
int64_t and u_int64_t which would be the more portable types for a
program to use. 'hexdump' is from BSD as well so that's probably why it
uses them and not the standard ones.
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html