in reply to Debugger Bug?

It could be considered odd that "p" writes to (and therefore flushes) STDOUT, but I wouldn't say it's a problem.

Or are you complaining about "x"? It's working properly. Did you mean to turn off buffering on STDOUT? or did you mean to do x "horst" instead of x print "horst"?

Update: "x" flushes the output on both 5.8.8-linux and 5.10.1-Windows for me.

Replies are listed 'Best First'.
Re^2: Debugger Bug?
by LanX (Saint) on Sep 02, 2009 at 23:32 UTC
    I'm confused about the buffering, why should x turn on any buffering at all?

      DB<24> @arr=a..z
 
  DB<25> x print @arr
0  1
  DB<26> 
abcdefghijklmnopqrstuvwxyz
  DB<26> print @arr
abcdefghijklmnopqrstuvwxyz
  DB<27>

    [download]

    please note at line 26 I just typed return !?!

    Cheers Rolf

    UPDATE: "This is perl, v5.10.0 built for i486-linux-gnu-thread-multi"

[reply]
[d/l]
[select]

      Buffering is on by default. Try perl -e"print 'foo'; sleep 5; print 'bar'"

      please note at line 26 I just typed return !?!

      Reading from STDIN is documented to flush STDOUT. (One or both may need to be associated with a terminal for that to occur.)

[reply]
[d/l]
        Sure, turning on AUTOFLUSH helps!

          DB<1> $| = 1
 
  DB<2> x print "horst"
horst0  1
  DB<3> p print "horst"
horst1
  DB<4>  print "horst"
horst

        [download]

        But it's strange that only x doesn't flush automatically while other commands do ...

          DB<5> $| = 0
 
  DB<6> x print "horst"
0  1
  DB<7>  print "horst"
horsthorst
  DB<8> p print "horst"
1horst

        [download]

        Cheers Rolf

[reply]
[d/l]
[select]

In Section Seekers of Perl Wisdom