I believe that a const-cast might be used to support the kludge if necessary.
In Microsoft Visual C/C++ use:
const_cast<char *>argv[0] = cmdname;
I hope it helps.
W. Terry Lincoln \ \ _ /
Senior Engineer \ \ |J| /
Ultimate Technology Corporation \ _|E|_
a Tridex Company (NASDAQ:trdx) \ |_ S _|
mailto:WTerryLincoln@engineer.com \ |U|
http://www.AngelFire.com/ny/TerryLincoln \ / |S| \
http://www.geocities.com/Eureka/concourse/7326 \ | |
================================================ ~~~~~
Opinions expressed do not represent the management of UTC.
-----Original Message-----
From: Norbert Koch [mailto:n.koch@delta-ii.de]
Sent: Wednesday, May 12, 1999 4:14 PM
To: xemacs-nt
Cc: XEmacs Mailing List
Subject: [FAILURE] 21.2.13 on WinNT
----------------------------------------------------
Hi,
the current CVS sources can't be built on WinNT due to the followin
error:
..\src\ntproc.c(691) : error C2166: l-value specifies const object
The message is correct, because in function
/* When a new child process is created we need to register it
in our list,
so intercept spawn requests. */
int
sys_spawnve (int mode, CONST char *cmdname,
CONST char * CONST *argv, CONST char *CONST *envp)
{
We have the following assignment ...
/* make sure argv[0] and cmdname are both in DOS format */
unixtodos_filename ((char*)cmdname);
/* #### KLUDGE */
argv[0] = cmdname;
Do we absolutely need this kludge? In this case we can't use a const
pointer to const char in the arglist ...
Anybody?
'norbert.
[[ WARREN~1.VCF : 4406 in winmail.dat ]]