Re: [fpc-pascal] Re: put data to stdout (fpc vs. gcc)

2007-06-21 Thread Michael Van Canneyt
On Thu, 21 Jun 2007, [EMAIL PROTECTED] wrote: > Hi > > I try your solutions and here are the results: > > 1.) TIP: set text buffer higher (using settextbuf) -> RESULT: procedure > breaks later > 2.) TIP: use flush() after writeln() -> RESULT: procedure breaks on first > flush() > 3.) TIP: co

Re: [fpc-pascal] Re: put data to stdout (fpc vs. gcc)

2007-06-21 Thread Jonas Maebe
On 21 jun 2007, at 19:12, [EMAIL PROTECTED] wrote: I try your solutions and here are the results: 1.) TIP: set text buffer higher (using settextbuf) -> RESULT: procedure breaks later 2.) TIP: use flush() after writeln() -> RESULT: procedure breaks on first flush() 3.) TIP: convert first fl

Re: [fpc-pascal] Re: put data to stdout (fpc vs. gcc)

2007-06-15 Thread Micha Nelissen
Michael Van Canneyt wrote: > You would have to test the speed of each of them separately to be able > to say anything definitive. Like it is now, there is no indication > that it is the float-to-text routine which is to blame. So use sprintf in C, and the equivalent in fpc; and rerun the test. Mi

Re: [fpc-pascal] Re: put data to stdout (fpc vs. gcc)

2007-06-15 Thread Michael Van Canneyt
On Fri, 15 Jun 2007, Jonas Maebe wrote: > > On 15 jun 2007, at 11:44, Michael Van Canneyt wrote: > > > >I'm sorry, but you are not providing enough information to give any useful > > >comments. There is no reason why a generic library would error out because > > >certain code is "too slow". Is

Re: [fpc-pascal] Re: put data to stdout (fpc vs. gcc)

2007-06-15 Thread Jonas Maebe
On 15 jun 2007, at 11:53, Jonas Maebe wrote: That's quite unlikely to be the case. settextbuf seldomly makes a difference for me. Especially if you write to standard output, which will trigger a flush after every writeln anyway. (unless you redirect the output to a file, at least under *ni

Re: [fpc-pascal] Re: put data to stdout (fpc vs. gcc)

2007-06-15 Thread Jonas Maebe
On 15 jun 2007, at 11:44, Michael Van Canneyt wrote: I'm sorry, but you are not providing enough information to give any useful comments. There is no reason why a generic library would error out because certain code is "too slow". Is this a real time application on an embedded system or s

Re: [fpc-pascal] Re: put data to stdout (fpc vs. gcc)

2007-06-15 Thread Michael Van Canneyt
On Fri, 15 Jun 2007, Jonas Maebe wrote: > > On 15 jun 2007, at 11:24, [EMAIL PROTECTED] wrote: > > >Hi Jonas, > > > > > >I know, programs with a writeln() have lower performance, but I > > > >think, printf() and writeln() must do the same. This need time to > > > >calculate. > > >

Re: [fpc-pascal] Re: put data to stdout (fpc vs. gcc)

2007-06-15 Thread Jonas Maebe
On 15 jun 2007, at 11:24, [EMAIL PROTECTED] wrote: Hi Jonas, I know, programs with a writeln() have lower performance, but I think, printf() and writeln() must do the same. This need time to calculate. But the difference between printf() and writeln() are so, that the fpc program

Re: [fpc-pascal] Re: put data to stdout (fpc vs. gcc)

2007-06-14 Thread Jonas Maebe
On 14 jun 2007, at 12:22, [EMAIL PROTECTED] wrote: I know, programs with a writeln() have lower performance, but I think, printf() and writeln() must do the same. This need time to calculate. But the difference between printf() and writeln() are so, that the fpc program breaks wi