I will be out of the office starting 24-03-2005 and will not return until
06-04-2005.
I will respond to your message when I return.
--
DISCLAIMER:
This e-mail and any attachment(s) sent with it are intended exclusively f
[EMAIL PROTECTED] wrote:
I will be out of the office starting 24-03-2005 and will not return until
06-04-2005.
I will respond to your message when I return.
Can he be be removed from the list (or at least his account disables)?
Vincent.
___
fpc-pascal m
I will be out of the office starting 24-03-2005 and will not return until
06-04-2005.
I will respond to your message when I return.
--
DISCLAIMER:
This e-mail and any attachment(s) sent with it are intended exclusively f
I will be out of the office starting 24-03-2005 and will not return until
06-04-2005.
I will respond to your message when I return.
--
DISCLAIMER:
This e-mail and any attachment(s) sent with it are intended exclusively f
Quoting Michael Van Canneyt <[EMAIL PROTECTED]>:
>
>
> On Wed, 23 Mar 2005 [EMAIL PROTECTED] wrote:
>
> > Quoting Marco van de Voort <[EMAIL PROTECTED]>:
> >
> >>> On Tue, 22 Mar 2005, ml wrote:
> // than one interface
> a := (object as IA); // correct
> b := (object as IB); //
Hi Jeffrey,
on 2005-03-23T22:16:26+02:00 Jeffrey wrote:
> However, the example below gives me a similar warning
> with 1.9.8, but not 1.9.6:
I don't get such a warning with a version some days ago.
> program vdnstbi;
> var
> s:string;
> begin
> str(16, s); // Variable "s" does not seem to be
Hi Jonas,
on 2005-03-23T22:26:03+02:00 Jonas wrote:
> On 23 mrt 2005, at 22:16, Jeffrey Pohlmeyer wrote:
>> program vdnstbi;
>> var
>> s:string;
>> begin
>> str(16, s); // Variable "s" does not seem to be initialized
>> WriteLn(s);
>> end.
>>
>> Does "S" really need to be initialized ?
>
On 23 mrt 2005, at 22:16, Jeffrey Pohlmeyer wrote:
program vdnstbi;
var
s:string;
begin
str(16, s); // Variable "s" does not seem to be initialized
WriteLn(s);
end.
Does "S" really need to be initialized ?
No, that is an error in the compiler. I don't know whether it has
already been fixed i
> BlockRead (Fin,buf,Sizeof(buf),NumRead);
> Should the buf be initialized (and if so - how)
Maybe like this:
FillByte(buf, Sizeof(buf), 0);
I tried the blockread example with FPC
v1.0.10, v1.9.6, v1.9.4, and v1.9.8
and none of them gives a warning here.
However, the example below gives me
Hi,
I'm wondering why some Win32 API functions declared in
'redef.inc' are disabled, since the compatibility with
Delphi is compromised. For example:
//function CreateFontIndirect(const p1: TLogFont)..
Is there any reason for this?
Stefan
___
On Wed, 23 Mar 2005 [EMAIL PROTECTED] wrote:
Quoting Marco van de Voort <[EMAIL PROTECTED]>:
On Tue, 22 Mar 2005, ml wrote:
// than one interface
a := (object as IA); // correct
b := (object as IB); // returns pointer to the first interface
vmt=IA
c := (object as IC); // returns pointer to the
Quoting Marco van de Voort <[EMAIL PROTECTED]>:
> > On Tue, 22 Mar 2005, ml wrote:
> > > // than one interface
> > > a := (object as IA); // correct
> > > b := (object as IB); // returns pointer to the first interface
vmt=IA
> > > c := (object as IC); // returns pointer to the first interface
v
> On Tue, 22 Mar 2005, ml wrote:
> > // than one interface
> > a := (object as IA); // correct
> > b := (object as IB); // returns pointer to the first interface vmt=IA
> > c := (object as IC); // returns pointer to the first interface vmt=IA
> > // there's no way to do again it's like direct ca
On Tue, 22 Mar 2005, ml wrote:
Quoting Marco van de Voort <[EMAIL PROTECTED]>:
Like first, I wouldn't like to spam this mailing list about interfaces.
Can I contact you directly or somewhere else?
I would like to try to patch some things but I would probably have few
questions how to implement it
14 matches
Mail list logo