These were possibly useful options when asynch support was being
added long ago. Async simulator I/O is quite stable and should always
be leveraged whenever pthreads is available.
Card decks will never be excessively large (> uint32) since there never
was a computer room big enough to hold that many cards. :-)
Hopper counts and size are all of type t_addr since they are referenced
relative to uptr->pos which tracks the hopper position. That state is
managed so position is properly managed across a SAVE/RESTORE.
On some systems that use sim_card, t_addr is 64bits, hence
make vax the primary build target and microvax3900 the copied result.
The microvax3900 binary name was added when all the different VAX
simulator models were add to simh and each was appropriately named
based on the system model name of each respective simulator.
The vax simulator name was the earliest vax implemented so a binary
of that name is produced for upward compatibility for existing users.
Producing the vax simulator and then copying it to microvax3900
produces equivalent results, but is easier to auto convert to cmake
build configuration files which then will generate a vax project
file when cmake is generating those.
Programmatic interval timers are not proper candidates for calibrated
clocks since the interval values can change arbitrarily under program
control and then interfer with attempts at proper calibration.
If libpcreposix isn't available, we can't fall back to the local
regex.h since the default C runtime on Linux and OS/X implementations
of the regex functionality doesn't ever match regular expressions
with imbedded newlines.
There are no extended arguments while parsing SHOW CONSOLE commands.
SHOW CONSOLE is a special parsing case somewhat equivalent to of SHOW
DEVICE for a device display. No SHOW CONSOLE commands take value arguments.
Adopted from Dave Bryan's changes in V3.11
Similar to the build_ming.bat procedure which will invoke MinGW to
biuild siimulators, this procedure will rebuild all of SIMH simulators using
Visual Studio.
If this procedure is not invoked from a Developer Command Prompt
then the VS2008 tools are preferred if VS2008 is installed,
otherwise the installed Visual Studio tools will be used
prefering newer Visual Studio versions over older ones.
If this procedure is invoked from a Developer Command Prompt
then the tool chain provided with the command prompt is used
to build the simh projects.
A single argument to this procedure may be the word Debug, which
will cause Debug binaries to be build rather than the Release
binaries which is the default.
This procedure establishes a telnet listen port solely so that the console
output traffic can be buffered (and not emitted). Since nothing will ever
connect to this port we bound it to the localhost address so that firewall
prompts aren't generated when building in a new directory.
