NetNews Usenet Archive 1992 #30/NN_1992_30.iso/spool/comp/lang/c/18485

Internet Message Format | 1992-12-16 | 1.6 KB

Xref: sparky comp.lang.c:18485 comp.std.c:3218
Path: sparky!uunet!tdat!tools3!swf
From: [e-mail] (Stan Friesen)
Newsgroups: comp.lang.c,comp.std.c
Subject: Re:  Is this ANSI: final (long)
Message-ID: <[e-mail]>
Date: 16 Dec 92 19:19:33 GMT
References: <[e-mail]> <[e-mail]> <[e-mail]> <[e-mail]> <[e-mail]>
Sender: [e-mail]
Distribution: world
Organization: NCR Teradata Database Business Unit
Lines: 30

In article <[e-mail]>, [e-mail] (Martin Weitzel) writes:
|> In article <[e-mail]> [e-mail] (Gary Merrill) writes:
|> :In article <[e-mail]>, [e-mail] (Ross Smith) writes:
|> :|>
|> :|> ... Why not just
|> :|> use a pointer instead of kludging it up with a fake array?
|> :|> [example deleted]
|> :
|> :The point is this:  If you are dynamically allocating *both* the
|> :structure and the data, the approach you suggest requires *two*
|> :separate allocations (and two separate frees if you will be freeing
|> :the stuff). ...
|>
|> Yes, and there's another point:  With a single allocation you may
|> memcpy/memmove/memcmp/[f]read/[f]write the whole easily. ...

Of course you could solve both problems by using the solution we came up with here:

    struct data {
        char    *dptr
        ...
    };

    struct data *dp = malloc(sizeof(struct data) + strlen(string));
    dp->dptr = (char *)dp + sizeof(struct data);

--
[e-mail]            (formerly tdatirv!sarima)
  or
[e-mail]