Zitat von Marco van de Voort <[EMAIL PROTECTED]>:
> In our previous episode, Mattias Gärtner said:
> > > > Any progress?
> > >
> > > IIRC, we once had the idea to feed the compiler an error message file
> > > with only error numbers as error "messages" so parsing would be easier.
> >
> > The error
Zitat von Marc Weustink <[EMAIL PROTECTED]>:
> Mattias Gaertner wrote:
> > On Wed, 13 Aug 2008 23:12:25 +0200 (CEST)
> > Daniël Mantione <[EMAIL PROTECTED]> wrote:
> >
> >> [...]
> The text mode IDE can display statisics while compiling. Why can't
> Lazarus?
>
> There is the c
Mattias Gaertner wrote:
On Wed, 13 Aug 2008 23:12:25 +0200 (CEST)
Daniël Mantione <[EMAIL PROTECTED]> wrote:
[...]
The text mode IDE can display statisics while compiling. Why can't
Lazarus?
There is the compiler unit, which *is* available, and this is the
only officially supported compiler i
Martin Schreiber schrieb:
On Thursday 14 August 2008 19.04:27 Florian Klaempfl wrote:
Martin Schreiber schrieb:
On Thursday 14 August 2008 11.29:40 Florian Klaempfl wrote:
Martin Schreiber schrieb:
There are no pseudo terminals on win32, I must use pipes. The current
2.0.3 RTL does not flush
On Thursday 14 August 2008 19.04:27 Florian Klaempfl wrote:
> Martin Schreiber schrieb:
> > On Thursday 14 August 2008 11.29:40 Florian Klaempfl wrote:
> >> Martin Schreiber schrieb:
> >>> There are no pseudo terminals on win32, I must use pipes. The current
> >>> 2.0.3 RTL does not flush output on
Marco van de Voort schrieb:
In our previous episode, Martin Schreiber said:
Indeed, people complained about the speed when redirecting output to a
file.
So the answer is:
"It is not possible to get flushed writeln and compiler messages on win32
pipes with FPC"?
Maybe, (with a custom textio d
Martin Schreiber schrieb:
On Thursday 14 August 2008 11.29:40 Florian Klaempfl wrote:
Martin Schreiber schrieb:
There are no pseudo terminals on win32, I must use pipes. The current
2.0.3 RTL does not flush output on writeln if the filehandle is a pipe
(2.0.2 does!). So the IDE target console w
In our previous episode, Martin Schreiber said:
> > Indeed, people complained about the speed when redirecting output to a
> > file.
>
> So the answer is:
> "It is not possible to get flushed writeln and compiler messages on win32
> pipes with FPC"?
Maybe, (with a custom textio driver, so that
On Thursday 14 August 2008 11.29:40 Florian Klaempfl wrote:
> Martin Schreiber schrieb:
> > There are no pseudo terminals on win32, I must use pipes. The current
> > 2.0.3 RTL does not flush output on writeln if the filehandle is a pipe
> > (2.0.2 does!). So the IDE target console window is unusabl
Martin Schreiber schrieb:
There are no pseudo terminals on win32, I must use pipes. The current 2.0.3
RTL does not flush output on writeln if the filehandle is a pipe (2.0.2
does!). So the IDE target console window is unusable on win32 with FPC 2.0.3
RTL and works OK with FPC 2.0.2 RTL.
"
;-)
On Wednesday 13 August 2008 23.12:25 Daniël Mantione wrote:
> >
> > Can you give a link?
>
> http://lists.freepascal.org/lists/fpc-devel/2006-May/007788.html
>
Hmm, the question remains:
"
Since some time FPC doesn't flush output on pipes after writeln.
On linux I can use a pseudo terminal, what c
On Wed, 13 Aug 2008 23:12:25 +0200 (CEST)
Daniël Mantione <[EMAIL PROTECTED]> wrote:
>[...]
> >> The text mode IDE can display statisics while compiling. Why can't
> >> Lazarus?
> >>
> >> There is the compiler unit, which *is* available, and this is the
> >> only officially supported compiler inte
Op Wed, 13 Aug 2008, schreef Vincent Snijders:
Because it is a unit:
* A crashing compiler would mean a crashing IDE.
* A compiler with memory leak would mean a IDE with memory leak.
Your point is correct, but the textmode IDE does survive compiler crashes
and you can continue development (
Op Wed, 13 Aug 2008, schreef Mattias Gaertner:
On Wed, 13 Aug 2008 21:29:59 +0200 (CEST)
Daniël Mantione <[EMAIL PROTECTED]> wrote:
Op Wed, 13 Aug 2008, schreef Vincent Snijders:
Daniël Mantione schreef:
Op Wed, 13 Aug 2008, schreef Vincent Snijders:
It easier to change the message pa
Daniël Mantione schreef:
Op Wed, 13 Aug 2008, schreef Vincent Snijders:
Daniël Mantione schreef:
Op Wed, 13 Aug 2008, schreef Vincent Snijders:
It easier to change the message parser if you change it, than to
design a protocol for more computer friendly messages.
It's not about what is l
Daniël Mantione schreef:
Op Wed, 13 Aug 2008, schreef Vincent Snijders:
Daniël Mantione schreef:
Op Wed, 13 Aug 2008, schreef Vincent Snijders:
It easier to change the message parser if you change it, than to
design a protocol for more computer friendly messages.
It's not about what is l
On Wed, 13 Aug 2008 21:29:59 +0200 (CEST)
Daniël Mantione <[EMAIL PROTECTED]> wrote:
>
>
> Op Wed, 13 Aug 2008, schreef Vincent Snijders:
>
> > Daniël Mantione schreef:
> >> Op Wed, 13 Aug 2008, schreef Vincent Snijders:
> >>
> >>> It easier to change the message parser if you change it, than
Op Wed, 13 Aug 2008, schreef Vincent Snijders:
Daniël Mantione schreef:
Op Wed, 13 Aug 2008, schreef Vincent Snijders:
It easier to change the message parser if you change it, than to design a
protocol for more computer friendly messages.
It's not about what is less work. It's about what
Daniël Mantione schreef:
Op Wed, 13 Aug 2008, schreef Vincent Snijders:
It easier to change the message parser if you change it, than to
design a protocol for more computer friendly messages.
It's not about what is less work. It's about what has the best
compatibility, the best maintainabi
Op Wed, 13 Aug 2008, schreef Vincent Snijders:
It easier to change the message parser if you change it, than to design a
protocol for more computer friendly messages.
It's not about what is less work. It's about what has the
best compatibility, the best maintainability, the best reliability
Daniël Mantione schreef:
Op Wed, 13 Aug 2008, schreef Mattias Gärtner:
FYI: Because there are several tools to parse FPC/Make/whatever output
it is planned to tell fpc to always give english output and show the
translated text in the messages window.
Ok, for once and for all, and please re
Op Wed, 13 Aug 2008, schreef Mattias Gärtner:
FYI: Because there are several tools to parse FPC/Make/whatever output
it is planned to tell fpc to always give english output and show the
translated text in the messages window.
Ok, for once and for all, and please read up the following words
Zitat von ik <[EMAIL PROTECTED]>:
> On Wed, Aug 13, 2008 at 6:58 PM, Micha Nelissen <[EMAIL PROTECTED]> wrote:
> > Bernd Mueller wrote:
> >>
> >> I think, the proper way could be, that fpc makes this message fatal, if
> >> the unit source is not present.
> >
> > The proper way is probably for Laza
On Wed, Aug 13, 2008 at 6:58 PM, Micha Nelissen <[EMAIL PROTECTED]> wrote:
> Bernd Mueller wrote:
>>
>> I think, the proper way could be, that fpc makes this message fatal, if
>> the unit source is not present.
>
> The proper way is probably for Lazarus to parse also other messages in case
> of Fat
Bernd Mueller wrote:
I think, the proper way could be, that fpc makes this message fatal, if
the unit source is not present.
The proper way is probably for Lazarus to parse also other messages in
case of Fatal, to give more context :-).
Micha
___
f
Bernd Mueller wrote:
Florian Klaempfl wrote:
Bernd Mueller schrieb:
Hello,
The compiler message "PPU Invalid Version n" should be made a fatal
error. This would help Lazarus to display the real problem (wrong ppu
version), instead of displaying the error Massage "Fatal: Can't find
unit x",
Florian Klaempfl wrote:
Bernd Mueller schrieb:
Hello,
The compiler message "PPU Invalid Version n" should be made a fatal
error. This would help Lazarus to display the real problem (wrong ppu
version), instead of displaying the error Massage "Fatal: Can't find
unit x", which is misleading in
Bernd Mueller schrieb:
Hello,
The compiler message "PPU Invalid Version n" should be made a fatal
error. This would help Lazarus to display the real problem (wrong ppu
version), instead of displaying the error Massage "Fatal: Can't find
unit x", which is misleading in this case.
This has a
Hello,
The compiler message "PPU Invalid Version n" should be made a fatal
error. This would help Lazarus to display the real problem (wrong ppu
version), instead of displaying the error Massage "Fatal: Can't find
unit x", which is misleading in this case.
Regards, Bernd.
Index: compiler/ms
29 matches
Mail list logo
