On Sun, 4 May 2008 14:53:08 -0400, Gerhard Postpischil wrote: >Paul Gilmartin wrote: >> it if it exists regardless of syntax rules). If the designers >> intended to support mixed case names, as STOW and BLDL do, TSO, >> ISPF, and other utilities should not overrule their design by >> forcing input to upper case, particularly if the member name > >You're imputing too much into the design. When OS/360 was first >written, there were no keypunches with lower case, and no way to >place lower case letters on an IEBUPDTE ./ ADD or LKED NAME >statement (short of overpunching). The lack of case conversion >was more likely a decision of convenience in implementation, >rather than intent. Otherwise we'd need to conclude that they >also meant percent signs and other funny characters to be legal, > You've mentioned overpunching. And in assembler it was also possible to enter any character in hex in an argument to STOW or BLDL. My point of dissatisfaction is with other languages which have chosen to restrict the syntax short of what the OS accepts.
May I not conclude from the fact that STOW accepts "percent signs and other funny characters" that the designers intended them to be legal? (But I haven't tried lately; does STOW nowadays place such restrictions on member name syntax?) -- gil ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
