Hi Tom,
good to hear from you. It was my miss-understanding of what the code was
doing, not the issue with the compiler :>
At 03:22 PM 7/19/2005, Tom Lane wrote:
Chris Bowlby <[EMAIL PROTECTED]> writes:
> I understand the concept of the code, to append binary values to a string
> buffer (cha
Ahh, so it's not attempting to turn it into an "acsii" string, just storing
raw binary data... Ok that makes sense now, thanks for the help.
At 02:54 PM 7/19/2005, Korry wrote:
If I understand the code right, your trying to pass in to
appendBinaryStringInfo an "address" or reference to the n8
Chris Bowlby <[EMAIL PROTECTED]> writes:
> I understand the concept of the code, to append binary values to a string
> buffer (char *), but, under my compiler on FreeBSD 5.4.x (gcc (GCC) 3.4.2
> [FreeBSD] 20040728) I see a few issues that have cropped up.
You've got a broken compiler then, becau
If I understand the code right, your trying to pass in to
appendBinaryStringInfo an "address" or reference to the n8, n16, or n32
variables and cast them so that a char * pointer can access that address
space. Through some testing that I've been doing (outputting the values in
the appendB
Hi All,
I've been doing a code audit (review) for my own personal use of the
7.4.x series code base and have come across something that I'd like to get
more details on, if it is possible to do so.
I've been going over the communications section and am curious how this
segment of code is ac
