Bob Apthorpe
Bob Apthorpe
I don't know of a good Fortran unit testing library; I usually use ftncheck which is part of Arjen Markus' FLIBS project. The existing tests run under ctest without error...
Fair enough. It was written assuming `ITEMS(OBJECT)` returned 0 for `OBJECT` = 0 and replicated the behavior of the later code that segfaults because of bad indexing; the behavior should...
A little more info: If you start a fresh game and enter `UNLO` (with no noun), you come out of `INPUT()` with the following state: * `ACTION(1)` = 30 "UNLO"...
If we were really bored, we could look up the behavior of the OS/360 Fortran H Extended compiler (`bitsavers.org` is a godsend) though honestly, who knows what options they might...
The workaround is to open a command window and run `cquest` from the command line. Try ~~~sh [Windows key] run cmd ~~~ and that should get you to a command...
I know this is rather late but would `include(GNUInstallDirs)` be of any help here? https://cmake.org/cmake/help/latest/module/GNUInstallDirs.html has details on usage. I've had reasonable success using it when packaging under Linux, Windows,...
Perhaps I should be using `corrosion_install` instead; digging through the source code I distilled out the following: ``` corrosion_install(TARGETS ostrabak DESTINATION ${CMAKE_CURRENT_BINARY_DIR}/_install CONFIGURATIONS Debug) ``` but this does nothing, not...
Issue #65 seems related. Also, it doesn't appear that `-DCMAKE_BUILD_TYPE=Release` passes the build type on to `cargo`/`rustc`, defaulting to `debug` build no matter what type of build is actually specified....
A problem with Hollerith fields is that regular expressions can't match them in one pass. They take the form of `([1-9][0-9]*)H(.{\1})` with the wrinkle that `.{\1}` isn't legal regex syntax....
I have a working solution and there'd be no problem toggling it on or off with `allow_hollerith`. I'll send more info once I have the repo cloned but basically I...