>> Use the bug database to report bugs. Bugs reported on the mailing list
>> will be forgotten.
>
> I know, but www.freepascal.org & cvs.freepascal.org are down (?) altrow
> pings
> show they are active...
>
The bug database worked for me 1 hour ago.
___
Use the bug database to report bugs. Bugs reported on the mailing list
will be forgotten.
I know, but www.freepascal.org & cvs.freepascal.org are down (?) altrow pings
show they are active...
___
fpc-devel maillist - fpc-devel@lists.freepascal.org
ht
> While we on theme. At least in FPC 1.9.8 there is bug in compiler: it
> can't
> internally convert "constant AnsiChar" to "constant WideChar".
Use the bug database to report bugs. Bugs reported on the mailing list
will be forgotten.
___
fpc-devel m
While we on theme. At least in FPC 1.9.8 there is bug in compiler: it can't
internally convert "constant AnsiChar" to "constant WideChar".
=
uses SysUtils;
const sConst = 'W';
procedure Do1(const w: PWideChar);
begin StrToInt(w); end;
begin
Do1(sConst); //Err
peter green wrote:
oops looks like i commented out the wrong line when changing the
widestringmanager system for improved flexibility.
the code should be:
Function fpc_ShortStr_To_WideStr (Const S2 : ShortString): WideString;
{$ifdef hascompilerproc} compilerproc; {$endif}
{
Converts a ShortString
oops looks like i commented out the wrong line when changing the
widestringmanager system for improved flexibility.
the code should be:
Function fpc_ShortStr_To_WideStr (Const S2 : ShortString): WideString;
{$ifdef hascompilerproc} compilerproc; {$endif}
{
Converts a ShortString to a WideString
On Mon, 21 Mar 2005, C Western wrote:
> Is the assignment to Size meant to be commented out? (I have just
> started having trouble with a program which I think has just started
> using widestrings because the DOM unit has been switched to widestrings.)
The DOM unit has always been using widestr
Is the assignment to Size meant to be commented out? (I have just
started having trouble with a program which I think has just started
using widestrings because the DOM unit has been switched to widestrings.)
Colin
Function fpc_ShortStr_To_WideStr (Const S2 : ShortString): WideString;
{$ifdef h
>> > Yes! Exactly my point. But now the useful hints are sunk into tons of
>> > completely useless ones.
>>
>> Make your own error.msg file and change the hints you don't want to see
>> into notes or comments.
>
> Are you suggesting this as "quick hack" or do you find useful those hints?
> Are you
> > Yes! Exactly my point. But now the useful hints are sunk into tons of
> > completely useless ones.
>
> Make your own error.msg file and change the hints you don't want to see
> into notes or comments.
Are you suggesting this as "quick hack" or do you find useful those hints?
Are you theoricall
Uberto Barbini wrote:
>>But what do you mean with published methods? The published section is
>>intended only for properties, which should be published in the object
>>inspector. I guess you mean event methods. Beside event methods,
>>callback functions and virtual methods could be affected too.
>
> But what do you mean with published methods? The published section is
> intended only for properties, which should be published in the object
> inspector. I guess you mean event methods. Beside event methods,
> callback functions and virtual methods could be affected too.
Yes, it means anything
12 matches
Mail list logo
