This is by design.
- Original Message -
From: mariano podesta
To: fpc-devel@lists.freepascal.org
Sent: Saturday, January 21, 2006 1:56 AM
Subject: [fpc-devel] interface vs optimizer
hi people,
there is a problem with functions returning interfaces:
if nobody stores the result, the
Delphi 11 .Net 2.0 will support Generics. Maybe Delphi 11 Win32.
This page looks only like the start of a proposal. Neither complete nor
official.
Why do you think, that D2006 will have generics?
Not Delphi 2006, but Delphi 2007
___
fpc-devel
procedure TestBuf(const Buf; Size: Integer);
begin
end;
It should work. AFAIR, typed constants are treated exactly as variables with
an initial value.
Actually untyped parameters accept anything except numeral or untyped numeric
constant in Delphi. The meaning of const in this example is
Try www.jp.freepascal.org as a workaround (works nice here), or the
google cache.
But I still will not be able to fill / browse bug reports!
___
fpc-devel maillist - fpc-devel@lists.freepascal.org
http://lists.freepascal.org/mailman/listinfo/fpc-devel
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
Delphi dowsn't allow sets with ordinal values larger than 255 too:
That's incorrect.
.
Sets are restricted to a maximum of 256 members, but the ordinal values
of the members can be higher.
As I've already posted: sample code below not compile in any Delphi version. You
can try it yourself.
- Original Message -
From: DrDiettrich [EMAIL PROTECTED]
To: FPC developers' list fpc-devel@lists.freepascal.org
Sent: Tuesday, February 15, 2005 4:11 AM
Subject: Re: [fpc-devel] Bug in PWidechar and refcounting
Alexey Barkovoy wrote:
PAnsiChar, PChar are just pointers and not garbage
2) Sets with minimal size, at least with 1 and 2 bytes for replacement
of Byte and Word types.
This is already correctly working (at least in FPC 1.9.x). For example:
type
{$MINENUMSIZE 2}
enumDMUS_VARIATIONT_TYPES = (
DMUS_VARIATIONT_SEQUENTIAL {= 0}, (* Play sequential starting with
Normally I would aggree with you, but as far as I can see, PWideChar is
also an automated type. (If not then large parts of the variant-code in
the RTL has to be rewritten, and probably alsoe the wstrings.inc file)
From wstrings.inc:
WideString is defined as a 'silent' pwidechar :
a pwidechar
I where any chance to see FreePascal generating VMT's for classes that is
more compatible with C++ / TurboPascal / Delphi one?
To explain mine question: recently I've been porting Delphi framework
interfacing to C++ code to FPC and finded out that althrow Delphi VMT layout
is compatible to C++
Fixes description:
2005/01/10 21:50:05 jonas
+ support for passing records in registers under darwin
* tcgpara now also has an intsize field, which contains the size in
bytes of the whole parameter
I've initially filled bug report here:
- Original Message -
From: peter green [EMAIL PROTECTED]
To: FPC developers' list fpc-devel@lists.freepascal.org
Sent: Sunday, January 09, 2005 11:45 PM
Subject: RE: [fpc-devel] ansistrings and widestrings
Type
// Lenght paremeters are number of CHARS not bytes
Well functions are called ANSI to unicode and vice versa. ANSI is always single
byte; by unicode people usually refer to utf16, not multibyte encoding and both
Delphi and FPC define WideString as double byte strings. So semantically
functions do that is required. IMHO then assigning widestring
Firstly: I agree that Wide2AnsiMoveProc and Ansi2WideMoveProc should take size
of resulting string.
Next: I was wrong about ansistrings - on Windows their are (PCHAR's) used (until
WinNT arrived) in far east localized versions coupled with multibyte encoding.
So currenltly for legacy
14 matches
Mail list logo
