I have the above compiler installed from the zip files (OS/2 host, all targets), but I've been unable to obtain a copy of the retail Watcom
11.x compiler. I assume this will limit me to compiling for 16-bit
DOS until the Open Watcom project concocts their own SDKs, etc., for Windows, OS/2, and extended DOS, correct?
2. I have three programs (all quite similar to one another) that send output to the printer (stdprn).
All three programs compile flawlessly under Turbo-C 2.0, [...]
You then need to create a target (a
.tgt file) within that project; select Target|New Target from the
menu bar if the New Project dialogue does not take you through
target creation (it should).
Nope--that's where I get the "No targets are installed" error. All
menu options are greyed out except "Create a Project". In fact, only
the three leftmost buttons are on the toolbar. The rest shown in the tutorial are simply not there.
Turbo C is a very non-standard implementation of C. It is so old as
to be useless in a modern context.
Well, I tried to make my code as portable and ANSI-standard as I could
(I think it was you who wrote the portability guidelines that used to float around the FidoNet C echoes).
And until now, Turbo C was all I had available.
For example, "stdprn" is *not* a standard I/O stream and never has
been. The only standard streams are stdin, stdout and stderr. I
suggest you use stdout for printing and redirect it to a printer
using the command line redirection symbol (>). Then use stderr to
report errors to the console.
You lost me here. Are you saying that the *user* will need to
redirect? I'm not comfortable with that--the users of my programs
will often be nearly computer-illiterate.
I'm not about to even mention command lines to them.
Also, I'm using a lot of Epson printer
codes to do what needs to be done--how will a redirect from stdout
affect that?
Newer cuts of OS/2 have the DTK on the install media. Its
location varies with version, but will usually be located under a
directory named TOOLKIT.
I'm not finding it on my Warp 4 CDs. Can you give me some
filenames?
Once you introduce a C++ application framework you end up writing
a truckload of little subroutines and a little bit of glue code
to join them to the AF's common code. It looks butt-ugly, but it
is easy.
I'm already used to programming in a fairly modular fashion. Is
this what you mean
The three AFs that support OS/2 and Windows are all free for the
download. I suggest you try wxWindows, as it supports LINUX and
*BSD, as well as OS/2 and Windows.
Where do I download it?
Ahhh. . . I installed the OS/2 host stuff, not the Win16 host
stuff. Do I need the hosting files for all platform hosts?
I don't think so. The Win16 files account for most of the IDE's configuration, including most of the OS/2 and Win32 IDEs'
configurations. I think Watcom perceived Win16 as the lowest common denominator, and put the bulk of the common configuration data there.
So, you should have a fairly substantial BINP directory, a smallish
BINW directory and little or no BINNT directory.
The only IBM-burnt CDs I have to hand are for MCP2. The installation program on those is x:\TOOLKIT\TKINSTAL.EXE, where "x" is your CD-ROM drive.
It is getting there. Object methods are even more fragmented than conventional (i.e. FORTRAN-style) modular programming.
Start at http://www.wxwindows.org/ and choose whichever
implementations you need: OS/2, Win32, X11 (LINUX and *BSD), MacOS, whatever.
The way to write to a parallel device as a C stream that will work on
both DOS and OS/2 is to open it with fopen(), write to it whatever is desired, and then close it with fclose().
Well, none of the ide*.cfg files are in the Win16 IDE zip files. That seems to be the key that I'm missing.
So, you should have a fairly substantial BINP directory, a smallish
BINW directory and little or no BINNT directory.
I have exactly two files in the BINW directory: wcl.exe and
wcl386.exe. Those are the only ones that came on the zip files for
OS/2 host and all targets that are designated for that directory.
Well, my Warp CDs just got buried the other day by a mountain of
boxes.
It is getting there. Object methods are even more fragmented than
conventional (i.e. FORTRAN-style) modular programming.
Perhaps I'll have a better understanding once I get to the C++
tutorial.
Start at http://www.wxwindows.org/ and choose whichever
implementations you need: OS/2, Win32, X11 (LINUX and *BSD), MacOS,
whatever.
The only OS/2 downloads I found are via CSV, which I'm still trying to make sense of.
I wish I could just ftp what I need and be done with it.
Ok. I'll zip up the configuration files from my BINW directory and
e-mail them to you.
Well, George said he couldn't find it, so you perhaps need WSeB or
later. [George, did you check the BonusPak CD too?]
It is quite simple: in FORTRAN and all "procedural" languages,
subroutines and functions are either wholly public or wholly private.
In OO languages, a method is owned by a class of data, so for most
method calls you need an instance of that class in order to call the method.
Ah. I have am IBM-written PDF document somewhere that is a tutorial on CSV. I shall include it in the e-mail with the Watcom configuration
files. Do you have Acrobat or GSView? If neither I suggest you find a
copy of Acrobat/2, as most of IBM's newer doco is distributed in PDF format.
I have been considering building a Watcom-hosted implementation of
wxOS2 and uploading it to Hobbes, perhaps sending it down the OS/2 filebone as well. Since both you and Mike Luther have expressed
interest (and I expect there are some interested lurkers, too) this
could be something useful for me to do in the next few weeks. Watch
this space.
Ahhh. . . I installed the OS/2 host stuff, not the Win16 host
stuff. Do I need the hosting files for all platform hosts?
I don't think so. The Win16 files account for most of the IDE's configuration, including most of the OS/2 and Win32 IDEs' configurations. I think Watcom perceived Win16 as the lowest common denominator, and put the bulk of the common configuration data there.
Well, none of the ide*.cfg files are in the Win16 IDE zip files.
That seems to be the key that I'm missing.
So, you should have a fairly substantial BINP directory, a smallish BINW directory and little or no BINNT directory.
I have exactly two files in the BINW directory: wcl.exe
and wcl386.exe. Those are the only ones that came on the
zip files for OS/2 host and all targets that are designated
for that directory.
The only IBM-burnt CDs I have to hand are for MCP2. The installation program on those is x:\TOOLKIT\TKINSTAL.EXE, where "x" is your CD-ROM drive.
Well, my Warp CDs just got buried the other day by a
mountain of boxes. (The movers delivered our furniture and
other household goods from storage on Tuesday, and my
apartment looks like a warehouse.) I'll have to look again
at the CDs once I unbury them. (I can see them--I just
can't get to them.)
It is getting there. Object methods are even more fragmented than conventional (i.e. FORTRAN-style) modular programming.
Perhaps I'll have a better understanding once I get to the C++
tutorial.
Start at http://www.wxwindows.org/ and choose whichever implementations you need: OS/2, Win32, X11 (LINUX and *BSD), MacOS, whatever.
The only OS/2 downloads I found are via CSV, which I'm still
trying to make sense of. (I did download an OS/2 CSV client or
whatever the term is.) I emailed David Webster, who indicated that
the whole shooting match (all platforms, perhaps? can I even
select only OS/2?) runs about 100Mb. There's no way on God's green
earth I can download 100Mb of stuff, especially without some sort
of resume feature. I have a 56Kbps modem and my ISP limits me to
four hours per session. There is an available CD-ROM, but from the
description it appears that the OS/2 implementation of wxWindows is
NOT on the CD-ROM. I wish I could just ftp what I need and be done
with it.
The way to write to a parallel device as a C stream that will work on
both DOS and OS/2 is to open it with fopen(), write to it whatever
is desired, and then close it with fclose().
So I treat the device like another file?
The only OS/2 downloads I found are via CSV, [...]
Well, George said he couldn't find it, so you perhaps need WSeB or
later. [George, did you check the BonusPak CD too?
Sysop: | digital man |
---|---|
Location: | Riverside County, California |
Users: | 1,029 |
Nodes: | 17 (2 / 15) |
Uptime: | 183:54:53 |
Calls: | 503,708 |
Calls today: | 11 |
Files: | 158,907 |
D/L today: |
17,247 files (4,918M bytes) |
Messages: | 444,403 |
Posted today: | 3 |