Re: bin/44232: sort in unique numeric mode failes to distinquish 0 and <empty> in 5.1

[David Holland <dholland-bugs%netbsd.org@localhost>]

The following reply was made to PR bin/44232; it has been noted by GNATS.

From: David Holland <dholland-bugs%netbsd.org@localhost>
To: gnats-bugs%NetBSD.org@localhost
Cc: 
Subject: Re: bin/44232: sort in unique numeric mode failes to distinquish 0
 and <empty> in 5.1
Date: Sun, 13 Feb 2011 08:03:31 +0000

 On Tue, Dec 14, 2010 at 04:45:00PM +0000, 
Wolfgang.Stukenbrock%nagler-company.com@localhost wrote:
  >     ok_raid=" raid0 raid1 raid2 raid3 raid4 raid5 raid6 raid7 raid8 raid9 
raid10 raid11 raid12 raid13 raid14 raid15"
  >     echo "$ok_raid" | tr ' ' '\n' | sort -u -k1.5n | tr '\n' ' '
  > 
  >     You will get " raid1 raid2 raid3 raid4 raid5 raid6 raid7 raid8 raid9 
raid10 raid11 raid12 raid13 raid14 raid15".
  >     The "rail0" field is lost ...
 
 Here are a couple other somewhat related cases that also do the wrong thing:
 
    % ( echo 1e+600 ; echo 1e+800 ) | sort -un
    1e+600
    % ( echo 1e+10 ; echo 10e+9 ) | sort -un
    1e+10
    10e+9
    % 
 
 These problems affect current and not just 5.1. I guess they're a
 consequence of the fixes for various worse problems that appeared in
 5.0's sort...
 
 -- 
 David A. Holland
 dholland%netbsd.org@localhost