On Sun, 14 May 2006 08:48:07 +0200 (CEST)
Daniël Mantione [EMAIL PROTECTED] wrote:
About flushing the output, I think it is impossible to receive the output
interactively currently, it will output in bursts. You should still be
able to receive the output, though. If you want to receive it
Daniël Mantione wrote:
Op Sun, 14 May 2006, schreef Martin Schreiber:
Since some time FPC doesn't flush output on pipes after writeln.
On linux I can use a pseudo terminal, what can I do on win32 to get flushed
output from FPC into the message window of MSEide?
About flushing the
On Sunday 14 May 2006 08.48, Daniël Mantione wrote:
Op Sun, 14 May 2006, schreef Martin Schreiber:
Since some time FPC doesn't flush output on pipes after writeln.
On linux I can use a pseudo terminal, what can I do on win32 to get
flushed output from FPC into the message window of MSEide?
Just posting some more information: here is the verbose output when using the
-va option:
Searching file c:\pascal\FPC-2.0.2-CrossLinux\bin\i386-win32\ld.exe... found
Using util c:\pascal\FPC-2.0.2-CrossLinux\bin\i386-win32\ld.exe
hello.pas(16,1) Error: Can't call the linker, switching to
On Sun, 14 May 2006, Martin Schreiber wrote:
On Sunday 14 May 2006 08.48, Daniël Mantione wrote:
Op Sun, 14 May 2006, schreef Martin Schreiber:
Since some time FPC doesn't flush output on pipes after writeln.
On linux I can use a pseudo terminal, what can I do on win32 to get
On Sun, 14 May 2006, Daniël Mantione wrote:
Op Sun, 14 May 2006, schreef Martin Schreiber:
Since some time FPC doesn't flush output on pipes after writeln.
On linux I can use a pseudo terminal, what can I do on win32 to get flushed
output from FPC into the message window of
On Sun, 14 May 2006 12:03:34 +0200 (CEST)
Michael Van Canneyt [EMAIL PROTECTED] wrote:
On Sun, 14 May 2006, Daniël Mantione wrote:
Op Sun, 14 May 2006, schreef Michael Van Canneyt:
On Sun, 14 May 2006, Daniël Mantione wrote:
Op Sun, 14 May 2006,
On Sun, 14 May 2006 11:46:33 +0200
Florian Klaempfl [EMAIL PROTECTED] wrote:
Michael Van Canneyt wrote:
On Sun, 14 May 2006, Daniël Mantione wrote:
Op Sun, 14 May 2006, schreef Michael Van Canneyt:
On Sun, 14 May 2006, Daniël Mantione wrote:
Op Sun, 14 May 2006, schreef
We could do this ourselves by assigning a unique number to each error.
(and keeping these numbers)
All messages already have an unique number. It is only not used in the output.
Peter
___
fpc-devel maillist - fpc-devel@lists.freepascal.org
Op Sun, 14 May 2006, schreef Florian Klaempfl:
Parsing the current error messages isn't that hard?
Perhaps it is even easier than the format I proposed, but it is bad
software design and asking for breakage.
Daniël___
fpc-devel maillist -
On Sun, 14 May 2006, Peter Vreman wrote:
We could do this ourselves by assigning a unique number to each error.
(and keeping these numbers)
All messages already have an unique number. It is only not used in the output.
So, in principle they don't change ?
I seem to remember
Martin Schreiber wrote:
On Sunday 14 May 2006 16.54, Florian Klaempfl wrote:
The error numbers didn't change, they are keep unique.
I propose to do the following:
- add an option -vm (machine readable output)
Using this option the compiler outputs the messages csv like and flushes
after
On Sun, 14 May 2006, Mattias Gaertner wrote:
On Sun, 14 May 2006 12:10:14 +0200 (CEST)
Michael Van Canneyt [EMAIL PROTECTED] wrote:
[...]
I'm all for such a message form; it should be easy to add with some -v
switch... But
- This is no use if the message code changes over
On Sun, 14 May 2006, Florian Klaempfl wrote:
The error numbers didn't change, they are keep unique.
I propose to do the following:
- add an option -vm (machine readable output)
Using this option the compiler outputs the messages csv like and flushes
after each message:
message type tab
Because the path is not found, which is 100% right. It's just a made up
dummy directory to see if errors are working properly.
It seems to be in the 48-100 character path length range which causes
issues, but I can't get a definite number like 48 or 47, since I've
noticed fluctuations, or
On Sunday 14 May 2006 17.16, Florian Klaempfl wrote:
I need no machine readable output (up to now), I need a way to get
flushed writeln output from the RTL on widows to display it in the MSEide
message window (compiler output) and the target window (program output).
On linux I use a PTY to
On Sun, 14 May 2006, Florian Klaempfl wrote:
The error numbers didn't change, they are keep unique.
I propose to do the following:
- add an option -vm (machine readable output)
Using this option the compiler outputs the messages csv like and flushes
after each message:
message type
On 14 May 2006, at 18:16, ik wrote:
You get only a proper fpc when build with make. The x86_64 is defined
and passed by the makefile.
May I ask why does it do such things ?! Why doesn't it use the already
the existed $define statments ?
You have to specify for which target you want to
Martin Schreiber wrote:
On Sunday 14 May 2006 17.16, Florian Klaempfl wrote:
I need no machine readable output (up to now), I need a way to get
flushed writeln output from the RTL on widows to display it in the MSEide
message window (compiler output) and the target window (program output).
On
Try to add a LD param that increases LD's verbosity. Then see if the problem
is LD's parsing. It could be that there are still shortstrings here and
there in the compiler, but 255 chars limits are not likely.
The LD man page says to pass --verbose .. will do some testing and report
On 14 May 2006, at 21:03, L505 wrote:
Passing --verbose option actually inflicts my problem! it doesn't
report back anything
verbose because the --verbose is a few extra characters over the
limit of whatever the
limit is I'm hitting.. hmmm...
The compiler mainly uses shortstrings for
On Sun, 14 May 2006, Daniël Mantione wrote:
Op Sun, 14 May 2006, schreef Michael Van Canneyt:
On Sun, 14 May 2006, Florian Klaempfl wrote:
The error numbers didn't change, they are keep unique.
I propose to do the following:
- add an option -vm (machine readable
On Sun, 14 May 2006, Dani?l Mantione wrote:
XML requires an advanced parser and existing parsers will also produce
complicated parser trees. (All that is needed is a sequence of key/value
pairs, XML is a recursive tree). I'm not against it, but I have a light
preference for something
On 14 May 06, at 19:20, Vincent Snijders wrote:
Tomas Hajny wrote:
On 14 May 06, at 8:54, Vincent Snijders wrote:
Daniël Mantione wrote:
Op Sun, 14 May 2006, schreef Martin Schreiber:
Since some time FPC doesn't flush output on pipes after writeln.
On linux I can use a pseudo terminal,
On Sunday 14 May 2006 20.17, Florian Klaempfl wrote:
Martin Schreiber wrote:
The problem exists not only for the compiler but for all console
programs. I found no way to display the interactive output in a IDE
window on win32. On Linux I can use a pseudo terminal to get flushed
output
Op Mon, 15 May 2006, schreef Martin Schreiber:
On Sunday 14 May 2006 20.17, Florian Klaempfl wrote:
Martin Schreiber wrote:
The problem exists not only for the compiler but for all console
programs. I found no way to display the interactive output in a IDE
window on win32. On Linux
Op Mon, 15 May 2006, schreef Martin Schreiber:
On Monday 15 May 2006 07.29, Daniël Mantione wrote:
Op Mon, 15 May 2006, schreef Martin Schreiber:
How do FPIDE and Lazarus solve the problem?
The IDE retrieves the messages through the comphook unit.
And the output from a console
27 matches
Mail list logo
