Re: Idea for a possible enhancement to z architecture

2012-01-02 Thread Bernd Oppolzer
Thank you for making clear that the different behaviour depends on the operating system, not on the hardware. Some slightly off-topic remarks: I've seen the (null) output on NULL string pointers on printf with other compilers, too (maybe Windoze, but I don't recall - no segmentation in this

Automatická odpověď: Idea for a possible enhancement to z architecture

2012-01-02 Thread Tancer, Jiri
I am sorry for my absence. I will be back on Monday 18.7.2011. Thanks Jiri

Re: Idea for a possible enhancement to z architecture

2012-01-02 Thread Bernd Oppolzer
Let me add one little story: for our insurance math package, which we deploy on many different platforms, we kept for a very long time two target platforms, although they were no more needed by customers, simply because we made the experience that there were sometimes logical errors in our

HLASM native UNIX support.

2012-01-02 Thread John McKown
This is, vaguely, triggered by the discussion on the Mixed Case Support thread. One thing, as I may have mentioned here, that I am doing is writing some z/OS UNIX programs in HLASM (due to no C compiler). I am doing UNIX-like methodology, in that I am keeping the source in a UNIX file (with a .s

Re: mixed case in assembler

2012-01-02 Thread John Gilmore
I like Edward Jaffe's proposal for a SYMCASE(any|asis) functionally very much, except that the keyword value 'asis' seems to me to have unfortunate connotations in this context; and I should prefer to see SYMCASE(any|match) implemented instead, without changing EJ's functional specifications. My

Re: HL:ASM native UNIX support

2012-01-02 Thread John Gilmore
John McKown wrote: | One thing which is a bit frustrating is that my macros, | even if in a UNIX file, must be kept in UPPER case. Only the NAMES of your macros need be. The text of macro definitions can be mixed-case. Under the covers z/OS UNIX libraries are PDSEs, and PDSE member names are

Re: HL:ASM native UNIX support

2012-01-02 Thread John McKown
On Mon, 2012-01-02 at 19:08 -0500, John Gilmore wrote: John McKown wrote: | One thing which is a bit frustrating is that my macros, | even if in a UNIX file, must be kept in UPPER case. Only the NAMES of your macros need be. The text of macro definitions can be mixed-case. Yes, I meant

Re: HL:ASM native UNIX support

2012-01-02 Thread Paul Gilmartin
On Jan 2, 2012, at 17:08, John Gilmore wrote: Under the covers z/OS UNIX libraries are PDSEs, and PDSE member names are limited to eight characters---majuscules, numerics and @|#|$---the first of which cannot be numeric. No. -- gil