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.: same code base; OT: z/TPX |
||
Line 227:
::::{{tq|In the case of z/OS and z/VSE, even macros with the same name do not have the same syntax.}} Yes, that's one reason why, in assembly language, you can't write code using the {{code|GET}} and {{code|PUT}} sequential I/O APIs and have it build for and run on both OSes. The reasons are different for the C low-level file APIs - for example, the lowest-level sequential file I/O APIs are {{code|read()}} and {{code|write()}} on UN*Xes and {{code|ReadFile()}} and {{code|WriteFile()}} on Windows and, while the Visual Studio C library has file I/O APIs that are very similar to {{code|read()}} and {{code|write()}}, they are named {{code|_read()}} and {{code|_write()}} to avoid that very sort of name collision, and the lowest-level sequential file I/O APIs on VMS are whatever Record Management Services gives you - but the underlying problem is the same.
::::{{tq|The HLA Toolkit does include an OS-independent macro library, containing macros for control structures, e.g., CASE, IF.}} Are they "OS-independent" in the sense that they have different implementations on z/OS and z/VSE because of OS differences, or are they "OS-independent" in that there is no reason to have different implementations on different OSes and thus the implementations aren't different? If the HLA Toolkit were to offer macros and library routines to hide the differences between z/OS and z/VSE sequential I/O, ''that'' would be interesting, and might be the equivalent fo the C-defined file I/O APIs. [[User:Guy Harris|Guy Harris]] ([[User talk:Guy Harris|talk]]) 22:04, 13 July 2023 (UTC)
::::The structured programming macros in the HLA Toolkit do not use OS services; there is a single code base regardless of OS.
::::OT: z/TPX cannot host any compiler; you need a z/OS or Linux system to do builds. -- [[User:Chatul|Shmuel (Seymour J.) Metz Username:Chatul]] ([[User talk:Chatul|talk]]) 05:35, 14 July 2023 (UTC)
| |||