Content deleted Content added
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.: The issue is differences with lower-level OS APIs and the absence of a required-by-the-language higher-level OS-independent API. |
→Even something as simple as writing a "sequential file" is coded differently e.g. in z/OS than in z/VSE.: not the same syntax; structured programming macros |
||
Line 223:
::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)
:::In the case of z/OS and z/VSE, even macros with the same name do not have the same syntax.
:::The HLA Toolkit does include an OS-independent macro library, containing macros for control structures, e.g., CASE, IF. -- [[User:Chatul|Shmuel (Seymour J.) Metz Username:Chatul]] ([[User talk:Chatul|talk]]) 21:24, 13 July 2023 (UTC)
| |||