comment on

Doesnt seem to affect the AS/Win32 builds....

D:\Development>perl -v

This is perl, v5.6.1 built for MSWin32-x86-multi-thread
(with 1 registered patch, see perl -V for more detail)

Copyright 1987-2001, Larry Wall

Binary build 633 provided by ActiveState Corp. http://www.ActiveState.
+com
Built 21:33:05 Jun 17 2002

...

D:\Development>perl -e "chop string;"
Can't modify constant item in chop at -e line 1, near "string;"
Execution of -e aborted due to compilation errors.
[download]

and

E:\>perl58 -v

This is perl, v5.8.0 built for MSWin32-x86-multi-thread
(with 1 registered patch, see perl -V for more detail)

...

E:\>perl58 -e "chop string"
Can't modify constant item in chop at -e line 1, at EOF
Execution of -e aborted due to compilation errors.
[download]

Yves / DeMerphq
---
Writing a good benchmark isnt as easy as it might look.

In reply to Re: perl segfaults when parsing script by demerphq
in thread perl segfaults when parsing script by amphiplex

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


Just another Perl shrine
	PerlMonks