Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!sol.ctr.columbia.edu!lll-winken!uunet!lupine!rfg
From: rfg@NCD.COM (Ron Guilmette)
Newsgroups: comp.std.c
Subject: Re: Apollo speaks (was How ANSI is Apollo's cc 6.7 (SR 10.2))
Message-ID: <1570@lupine.NCD.COM>
Date: 13 Sep 90 16:09:35 GMT
References: <15434@reed.UUCP> <4cc44d3a.20b6d@apollo.HP.COM>
Organization: Network Computing Devices, Inc., Mt. View, CA
Lines: 14

In article <4cc44d3a.20b6d@apollo.HP.COM> smv@apollo.hp.com writes:
>
>In other areas, <ctype.h> for example, it was not possible to provide the
>functionality required by ANSI C with the existing symbols.  The changes
>made to solve these problems will be with us in both strict and extended
>ANSI modes.

I'd like to see some elaboration on this.  What exactly is so special about
<ctype.h>?
-- 

// Ron Guilmette  -  C++ Entomologist
// Internet: rfg@ncd.com      uucp: ...uunet!lupine!rfg
// Motto:  If it sticks, force it.  If it breaks, it needed replacing anyway.