OT: MS include file barfs before even get to "real" code...

[dpb]

Compilation of code was given supposedly built under OW starts out as...

cd c:\matlabr11\toolbox\matlab\general
wmake -f c:\matlabr11\toolbox\matlab\general\ibrowse.mk -h -e
c:\matlabr11\toolbox\matlab\general\ibrowse.dll
wpp386 ibrowse.cpp -i="C:\WATCOM\h;C:\WATCOM\h\nt" -w4 -e25 -zq -od -d2
-bd -5r -bt=nt -mf
C:\WATCOM\H\NT\wtypes.h(379): Error! E006: (col 26) syntax error;
probable cause: missing ';'
C:\WATCOM\H\NT\wtypes.h(379): Note! N393: (col 26) included from
C:\WATCOM\H\NT\objbase.h(408)
C:\WATCOM\H\NT\wtypes.h(379): Note! N393: (col 26) included from
C:\WATCOM\H\NT\ole2.h(28)
C:\WATCOM\H\NT\wtypes.h(379): Note! N393: (col 26) included from
C:\WATCOM\H\NT\windows.h(165)
C:\WATCOM\H\NT\wtypes.h(379): Note! N393: (col 26) included from
ibrowse.cpp(23)
C:\WATCOM\H\NT\wtypes.h(1078): Error! E336: (col 23) declaration
specifiers are required to declare 'ULONGLONG'
C:\WATCOM\H\NT\wtypes.h(1078): Error! E006: (col 19) syntax error;
probable cause: missing ';'
C:\WATCOM\H\NT\wtypes.h(1079): Error! E121: (col 5) syntax error
C:\WATCOM\H\NT\wtypes.h(1080): Error! E121: (col 1) syntax error
...

extern "C"
{
#define bool BOOL
#include <windows.h>
#include "mex.h"
}

Line 23 in the source file is the line

#include <windows.h>

above, all else in the file ahead of that is comments or white space so
it seems the issue has to be in the header file itself. The area from
379 looks like

typedef unsigned __int64 ULONGLONG;
#if 0
typedef hyper LONGLONG;

typedef MIDL_uhyper ULONGLONG;

typedef LONGLONG __RPC_FAR *PLONGLONG;

typedef ULONGLONG __RPC_FAR *PULONGLONG;

typedef struct _LARGE_INTEGER
{
LONGLONG QuadPart;
} LARGE_INTEGER;

typedef LARGE_INTEGER __RPC_FAR *PLARGE_INTEGER;

typedef struct _ULARGE_INTEGER
{
ULONGLONG QuadPart;
} ULARGE_INTEGER;

#endif // 0


I was never much of a C wonk and now having been nearly 10 yr, what
little facility I had is rusty at best...

Anybody (like Lynn :) ) able to divine what the issue is here? The
wtypes.h file is straight from the distribution CD.

[Frank Beythien]

Am 03.01.2017 um 23:34 schrieb dpb:
> Compilation of code was given supposedly built under OW starts out as...
>
> cd c:\matlabr11\toolbox\matlab\general
> wmake -f c:\matlabr11\toolbox\matlab\general\ibrowse.mk -h -e
> c:\matlabr11\toolbox\matlab\general\ibrowse.dll
> wpp386 ibrowse.cpp -i="C:\WATCOM\h;C:\WATCOM\h\nt" -w4 -e25 -zq -od -d2
> -bd -5r -bt=nt -mf
> C:\WATCOM\H\NT\wtypes.h(379): Error! E006: (col 26) syntax error;

My wtypes.h looks very different.
The only place where I find the line

typedef unsigned __int64 ULONGLONG;

is in h/nt/winnt.h
What is your watcom version?

Regarding direct screenio. I use dosemu for executing old dosprograms.

CU
Frank

[dpb]

On 01/04/2017 4:18 AM, Frank Beythien wrote:
> Am 03.01.2017 um 23:34 schrieb dpb:
>> Compilation of code was given supposedly built under OW starts out as...
>>
>> cd c:\matlabr11\toolbox\matlab\general
>> wmake -f c:\matlabr11\toolbox\matlab\general\ibrowse.mk -h -e
>> c:\matlabr11\toolbox\matlab\general\ibrowse.dll
>> wpp386 ibrowse.cpp -i="C:\WATCOM\h;C:\WATCOM\h\nt" -w4 -e25 -zq -od -d2
>> -bd -5r -bt=nt -mf
>> C:\WATCOM\H\NT\wtypes.h(379): Error! E006: (col 26) syntax error;
>
> My wtypes.h looks very different.
> The only place where I find the line
>
> typedef unsigned __int64 ULONGLONG;
>
> is in h/nt/winnt.h
> What is your watcom version?

Since I didn't have the C/C++ compiler installed, I refreshed the
commercial install from the v10.6 Watcom distribution CD. The note I
saw on the distribution download looked to me like was essentially same
version so didn't think there'd be any real differences. I guess I need
to download and install a fresh OW from the git-go and see what then
happens. Thanks for checking; the h files are in the Fortran installed
directory tree and they do look much cleaner. I _could_ try changing
the INCLUDE library path I suppose... :)

> Regarding direct screenio. I use dosemu for executing old dosprograms.

Not familiar with it...guess dags will find a reference so will see if
can find it.

Thanks for the time/info...

--dpb

[Frank Beythien]

Am 04.01.2017 um 15:53 schrieb dpb:

> Since I didn't have the C/C++ compiler installed, I refreshed the
> commercial install from the v10.6 Watcom distribution CD. The note I

Oh, better try the 1.9 version. At least for C(++) there are several
changes.

> saw on the distribution download looked to me like was essentially same
> version so didn't think there'd be any real differences. I guess I need
> to download and install a fresh OW from the git-go and see what then

I don't trust the GIT fork from Jiri.

> happens. Thanks for checking; the h files are in the Fortran installed
> directory tree and they do look much cleaner. I _could_ try changing
> the INCLUDE library path I suppose... :)
>
>> Regarding direct screenio. I use dosemu for executing old dosprograms.
>
> Not familiar with it...guess dags will find a reference so will see if
> can find it.

http://dosemu.org/

CU
Frank

[dpb]

On 01/04/2017 10:17 AM, Frank Beythien wrote:
> Am 04.01.2017 um 15:53 schrieb dpb:
>
>> Since I didn't have the C/C++ compiler installed, I refreshed the
>> commercial install from the v10.6 Watcom distribution CD. The note I
>
> Oh, better try the 1.9 version. At least for C(++) there are several
> changes.

It's installing at the moment...

..

>> to download and install a fresh OW from the git-go and see what then
>
> I don't trust the GIT fork from Jiri.

That "git-go" is "from the beginning", not "GIT"

>> happens. Thanks for checking; the h files are in the Fortran installed
>> directory tree and they do look much cleaner. I _could_ try changing
>> the INCLUDE library path I suppose... :)

I did give that a go just to see...different issues arose, but the
specific error went away.

I still can't figure out what, specifically, it doesn't like about the
particular typedef statement; surely looks like legal syntax to me.

>>> Regarding direct screenio. I use dosemu for executing old dosprograms.
>>
>> Not familiar with it...guess dags will find a reference so will see if
>> can find it.
>
> http://dosemu.org/

Seems to be for Linux, tho, not under Windoes???

[dpb]

On 01/04/2017 10:17 AM, Frank Beythien wrote:

> Am 04.01.2017 um 15:53 schrieb dpb:
>
>> Since I didn't have the C/C++ compiler installed, I refreshed the
>> commercial install from the v10.6 Watcom distribution CD. The note I
>
> Oh, better try the 1.9 version. At least for C(++) there are several
> changes.

...

OK, guess shoulda' just done it first...it now does get thru the OS
include files; there's a problem in the code itself independent of that
so guess that's where the starting point will be.

I looked at the code some more while the install was going; I may just
trash the whole thing and rewrite the wanted functionality from scratch;
this is grossly over-complicated to accomplish the task...think I could
do it in about the tenth of the code in Fortran that I know much better
with just a couple of Win32 API calls needed.

Guess I'll spend a few to see if can fixup the issues here to at least
see if can get it to compile first...

Anyway, thanks again for the input; much appreciated. I'm surprised the
original Watcom distribution wouldn't even compile the header files
altho I'd never tried either a CPP compilation nor using the Windows
header files. The big app uses a few C routines in the F77 app but
they're standalone things for memory tricks not available in Fortran and
the like so didn't need any of the OS-dependent header files so never
ran into the issue before.

[Frank Beythien]

Am 04.01.2017 um 18:45 schrieb dpb:

>>>> Regarding direct screenio. I use dosemu for executing old dosprograms.
>>>
>>> Not familiar with it...guess dags will find a reference so will see if
>>> can find it.
>>
>> http://dosemu.org/
>
> Seems to be for Linux, tho, not under Windoes???

My bad, try qemu, it is available for winxx

http://wiki.qemu.org/Hosts/W32

CU
Frank