Internal representation is one thing,
but what happen when you need to interact with OS API and CRT?
You need to cast our internal types into those used by the API or run-time?
(like the whole WIN API types change when use work in UNICODE)
Chen.___
Har
Revision: 10207
http://harbour-project.svn.sourceforge.net/harbour-project/?rev=10207&view=rev
Author: vszakats
Date: 2009-02-08 21:36:57 + (Sun, 08 Feb 2009)
Log Message:
---
2009-02-08 22:19 UTC+0100 Viktor Szakats (harbour.01 syenar hu)
* include/hbapifs.h
* sou
Revision: 10206
http://harbour-project.svn.sourceforge.net/harbour-project/?rev=10206&view=rev
Author: vszakats
Date: 2009-02-08 19:57:07 + (Sun, 08 Feb 2009)
Log Message:
---
2009-02-08 20:56 UTC+0100 Viktor Szakats (harbour.01 syenar hu)
* doc/whatsnew.txt
+ St
Revision: 10205
http://harbour-project.svn.sourceforge.net/harbour-project/?rev=10205&view=rev
Author: vszakats
Date: 2009-02-08 17:07:38 + (Sun, 08 Feb 2009)
Log Message:
---
2009-02-08 18:06 UTC+0100 Viktor Szakats (harbour.01 syenar hu)
* source/rtl/gtwvt/gtwvt.c
Hi Przemek,
Now I think I understand your concept, plus that your
main concern (for now) is that BYTE's signedness isn't
currently well defined. Of course I didn't want to change
anything that could break compatibility.
Here's my draft planned steps to switch to a properly typed
core; I've keyed t
On Sat, 07 Feb 2009, Szak�ts Viktor wrote:
Hi Viktor,
> > I suggest to change all 'BYTE *' used as file name in Harbour
> > FS API and similar functions to 'char *' type to not replicate
> > the problems which comes from Clipper, f.e. from CL53 header files:
> > typedef unsigned char BYTE;
> >
When I have installed OW 1.8 with option to Linux (experimantal),
can I to compile on Windows executables under Linux?
Regards,
Marek Horodyski
--
169 stacji TV! Naziemne i satelitarne!
Sprawdz program TV w kilka sekund >> htt
