comment on

I try to hide it, but my first love was Dylan and I'm a functional programmer at heart. It often frustrates me that I can't use the return values of chomp, s, pop, etc. to chain operations/functions.

Had I the capability to turn back the clock and influence Larry in his language decisions, I would vote for the operators like the above to return the value that they now modify in place, and for each to have a bang complement (e.g. chomp!) that works the way the current ones do. Ruby does this to some extent.

tchrist has been known to say similar things, based on his observations of what people new to the language expect. See, for example, this perl6 post. I can't see a change like this really happening -- it would affect too many scripts.

-dlc

In reply to Re: How do you chomp your chomps? by dchetlin
in thread How do you chomp your chomps? by kaatunut

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.


Think about Loose Coupling
	PerlMonks