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 ob
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 m
How do MS compilers handle code written for both Ansi and Unicode
environments, and the related data types? How are string arguments (out)
handled in Windows API's?
Is this Microsoft way a good model for other platforms?
MS provides types for strngs/characters which are become differ if UNICODE
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 con
However, I just tried to ping from www.freepascal.org to the machine
mentioned here by someone (xzone.dyndns.org) and packets with size of
16000 went through without problems...
Not sure will this help but today I can access www.freepascal.org from the same
machine that has not been able to do thi
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
ISP and consequently DNS has changed. Check the IP address.
It should be 62.166.198.202
But you're the only one to report problems, which suggests the problem is
somewhere on your side. Maybe a proxy ?
Well I'm having problems with www.freepascal.org for around a month now (maybe
even more). Somet
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".
=
uses SysUtils;
const sConst = 'W';
procedure Do1(const w: PWideChar);
begin StrToInt(w); end;
begin
Do1(sConst); //Err
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.
ty
{$mode delphi}
type aenum=510..517;
aset = set of aenum;
begin
Writeln(sizeof(aset));
end.
xbla.pp(5,25) Error: illegal type declaration of set elements
xbla.pp(10,4) Fatal: There were 1 errors compiling module, stopping
Delphi dowsn't allow sets with ordinal values larger than 255 too:
Borlan
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
va
- Original Message -
From: "DrDiettrich" <[EMAIL PROTECTED]>
To: "FPC developers' list"
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 no
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 tha
Delphi and FreePascal simplest interfaces already includes IUnknown. So using
raw interfaces is incompatible here too.
No.
You could try to use CORBA interfaces, they don't have IInterface (or
IUnknown) as the parent.
There is a compiler switch for this.
Thanks, I'll look at it. Seems really bette
- Original Message -
From: "Florian Klaempfl" <[EMAIL PROTECTED]>
For example "DECLARE_INTERFACE_(IClassFactory, IUnknown)" in C++ is expanded
to "struct FAR IClassFactory : public IUnknown", so really public parts of
VMT (with positive offset) are always [should be] compatible. Surely
rts when people were forced to use similiar cripped
interfaces exposed by C++ programmers. So it's the real problem not just
artificial one.
Regards,
Alexey Barkovoy
___
fpc-devel maillist - fpc-devel@lists.freepascal.org
http://lists.freepascal.org/mailman/listinfo/fpc-devel
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++ o
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++ o
[80] == address of
DoSomething).
(1)
typedef class IMyClass
{
public:
__cdecl virtual void DoSomething()=0;
} *lpMyClass;
(2)
type
IMyClass = class(TObject)
public
procedure DoSomething; virtual; cdecl; abstract;
end;
Regards,
Alexey Barkovoy
I've found the problem. Some checks were missing, because it should have
given an Internal error instead of generating buggy code. Still looking
for a clean solution. In the meanwhile you can use your workaround as
described above.
Thanks, good to know that someone is looking over it
__
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:
http://www.freepascal.org/bugs/showrec.p
- Original Message -
From: "peter green" <[EMAIL PROTECTED]>
To: "FPC developers' list"
Sent: Sunday, January 09, 2005 11:45 PM
Subject: RE: [fpc-devel] ansistrings and widestrings
Type
// Lenght paremeters are number of CHARS not bytes
TWide2AnsiMove=function(source:pwidechar; srcle
- Original Message -
From: "Marco van de Voort" <[EMAIL PROTECTED]>
To: "FPC developers' list"
Sent: Sunday, January 09, 2005 2:53 PM
Subject: Re: [fpc-devel] ansistrings and widestrings
This is the level where multibyte characters can come in, so that just a
Character can be different
- Original Message -
From: "peter green" <[EMAIL PROTECTED]>
To: "FPC developers' list"
Sent: Friday, January 07, 2005 7:24 PM
Subject: RE: [fpc-devel] ansistrings and widestrings
it should be noted that pascal classes are really not suited to doing
strings.
to do strings with classes y
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 applicatio
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 t
if i do ansistringvar := widestringvar or widestringvar := ansistringvar
what does the compiler do?
1: use the systems default encoding (if so obtained from where?)
2: use utf-8
3: use iso-8859-1
4: use something else?
furthermore if the encoding used is one not capable of representing all
unicode
28 matches
Mail list logo
