WIN-28.1: fix POSIX file descriptor numbering assumptions

[Adam Megacz]

Oh crap. Huge, huge typo on my part. I will correct this, very sorry.

  - a

Tom Tromey <tromey@redhat.com> writes:
> >>>>> "Adam" == Adam Megacz <patches@lists.megacz.com> writes:
> 
> Adam> Index: natFileDescriptorEcos.cc
>  
> Adam> +void
> Adam> +java::io::FileDescriptor::init(void)
> Adam> +{
> Adam> +  in = new java::io::FileDescriptor((jint)(GetStdHandle (0)));
> Adam> +  out = new java::io::FileDescriptor((jint)(GetStdHandle (1)));
> Adam> +  err = new java::io::FileDescriptor((jint)(GetStdHandle (2)));
> Adam> +}
> 
> Shouldn't these just be `0', `1', `2'?
> 
> Adam> Index: natFileDescriptorPosix.cc
> Adam> +void
> Adam> +java::io::FileDescriptor::init(void)
> Adam> +{
> Adam> +  in = new java::io::FileDescriptor((jint)(GetStdHandle (0)));
> Adam> +  out = new java::io::FileDescriptor((jint)(GetStdHandle (1)));
> Adam> +  err = new java::io::FileDescriptor((jint)(GetStdHandle (2)));
> Adam> +}
> 
> Likewise.
> 
> Tom
> 

-- 
"If I put copyrighted material into the 'chewy nougat center', I can
 claim the crunchy chocolate coating is an 'Access Control
 Mechanism'."                                     --lynx_user_abroad

Why Windows NT/2k/XP is unreliable: www.zappadoodle.com