Hi Micha,
on 2005-03-25T22:36:10+02:00 Micha wrote:
>> In the last weeks we have had four discussions about hints.
> You only mention 3 here ?
I count four. The first, the second, the third and the problem
discussed in this thread.
>> The first problem was a bug and is solved.
> So ?
I
Peter J. Haas wrote:
> Hi Peter,
>
> on 2005-03-25T19:37:02+02:00 Peter wrote:
>
>>>I know. But why I should explain it more detailed, if you anyway
>>>disapprove such suggestions. :-(
>
>
>>Most ppl want compatibility with Delphi. When we add a warning for
>>uninitialized var parameters then
On Fri, 25 Mar 2005 21:35:10 +0100
"Peter J. Haas" <[EMAIL PROTECTED]> wrote:
> > Most ppl want compatibility with Delphi. When we add a warning for
> > uninitialized var parameters then there will be a lot of bug reports
> > that Delphi doesn't warn in those cases and we will have to reject
> > t
Does anybody here on this list want the hints off by default? I don't.
Definetely, a possibility to switch hints on/off (with the latter as default)
would be great, but if it is not available.
It is also clear to me that, concerning hints, there is no such thing as
Delphi-compatibility. Why both
Hi Peter,
on 2005-03-25T19:37:02+02:00 Peter wrote:
>> I know. But why I should explain it more detailed, if you anyway
>> disapprove such suggestions. :-(
> Most ppl want compatibility with Delphi. When we add a warning for
> uninitialized var parameters then there will be a lot of bug reports
>
> Hi Peter,
>
> on 2005-03-24T23:23:30+02:00 Peter wrote:
>>> The problem, you describe above could be solved relative simple, even
>>> the solution is more complex. I don't know any details of the
>>> compiler, but I assume, that internally the compiler use a identical
>>> structure to manage the
Hi Peter,
on 2005-03-24T23:23:30+02:00 Peter wrote:
>> The problem, you describe above could be solved relative simple, even
>> the solution is more complex. I don't know any details of the
>> compiler, but I assume, that internally the compiler use a identical
>> structure to manage the parameter
> Hi Peter,
>
> on 2005-03-24T12:55:21+02:00 Peter wrote:
>
>>> I don't know, whether other compiler modes support const and out.
>>> If yes, the RTL/FCL/LCL functions should use it. This do mean e.g.
>
>> For compatibility we can't do this. Delphi also doesn't warn.
>
> This is not really a good a
On Thu, 24 Mar 2005, Peter J. Haas wrote:
> Hi Peter,
>
> on 2005-03-24T12:55:21+02:00 Peter wrote:
>
> >> I don't know, whether other compiler modes support const and out.
> >> If yes, the RTL/FCL/LCL functions should use it. This do mean e.g.
>
> > For compatibility we can't do this. Delphi al
Hi Peter,
on 2005-03-24T12:55:21+02:00 Peter wrote:
>> I don't know, whether other compiler modes support const and out.
>> If yes, the RTL/FCL/LCL functions should use it. This do mean e.g.
> For compatibility we can't do this. Delphi also doesn't warn.
This is not really a good argument. FPC
> I don't know, whether other compiler modes support const and out. If
> yes, the RTL/FCL/LCL functions should use it. This do mean e.g.
For compatibility we can't do this. Delphi also doesn't warn. And making
the warning dependent on the compiler mode will make things too complex.
Because it then
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 ?
>
Hi Peter,
on 2005-03-22T08:36:36+01:00 Peter wrote:
>> Hmmm... Just pure curiosity:
>> I am getting a warning "Variable does not seem to be initialized" on a
>> code
>> from FreePascal RTL guide:
...
>> BlockRead (Fin,buf,Sizeof(buf),NumRead); // <-- Warning here (buf)
> There are no warnin
On Tue, 22 Mar 2005 08:58:33 +0100, MichaÅ WoÅniak <[EMAIL PROTECTED]> wrote:
> As I said - pure curiosity. Besides, we all know the dream of a warning-free
> compilation. :)
If you just want to feel nice with your code, you can disable the
warnings at this piece of code, and re-enable it after, b
Dnia wtorek, 22 marca 2005 04:11, Kornel Kisielewicz napisał:
> Note that it is written "does not SEEM". The code is OK IMHO.
As I said - pure curiosity. Besides, we all know the dream of a warning-free
compilation. :)
Thanks
Mike
___
fpc-pascal mai
> Hmmm... Just pure curiosity:
> I am getting a warning "Variable does not seem to be initialized" on a
> code
> from FreePascal RTL guide:
>
> Var Fin, fout : File;
> NumRead,NumWritten : Word;
> Buf : Array[1..2048] of byte;
> Total : Longint;
>
> begin
> Assign (Fin, Paramstr(1));
Micha³ Wo¼niak wrote:
> Hmmm... Just pure curiosity:
> I am getting a warning "Variable does not seem to be initialized" on
> a code from FreePascal RTL guide:
Note that it is written "does not SEEM". The code is OK IMHO. Warnings
aren't always right -- for example if we have a function with many
Hmmm... Just pure curiosity:
I am getting a warning "Variable does not seem to be initialized" on a code
from FreePascal RTL guide:
Var Fin, fout : File;
NumRead,NumWritten : Word;
Buf : Array[1..2048] of byte;
Total : Longint;
begin
Assign (Fin, Paramstr(1));
Assign (Fout,Params
19 matches
Mail list logo
