22 Jun 2005 22:37:34 +0200, Alexandre Julliard <[EMAIL PROTECTED]>:
> Martin Fuchs <[EMAIL PROTECTED]> writes:
>
> > Let me change the question: Why should one use Unicode on those
> > systems at all? They don't support Unicode file systems - so there are
> > no 16 bit file names to display.
>
>
Martin Fuchs <[EMAIL PROTECTED]> writes:
> Let me change the question: Why should one use Unicode on those
> systems at all? They don't support Unicode file systems - so there are
> no 16 bit file names to display.
No, but using Unicode doesn't hurt, and is easier than going through
the effort of
22 Jun 2005 10:36:22 +0200, Alexandre Julliard <[EMAIL PROTECTED]>:
> Martin Fuchs <[EMAIL PROTECTED]> writes:
>
> > Sure, is not designed to be used "internally" in Wine. But
> > the point is,
> > I would like to maintain Winefile such, that it isn't constraint to
> > being used in Wine
> > only
> > So I really think Wine has to support the TCHAR type and all
> > associated functions/macros to stay as close to the Windows
> > API as possible.
>
> Wine obviously supports TCHAR, that doesn't mean you want to
> use it in new code. We have 16-bit support too but nobody
> advocates writing
22 Jun 2005 10:56:18 +0200, Alexandre Julliard <[EMAIL PROTECTED]>:
> "Ralf Reiterer" <[EMAIL PROTECTED]> writes:
>
> > So I really think Wine has to support the TCHAR type and all
> > associated functions/macros to stay as close to the Windows
> > API as possible.
>
> Wine obviously supports TCH
"Ralf Reiterer" <[EMAIL PROTECTED]> writes:
> So I really think Wine has to support the TCHAR type and all
> associated functions/macros to stay as close to the Windows
> API as possible.
Wine obviously supports TCHAR, that doesn't mean you want to use it in
new code. We have 16-bit support too
Martin Fuchs <[EMAIL PROTECTED]> writes:
> Sure, is not designed to be used "internally" in Wine. But
> the point is,
> I would like to maintain Winefile such, that it isn't constraint to
> being used in Wine
> only. For example it is currently also present in ReactOS. The idea is to
> allow
> c
> > The pure existence of in the Wine code base
> > shows me, Wine is aimed to support TCHARs. So why don't you
> > want to properly activate its functionality and take Winefile
> > as an example how to use it?
> > ...
> > I know, I won't be able to convince you. Any one out there to
> > support m
On 21.06.2005 23:44:21 Frank Richter wrote:
> On 21.06.2005 23:12, Martin Fuchs wrote:
> > The pure existence of in the Wine code base shows
> > me, Wine is aimed to support TCHARs.
> It may also just show that Wine wants to be compatible with existing sources
> that use , it doesn't necessarily
On 21.06.2005 23:12, Martin Fuchs wrote:
> The pure existence of in the Wine code base shows
> me, Wine is aimed to support TCHARs.
It may also just show that Wine wants to be compatible with existing sources
that use , it doesn't necessarily say anything about the internal use
of it or whether
Hi,
> The pure existence of in the Wine code base
> shows me, Wine is aimed to support TCHARs. So why don't you
> want to properly activate its functionality and take Winefile
> as an example how to use it?
> ...
> I know, I won't be able to convince you. Any one out there to
> support my poin
Hi,
> This stuff is getting uglier all the time. Please consider converting
> to Unicode properly and getting rid of all the TCHAR crap. I know the
> goal is to show how to use it, but at this point all it does is
> demonstrate why using TCHAR is a really bad idea. The way this is
> going pretty s
Martin Fuchs <[EMAIL PROTECTED]> writes:
> Why did I declare a new macro $(PREINCL) and insert it into Make.rule.in ?
> To allow inserting the include directory before .
But why do you need that?
> -IMPORTS = shell32 comdlg32 comctl32 ole32 mpr version user32 gdi32
> advapi32 kernel32
> +PRE
Changelog:
switch winefile to UNICODE mode
Why did I declare a new macro $(PREINCL) and insert it into Make.rule.in ?
To allow inserting the include directory before .
Another way would be to change the following line in Make.rule.in and move
$(EXTRAINCL) before -I$(TOPSRCDIR)/include:
INCLUD
Hi Marcelo,
2005/6/20, Marcelo Duarte <[EMAIL PROTECTED]>:
> I don´t understand something or winefile can use Michael Jung´s unixfs
> namespace extension?
The difference is: The unixfs namespace extension is implemented in
shell namespace. This is a quite huge overhead compared to directly
access
Martin Fuchs escreveu:
Changelog:
switch winefile to UNICODE mode
I don´t understand something or winefile can use Michael Jung´s unixfs
namespace extension?
+
+/* functions in unixcalls.c */
+
+extern void call_getcwd(char* buffer, size_t len);
+extern void* call_opendir(const char* path
16 matches
Mail list logo
