[Info-vax] C99 stuff (Re: The Road to V9.0)

[Bob Gezelter]

On Friday, June 7, 2019 at 7:37:47 AM UTC-4, clair... at vmssoftware.com wrote:
> This list is much different from that of First Boot which was more or less a strict progression: we did 1 then 2 then 3, etc. and each step depended on the previous step. Many of the V9.0 steps will happen in parallel and the order is not very important. Once we get to Real Boot and can run user programs, then the flood gates open. There will certainly be important events along the way which are not in the list and we'll have something to say about those, too. 
> 
> Real Boot
> 	load all images, not just those needed for First Boot
> 	load/run LOGIN_AUF rather than jumping into SYS$LOGINOUT
> 	load/run DIRECTORY rather than jumping into SYS$DIRECTORY
> 	switch from MD to real disk during startup
> 	execute DIR command
> 
> Crash Dump
> 	load dump kernel
> 	force a crash dump (;C from XDELTA)
> 	take real crash dump
> 	analyze with SDA
> 
> Conversational Boot
> 
> Start secondary CPUs
> 
> Create user accounts with AUTHORIZE.EXE
> 
> MOUNT / DISMOUNT disks
> 
> Run BATCH jobs
> 
> TCPIP - FTP
> 
> BACKUP / RESTORE
> 
> FORTRAN, PASCAL, COBOL, BASIC compilers
> 
> DEBUG an application
> 
> Run a threaded application
> 
> Installation from webserver

Clair,

WADR, while large components of the existing user base are comprised of FORTRAN, PASCAL, COBOL, and BASIC, I have found that even in installations which are based on "classic" languages, there are dependencies on C/C++. Often these dependencies are in the areas of supporting toolchains (e.g., ZIP/UNZIP, Apache, etc.). I note John's earlier posting on the question of native C++ using LLVM.

Admittedly without proof, I suspect that many ISVs and end-users will discover that the lack of native C/C++ is an impediment. Direction/guidance in this regard would likely be welcomed.

- Bob Gezelter, http://www.rlgsc.com