Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!unix.cis.pitt.edu!brutus.cs.uiuc.edu!psuvax1!psuvm!psuecl!c9h
From: c9h@psuecl.bitnet
Newsgroups: comp.lang.c
Subject: Re: C/370 is case insensitive, and just generally rots!
Message-ID: <72095@psuecl.bitnet>
Date: 13 Dec 89 21:46:53 GMT
References: <71894@psuecl.bitnet> <1989Dec13.173114.10295@ultra.com>
Organization: Engineering Computer Lab, Pennsylvania State University
Lines: 31

In article <1989Dec13.173114.10295@ultra.com>, ted@ultra.com (Ted Schroeder) writes:
> c9h@psuecl.bitnet writes:
>
> Well, not exactly.  IBM C/370 is case sensitive AS long as the data is local.
> I'm sure that globals are not case sensitive in Waterloo C either since the
> linker/loader doesn't support case.  It also doesn't support the "_" character
> and symbols can only be 8 chars long.  ("_" chars get turned into the "@" char
> automatically by the compiler).

Funny ...  Maybe Waterloo C knows something ...  Perhaps it has a better
way to handle this ...  Hell, I don't know.  All I know is that *it* doesn't
bitch and moan when I have too identifiers varying only in case.

> By the way, I've done a pretty major port of a Unix device driver for our
> product into VM and have had not a single issue with the compiler.  Now the
> loader, that I've got my opinions about, but let's not bad mouth the compiler
> when it's the rest of the IBM support you're really pissed about.

Your *damned* right I'm pissed.  Our people ordered the manual(s) with the
compiler (oh, about seven or eight months ago), and the manuals still aren't
here.


BTW:  I just checked.  WATC *is*, in every aspect, case sensitive.

--
- Charles Martin Hannum II       "Klein bottle for sale ... inquire within."
    (That's Charles to you!)     "To life immortal!"
  c9h@psuecl.{bitnet,psu.edu}    "No noozzzz izzz netzzzsnoozzzzz..."
  c9h@eclx.psu.edu               "Mem'ry, all alone in the moonlight ..."
  c9h@hcx.psu.edu
  cmh@psuecl2.bitnet