~dr|z3d
@RN
@StormyCloud
@T3s|4
@T3s|4_
@eyedeekay
@orignal
@postman
@zzz
%Liorar
+Afkaid
+FreefallHeavens
+Unbur
+Xeha
+cumlord
+goose2_
+j6
+poriori
+profetikla
+r00tobo
+snex
+uop23ip
+weko
An0nm0n
Arch
Danny
DeltaOreo
DiCEy1904
Irc2PGuest11229
Irc2PGuest21326
Irc2PGuest48909
Irc2PGuest54864
Irc2PGuest71250
Nausicaa
Onn4l7h
acetone_
anon2
anontor
anu
bak83
boonst
enoxa
fujifilm
goose2
itsjustme
mareki2pb
onon_1
qend-irc2p
shiver_
tr
u5657
user
veiledwizard
xen_NULL
dr|z3d
does this look saner, or am I making the same mistake here?
dr|z3d
b32 = reader.readLine();
dr|z3d
if (b32 == null) {return;}
zzz
same
dr|z3d
yeah, figured.
dr|z3d
so, totally pointless then, as you say. this should cover it: while((b32 = reader.readLine()) != null) {
dr|z3d
well, not totally pointless, as it prevents the issue from triggering, but not the correct fix.
dr|z3d
what about checking the filesize instead?
dr|z3d
int fileLength = (int) file.length();
dr|z3d
if (fileLength == 0) {return;}
zzz
better
zzz
but the reason for a ticket was that this is low priority, not for today, so if you want my analysis you'll have to sit tight ))
dr|z3d
sure, I don't think it's something that'll affect most people.
dr|z3d
if there's no file at all, non-issue. only zero length file, or presumably a file containing no b32s.
dr|z3d
got a stacktrace zzz, bug report updated.