[Subject Prev][Subject Next][Thread Prev][Thread Next][Subject Index][Thread Index]

# Re: Server limitations on network I/O

- Date: 21 Jul 1997 18:57:08 +0200
- From:
- Cc: moo-cows@the-b.org, jnolan@oise.utoronto.ca
- In-Reply-To: Michael Brundage's message of Sat, 19 Jul 1997 16:47:31 -0700 (PDT)
- References: <Pine.SOL.3.91.970719164654.629B-100000@laurel>

    >>>>> "Michael" == Michael Brundage <brundage@laurel.ipac.caltech.edu> writes:

        Michael> Couple o' questions: (1) What is the range of ASCII
        Michael> values which the server will accept (or output) through
        Michael> non-binary I/O?

    Jason, this applies to your problem too. The server uses the isgraph
    macro to test wether the current character is printable. It
    additionally checks for whitespace. The meaning of isgraph depends on
    the locale on some systems. Usually, isgraph is true if it's argument
    is above 32 and less than or equal to 127.

    The best approach for internationalization is to replace this function
    with a hand-rolled.

    Andreas

    --
    Never underestimate the value of fprintf() for debugging purposes.

References:

- Server limitations on network I/O

- From: Michael Brundage <brundage@laurel.ipac.caltech.edu>

- Prev by Subject: Server limitations on network I/O
- Next by Subject: Re: server messages in the database
- Prev by thread: Server limitations on network I/O
- Next by thread: floats and efficiency
- Index(es):
  - Subject
  - Thread

Home | Subject Index | Thread Index