I think that has to be safe for any compiler we've got.
-----Original Message-----
From: ethersoft(a)gmail.com [mailto:ethersoft@gmail.com] On Behalf Of Vin
Shelton
Sent: Thursday, December 07, 2006 12:05 PM
To: Benson Margulies
Cc: Stephen J. Turnbull; Ben Wing; XEmacs-Beta(a)xemacs.org
Subject: Re: qxe generation problem
On 12/7/06, Benson Margulies <bim2006(a)basistech.com> wrote:
Hmm. Why is it compiling that .c function with C++ const rules? We
can
try adding a cast. I'll look at this tonight.
I was just looking into this. Applying a cast:
--- xemacs-21.5-2006-12-07/src/fileio.c 2006-12-07 11:17:53.352323100
-0500
+++ xemacs-21.5-benson/src/fileio.c 2006-12-07 09:55:06.478972700
-0500
@@ -2325,7 +2325,7 @@
DACL_SECURITY_INFORMATION|GROUP_SECURITY_INFORMATION|OWNER_SECURITY_INFO
RMATION,
&psidOwner, &psidGroup, &pDacl, &pSacl, &pDesc);
if(error != ERROR_SUCCESS) { // FAT?
- attributes = qxeGetFileAttributes(filename);
+ attributes = qxeGetFileAttributes((Extbyte *)filename);
return (attributes & FILE_ATTRIBUTE_DIRECTORY) || (0 ==
(attributes
& FILE_ATTRIBUTE_READONLY));
}
is sufficient to produce a working native XEmacs-21.5 for the non-SDK
case.
I will continue to investigate....
- Vin
--
The Journey by Mary Oliver
http://www.poemhunter.com/p/m/poem.asp?poet=6771&poem=30506
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta