Here in this forum and elsewhere the notion that since the binder's support for AMODE(SPLIT) had been "little used" it would not be necessary or desirable to provide an analogous binder facility for mixing AMODE(31) and AMODE(64) in the same executable was widely reported. (I use the word 'reported' advisedly. Here, for example, the view of someone else, never necessarily that of the poster, was always what was set out.)
This notion had two important, albeit non-technical, merits. Both sloth and parsimony recommended it. It was nevertheless a bad, even a very bad one. Among the traditional statement-level languages, i.e., Java excluded, only one IBM C implementation yet supports AMODE(64), and others are apparently going to be slow in coming. Binder support for something like AMODE(MIXED,31,64) is thus urgent. (Binder terminology has traditionally had a short-term bias; ANY, for example, had to mutate into ANY31 abd ANY64.) John Gilmore, Ashland, MA 01721 - USA ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
