[MinGW-notify] [ mingw-Bugs-3469512 ] chomp($var = <STDIN>) crashes perl if there is no STDIN

[SF/projects/mingw n. l. <min...@li...>]

Bugs item #3469512, was opened at 2012-01-04 11:18
Message generated for change (Comment added) made by csware
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=102435&aid=3469512&group_id=2435

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: non-mingw
Group: None
Status: Closed
Resolution: Invalid
Priority: 5
Private: No
Submitted By: Sven Strickroth (MrTux) (csware)
Assigned to: Nobody/Anonymous (nobody)
Summary: chomp($var = <STDIN>) crashes perl if there is no STDIN

Initial Comment:
chomp($var = <STDIN>) crashes perl if there is no STDIN.

Exampel crash:
Use of uninitialized value in chomp at test.pl line 1.
0 [main] perl.exe" 1916 handle_exceptions: Exception: STATUS_ACCESS_VIOLATION
1297 [main] perl.exe" 1916 open_stackdumpfile: Dumping stack trace to perl.exe.stackdump


----------------------------------------------------------------------

Comment By: Sven Strickroth (MrTux) (csware)
Date: 2012-06-14 07:12

Message:
Why should an interpreter ever crash? E.g. perl on *nix system does not
crash in these situations - however, *nix perl correctly outputs the
warning "Use of uninitialized value in chomp" (no crash).

----------------------------------------------------------------------

Comment By: Earnie Boyd (earnie)
Date: 2012-06-14 05:55

Message:
IMO perl should crash in this case.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=102435&aid=3469512&group_id=2435