> Dirk Laurie [SMTP:[EMAIL PROTECTED]] wrote
>Van_Ryckeghem_Andr=E9?= wrote:
>>
>> and now a (newbe) question:
>> - how can i keep a pmx logfile on harddisk?
>In DOS and in Unix the command lines are:
> echo BASENAME | pmxa > pmxa_log
> pmxb > pmxb_log
Werner has been bugged me several times about creating a log file by
default, and the next release shall have one. When that will come is not
clear. I've lately been looking at iterative methods for optimizing
linebreaks. To ease the iteration (pmxa,pmxb,pmxa,pmxb,...) I've combined
(at long last) pmxa and pmxb into a single file. It runs and gives some
interesting results, but crashes on bigger problems when the Windows swap
space (i.e., virtual memory) gets filled up. The combined code seems to eat
up about a Mb on every iteration. Currently scratching my head about how to
stop this from happening. Any thoughts what could be causing it?
While I'm on the subject of future releases, if I do keep pmxa and pmxb
combined (as I would prefer), I will not be able to use the trusty old
compiler that's been making those nice compact binaries...the combined code
is just too big for the old compiler/linker to swallow. This leaves me only
with MS Powerstation, which creates binaries that will run in a DOS sindow,
but require Windows 95 or better to be present. Let me ask once again to
hear from people for whom this would create a problem. I.e., is anyone
running a DOS version of PMX on a machine that doesn't have Windows 95. I
cannot see any way around this problem at the moment and I fear that DOS
users with older systems may either have to upgrade their hardware or be
content with older versions of PMX. (Is this the ultimate price I'm paying
for programming in FORTRAN?).
--Don Simons
