Bugs: What means invalid?

Help
Jens Wulf
2010-02-15
2012-12-29
  • Jens Wulf
    Jens Wulf
    2010-02-15

    Hello,
    I've posted the following Problem with V 5.4000 as Bug:
    Bhaskar marked this as Closed/Invalid. What does this mean?
    Isn't it a bug?
    Greets Jens


    root@linux2:/tmp# ls -l
    total 0
    -rw-r-r- 1 root root 0 2010-02-14 20:25 test
    root@linux2:/tmp# m

    GTM>S DEV="/tmp/test" O DEV:READONLY U DEV S X=$ZEOF C DEV W X
    0
    GTM>

    This happens in the new Version 5.4
    Greets Jens

     
  • K.S. Bhaskar
    K.S. Bhaskar
    2010-02-15

    Yes, it means it is not a bug.  There previously was a bug, which is now fixed.

     
  • Jens Wulf
    Jens Wulf
    2010-02-15

    I really don't understand this.
    When i'm opening a file and there's nothing more to read I would expect $ZEOF to be set as true. This was the behaviour of all Verions <5.4000 also. But you are the Guru :-) …

     
  • K.S. Bhaskar
    K.S. Bhaskar
    2010-02-15

    The semantics are that a process has to attempt a READ from a file before it can know that it is at the EOF.  It was a bug that GT.M was setting $ZEOF before that READ.

     
  • Jens Wulf
    Jens Wulf
    2010-02-15

    Thank you for the fast answer. I've had a look in the manual and saw that you are principially right, but i don't see the disadvantage of the old behaviour. I'd say the old behaviour wasn't a bug, it was a feature.

     
  • K.S. Bhaskar
    K.S. Bhaskar
    2010-02-15

    The old behavior was inconsistent.  The new behavior (a) matches the documented behavior, (b) is consistent, and (C) makes customer applications run correctly.  Unfortunately, your code seems to have been hit by the law of unintended consequences of fixing a bug (or it  feels to you like removing a feature).  My regrets, Jens.