After a bit of (archaeological) digging, it appears our manuals are
incorrect and that we've visited this issue before.
When HLASM 1.4 development was in full flight, the CODEPAGE option was
added. This appears to have fallen victim to the short-on-os-storage issue
- and the coded 128k value was
Thank you very much
On 28.02.2014 12:26, Sharuff Morsa3 wrote:
After a bit of (archaeological) digging, it appears our manuals are
incorrect and that we've visited this issue before.
When HLASM 1.4 development was in full flight, the CODEPAGE option was
added. This appears to have fallen
On 2014-02-25, at 10:00, John Walker wrote:
So, to respond to the one comment, it was ok for the Science guys to want
mixed case things because that was what they were used to. Ok, I can buy
that. Same rationale can be applied to the C programmers. Now, let's be
fair, using the very
I think this discussion needs to distinguish clearly between case-sensitive
(treating caps and lower case the same) and case-insensitive (treating the
upper and lower case of the same character as different). Mixed-case
could mean either, and is therefore unclear.
IMHO, case-insensitivity is not
IBM Mainframe Assembler List ASSEMBLER-LIST@LISTSERV.UGA.EDU wrote on
02/28/2014 11:18:33 AM:
From: Hobart Spitz orexx...@gmail.com
I think this discussion needs to distinguish clearly between
case-sensitive
(treating caps and lower case the same) and case-insensitive (treating
the
upper and
I should be be on John Walker's side if 'z/OS' were telling him that
he may no longer write his routines in headlines. As it is, what he
appears to be saying is that I must write mine in headlines too; and I
am unsympathetic, even hostile to that notion.
He is and should be free to continue what
English (and other Latin-alphabet languages) is mostly
case-INsensitive. There's sometimes a difference between Bill and bill,
but bILL, BILL, bIlL are just silly versions of the same word.
There are some conventions in some c-based languages of using a symbol
with a leading Capital letter, and
I'm currently out of the office with no access to email.
I'll reply to your note as soon as I return.
Have a great day,
Steve
I will be out of the office, returning Monday March 10th. I will respond to
your email ASAP once I am back.
In the meantime if you require an urgent response, please contact our Customer
Support Centre on 212-855-1541.
BR_
FONT
From: Steve Smith sasd...@gmail.com
Sent: Saturday, March 01, 2014 9:56 AM
English (and other Latin-alphabet languages) is mostly
case-INsensitive. There's sometimes a difference between Bill and bill,
but bILL, BILL, bIlL are just silly versions of the same word.
But iTunes isn't?
When I said, ' So, to respond to the one comment, it was ok for the Science
guys to
want mixed case things because that was what they were used to. Ok, I can
buy that. Same rationale can be applied to the C programmers. Now, let's
be fair, using the very same reasoning, I can then justify
At 11:18 -0500 on 02/28/2014, Hobart Spitz wrote about Re: CamelCase
(was: ASSEMBLER-LIST Digest ...):
I think this discussion needs to distinguish clearly between case-sensitive
(treating caps and lower case the same) and case-insensitive (treating the
upper and lower case of the same
At 11:28 -0500 on 02/28/2014, Kirk Talman wrote about Re: CamelCase
(was: ASSEMBLER-LIST Digest ...):
Making STUFF stuff Stuff sTuff ... have different meanings is not as
fault-tolerant as it could be.
OTOH: Polish and polish ARE not the same. Telling someone in the army
to You should Polish
13 matches
Mail list logo
