From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] 8c padding problem
Date: Fri, 21 Dec 2007 23:34:42 -0500 [thread overview]
Message-ID: <0d2806b422357c14fe6a163193958bf3@quanstro.net> (raw)
In-Reply-To: <775b8d190712212025v2ee285e9rcc6507000c6289b7@mail.gmail.com>
> excuse me. that's what hjdicks was for .. and it's called pack. ok.
>
> abuse them or yourselfs for using such code.
>
> brucee
what's the alternative? what i can think of is either
cutting & pasting the repeated elements or not using
unnamed structures at all. unfortunately, that results
in awful code like so
h = (hdr*)buf;
p = (proto*)h->data;
e = (subprobo*)p->data;
- erik
next prev parent reply other threads:[~2007-12-22 4:34 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-21 23:10 erik quanstrom
2007-12-21 23:24 ` Martin Neubauer
2007-12-22 0:00 ` erik quanstrom
2007-12-21 23:48 ` Skip Tavakkolian
2007-12-21 23:52 ` erik quanstrom
2007-12-21 23:59 ` Skip Tavakkolian
2007-12-22 0:20 ` erik quanstrom
2007-12-22 4:25 ` Bruce Ellis
2007-12-22 4:34 ` erik quanstrom [this message]
2007-12-22 4:41 ` Bruce Ellis
2007-12-22 11:09 ` C H Forsyth
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=0d2806b422357c14fe6a163193958bf3@quanstro.net \
--to=quanstro@quanstro.net \
--cc=9fans@cse.psu.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).