Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.lang.c > #18453 > unrolled thread

Write int as a 4 byte big-endian to file.

Back to article view | Back to comp.lang.c

Contents

  Write int as a 4 byte big-endian to file. MS <ms@no_spam_thanks.com> - 2012-03-10 18:00 +0000
    Re: Write int as a 4 byte big-endian to file. Don Y <this@isnotme.com> - 2012-03-10 11:11 -0700
      Re: Write int as a 4 byte big-endian to file. MS <ms@no_spam_thanks.com> - 2012-03-10 18:36 +0000
        Re: Write int as a 4 byte big-endian to file. Stephen Sprunk <stephen@sprunk.org> - 2012-03-10 14:09 -0600
          Re: Write int as a 4 byte big-endian to file. Keith Thompson <kst-u@mib.org> - 2012-03-10 14:06 -0800
            Re: Write int as a 4 byte big-endian to file. Stephen Sprunk <stephen@sprunk.org> - 2012-03-10 21:53 -0600
        Re: Write int as a 4 byte big-endian to file. Eric Sosman <esosman@ieee-dot-org.invalid> - 2012-03-10 15:20 -0500
          Re: Write int as a 4 byte big-endian to file. Eric Sosman <esosman@ieee-dot-org.invalid> - 2012-03-10 15:22 -0500
    Re: Write int as a 4 byte big-endian to file. Bl0ckeduser <bl0ckedusersoft@gmail.com> - 2012-03-10 14:42 -0500
      Re: Write int as a 4 byte big-endian to file. Bl0ckeduser <bl0ckedusersoft@gmail.com> - 2012-03-10 16:33 -0500
        Re: Write int as a 4 byte big-endian to file. Malcolm McLean <malcolm.mclean5@btinternet.com> - 2012-03-10 13:46 -0800
      Re: Write int as a 4 byte big-endian to file. Joe Pfeiffer <pfeiffer@cs.nmsu.edu> - 2012-03-10 17:42 -0700
        Re: Write int as a 4 byte big-endian to file. Bl0ckeduser <bl0ckedusersoft@gmail.com> - 2012-03-10 22:53 -0500
    Re: Write int as a 4 byte big-endian to file. Tim Rentsch <txr@alumni.caltech.edu> - 2012-03-10 11:44 -0800
      Re: Write int as a 4 byte big-endian to file. "Morris Keesan" <mkeesan@post.harvard.edu> - 2012-03-10 17:18 -0500
        Re: Write int as a 4 byte big-endian to file. Ike Naar <ike@iceland.freeshell.org> - 2012-03-10 23:00 +0000
        Re: Write int as a 4 byte big-endian to file. Tim Rentsch <txr@alumni.caltech.edu> - 2012-03-11 13:08 -0700
          Re: Write int as a 4 byte big-endian to file. tom st denis <tom@iahu.ca> - 2012-03-12 05:56 -0700
            Re: Write int as a 4 byte big-endian to file. jacob navia <jacob@spamsink.net> - 2012-03-13 00:01 +0100
              Re: Write int as a 4 byte big-endian to file. gwowen <gwowen@gmail.com> - 2012-03-13 00:55 -0700
                Re: Write int as a 4 byte big-endian to file. Ike Naar <ike@sverige.freeshell.org> - 2012-03-13 09:56 +0000
                Re: Write int as a 4 byte big-endian to file. Ben Bacarisse <ben.usenet@bsb.me.uk> - 2012-03-13 12:26 +0000
                Re: Write int as a 4 byte big-endian to file. Tim Rentsch <txr@alumni.caltech.edu> - 2012-03-13 16:04 -0700
            Re: Write int as a 4 byte big-endian to file. Tim Rentsch <txr@alumni.caltech.edu> - 2012-03-13 15:54 -0700
    Re: Write int as a 4 byte big-endian to file. Sjouke Burry <s@b> - 2012-03-10 19:44 +0000
      Re: Write int as a 4 byte big-endian to file. "Morris Keesan" <mkeesan@post.harvard.edu> - 2012-03-10 17:21 -0500
    Re: Write int as a 4 byte big-endian to file. "Morris Keesan" <mkeesan@post.harvard.edu> - 2012-03-10 14:57 -0500
      Re: Write int as a 4 byte big-endian to file. Ike Naar <ike@iceland.freeshell.org> - 2012-03-10 21:17 +0000
        Re: Write int as a 4 byte big-endian to file. "Morris Keesan" <mkeesan@post.harvard.edu> - 2012-03-10 17:22 -0500
    Re: Write int as a 4 byte big-endian to file. Lew Pitcher <lpitcher@teksavvy.com> - 2012-03-10 15:55 -0500
    Re: Write int as a 4 byte big-endian to file. Geoff <geoff@invalid.invalid> - 2012-03-10 13:01 -0800
      Re: Write int as a 4 byte big-endian to file. Stephen Sprunk <stephen@sprunk.org> - 2012-03-10 22:01 -0600
        Re: Write int as a 4 byte big-endian to file. Malcolm McLean <malcolm.mclean5@btinternet.com> - 2012-03-11 00:36 -0800
      Re: Write int as a 4 byte big-endian to file. "io_x" <a@b.c.invalid> - 2012-03-13 12:29 +0100
        Re: Write int as a 4 byte big-endian to file. "io_x" <a@b.c.invalid> - 2012-03-13 13:14 +0100
    Re: Write int as a 4 byte big-endian to file. Malcolm McLean <malcolm.mclean5@btinternet.com> - 2012-03-10 12:39 -0800
      Re: Write int as a 4 byte big-endian to file. "Morris Keesan" <mkeesan@post.harvard.edu> - 2012-03-10 17:29 -0500
        Re: Write int as a 4 byte big-endian to file. Malcolm McLean <malcolm.mclean5@btinternet.com> - 2012-03-10 15:02 -0800
          Re: Write int as a 4 byte big-endian to file. "Morris Keesan" <mkeesan@post.harvard.edu> - 2012-03-11 18:26 -0400
    Re: Write int as a 4 byte big-endian to file. Ben Bacarisse <ben.usenet@bsb.me.uk> - 2012-03-10 21:12 +0000
    Re: Write int as a 4 byte big-endian to file. jgk@panix.com (Joe keane) - 2012-03-11 21:29 +0000
      Re: Write int as a 4 byte big-endian to file. Ian Collins <ian-news@hotmail.com> - 2012-03-12 10:34 +1300
        Re: Write int as a 4 byte big-endian to file. jgk@panix.com (Joe keane) - 2012-03-12 21:37 +0000
          Re: Write int as a 4 byte big-endian to file. Keith Thompson <kst-u@mib.org> - 2012-03-12 23:40 -0700
            Re: Write int as a 4 byte big-endian to file. Kaz Kylheku <kaz@kylheku.com> - 2012-03-13 07:11 +0000
      Re: Write int as a 4 byte big-endian to file. Ben Bacarisse <ben.usenet@bsb.me.uk> - 2012-03-11 21:45 +0000

Page 3 of 3 — ← Prev page 1 2 [3]

#18554

'fread' reads an array of bytes ['char *']

'fwrite' writes an array of bytes ['char *']

passing an 'int *' or 'struct foo *' [with a cast to defeat the type
system] is at best unportable and at worst really broken

[toc] | [prev] | [next] | [standalone]

#18555

On 03/12/12 10:29 AM, Joe keane wrote:
> 'fread' reads an array of bytes ['char *']
>
> 'fwrite' writes an array of bytes ['char *']
>
> passing an 'int *' or 'struct foo *' [with a cast to defeat the type
> system] is at best unportable and at worst really broken

Are you replying to something?

-- 
Ian Collins

[toc] | [prev] | [next] | [standalone]

#18607

In article <9s4k3mFa8vU4@mid.individual.net>,
Ian Collins  <ian-news@hotmail.com> wrote:
>Are you replying to something?

The subject line starts with "Re: ".

On my machine, you press left-arrow key.

In this here case, the subject line is fine, and the text is just a
recapitulation, explaining that he can't solve the problem [which is
implied, otherwise why the article?].

[toc] | [prev] | [next] | [standalone]

#18640

jgk@panix.com (Joe keane) writes:
> In article <9s4k3mFa8vU4@mid.individual.net>,
> Ian Collins  <ian-news@hotmail.com> wrote:
>>Are you replying to something?
>
> The subject line starts with "Re: ".
>
> On my machine, you press left-arrow key.
>
> In this here case, the subject line is fine, and the text is just a
> recapitulation, explaining that he can't solve the problem [which is
> implied, otherwise why the article?].

Not all Usenet clients make it easy to see the parent article.
Mine does, but then it's not necessarily trivial to get back to the
article I was reading (multiple articles can have the same parent).
That's why most of us, out of consideration for our readers, quote
enough context for each followup to make sense when read on its own.


-- 
Keith Thompson (The_Other_Keith) kst-u@mib.org  <http://www.ghoti.net/~kst>
    Will write code for food.
"We must do something.  This is something.  Therefore, we must do this."
    -- Antony Jay and Jonathan Lynn, "Yes Minister"

[toc] | [prev] | [next] | [standalone]

#18641

On 2012-03-13, Keith Thompson <kst-u@mib.org> wrote:
> Not all Usenet clients make it easy to see the parent article.

Not all homes have running water. So what?

[toc] | [prev] | [next] | [standalone]

#18557

jgk@panix.com (Joe keane) writes:

> 'fread' reads an array of bytes ['char *']
>
> 'fwrite' writes an array of bytes ['char *']

Did you have a nightmare where you woke up in 1979?  It's been a while
since fread and fwrite had char * parameters.

> passing an 'int *' or 'struct foo *' [with a cast to defeat the type
> system] is at best unportable and at worst really broken

It's perfectly well-defined, needs no cast, and is a common idiom.

-- 
Ben.

[toc] | [prev] | [standalone]

Page 3 of 3 — ← Prev page 1 2 [3]

Back to top | Article view | comp.lang.c

csiph-web