Content deleted Content added
Guy Harris (talk | contribs) →Requested move 3 September 2023: One of what? People using "BAL" as a generic term for S/3x0+z/Architecture assembly language, or people using "Basic Assembler Language" in that fashion? |
Guy Harris (talk | contribs) →Even something as simple as writing a "sequential file" is coded differently e.g. in z/OS than in z/VSE.: Fix several typos in a comment of mine. |
||
Line 230:
::::The references to [[z/OS]] and [[z/VSE]] are just examples of the fact that HLASM allows user-provided libraries and does not dictate the contents of those libraries. -- [[User:Chatul|Shmuel (Seymour J.) Metz Username:Chatul]] ([[User talk:Chatul|talk]]) 11:23, 13 July 2023 (UTC)
:Essentially the same is true for anything that allows user-defined libraries: the semantics, and sometimes the syntax, depend on the libraries that the user provides. There is nothing special about, e.g., ''SYS1.MACLIB'', from the perspective of HLASM. -- [[User:Chatul|Shmuel (Seymour J.) Metz Username:Chatul]] ([[User talk:Chatul|talk]]) 11:23, 13 July 2023 (UTC)
::"True" in the sense that "there may be two or more libraries, for a given language, where the libraries provide ways of doing some particular thing, but the way you do it with one of those libraries isn't the way you do it with another", but if smething allows user-defined libraries, user-defined libraries could be provided for several different OSes that supprt sequential file access with the same API on all of those different OSes, so you *could*, for example, provide the ability to sequentially write a file with the same code on z/OS and z/VSE, by linking the code, on z/OS, with the z/OS version of the library (which would implement its APIs atop QSAM APIs) and linking the code, on z/
::But if you want to use the OS's "native" sequential I/O APIs, you'd have to write different code for different OSes, as the APIs in question aren't the same.
::This is similar to, for example, "if you want to write code to write a text file sequentially, using the same C code on multiple OSes, you can use the standard C I/O routines, which would be implemented differently atop OSes that have different APIs for that, but if you want to use the native APIs, you might be able to do that with common code atop Linux/Solaris/macOS/FreeBSD/HP-UX/NetBSD/AIX/V7 UNIX/..., as they're all UN*Xes with the same core APIs for that, but you'd have to change the code a bit on Windows and a lot on VMS or other OSes for which there are C compilers". The difference here is that, as far as I know, HLASM doesn't provide any libraries with OS-independent sequential I/O APIs, whereas the library for a hosted C implementation must provide the standard C I/O routines. [[User:Guy Harris|Guy Harris]] ([[User talk:Guy Harris|talk]]) 21:03, 13 July 2023 (UTC)
| |||