=item trim

our Str multi Str::trim ( Str $string )

Removes leading and trailing whitespace from a string.

=cut

I could optionally make the following work:

$string.trim­leadi­ng<0>);

$string.trim­trail­ing<0>);

Setting leading or trailing to false (they default to true) would result in either leading or trailing whitespace not being trimmed. Setting both to false would be a no-op.

either leading or trailing whitespace not being trimmed. Setting both to false

would be a no-op.

Unless someone protests loudly, I can add this to S29, and I (or

someone else with tuits) can implement it in Rakudo.

Alternatively, those could be ltrim() and rtrim().

Or all could be allowed and $string.trim­leadi­ng<0>) could all

$string.rtrim internally.

* Ovid <publiustemp-perl6l­anguage2@yahoo.com> [2009-01-12 16:05]:

++

----- Original Message ----

Alternatively, those could be ltrim() and rtrim(). If you need to

dynamically determine what you're going to trim, you'd couldn't just set

variables to do it, though. You'd have to figure out which methods to call.

Or all could be allowed and $string.trim­leadi­ng<0>) could all

$string.rtrim internally.

From: Larry Wall <larry@wall.org>

On Mon, Jan 12, 2009 at 05:04:50AM -0800, Ovid wrote:

: ...the trivial $string.trim and trim($string) case.

Hmm, I'd think .trim should work like .chomp, and return the trimmed

string without changing the original. You'd use $str.=trim to do it

in place.

Can't say I really like the negated options though. They smell funny.

----- Original Message ----

In the pir, doesn't the "s = self" line copy self, thus ensuring that I'm changing "s" and not "self"?

Or do I need "s = clone self" (or however it's written).

Agreed, but ltrim and rtrim will disappoint Israelis and dyslexics alike. Suggestions welcome as I can't think of anything better.

The .Net framework calls 'em TrimStart and TrimEnd (and has a Trim that does

both). So maybe trim_start and trim_end if we wanted to take that lead...

Alternatively, those could be ltrim() and rtrim(). If you need to dynamically determine what you're going to trim, you'd couldn't just set variables to do it, though. You'd have to figure out which methods to call. Or all could be allowed and $string.trim­leadi­ng<0>) could all $string.rtrim internally.

----- Original Message ----

Alternatively, those could be ltrim() and rtrim(). If you need to dynamically determine what you're going to trim, you'd couldn't just set variables to do it, though. You'd have to figure out which methods to call. Or all could be allowed and $string.trim­leadi­ng<0>) could all $string.rtrim internally.

How about .trim­start) and .trim­end)?

Jonathan (>), Ovid (>>), Larry (>>>):

How about .trim­start) and .trim­end)?

From: Geoffrey Broadwell <geoff@broadwell.or­g>

When I saw your proposed syntax above, instead of reading "don't trim

leading/trailing whitespace", I read "change the definition of

'whitespace' to 'codepoint 0' for leading/trailing".

That of course raises the question of how one *would* properly override

trim's concept of whitespace ....

On Mon, Jan 12, 2009 at 05:04:50AM -0800, Ovid wrote:

: ...the trivial $string.trim and trim($string) case.

Hmm, I'd think .trim should work like .chomp, and return the trimmed

string without changing the original. You'd use $str.=trim to do it

in place.

Can't say I really like the negated options though. They smell funny.

Larry

1. No params, trim all

2. :start or :end, only trim that bit (not a negated option ­

3. If both, goto 1

I'd like not to have to type `.trim­start)` when I could just do

`.ltrim` though.

Also `:!start` to imply `:end` unless `:!end` (which in turn

implies `:start` unless `:!end`)?

I’d like not to have to type `.trim­start)` when I could just do

`.ltrim` though.

Also `:!start` to imply `:end` unless `:!end` (which in turn

implies `:start` unless `:!end`)?

Since that's RTL (Right To Left) text, should ltrim remove the

leading or trailing whitespace?

I like Jonathan's trim_start and trim_end.

Actually that makes me wonder now whether it’s actually a good

idea at all to make the function parametrisable at all. Even

`.ltrim.rtrim` is shorter and easier than `.trim­start,:end)­`!

So I question the usefulness of parametrisation here.

From: Aristotle Pagaltzis <pagaltzis@gmx.de>

Let me ask you first: does a string that runs Right-to-Left start

at the left and end at the right or start at the right and end at

the left?

Now to answer your question, *I* know where the *left* side is in

a string that runs from right to left: it’s at the *left*, same

as if the string ran from the left to the right, because left is

at the *left*.

­

* Aristotle Pagaltzis <pagaltzis@gmx.de> [2009-01-12 21:20]:

Depends on your string implementation if they're

non-destructive, since they potentially have to copy the middle

of the string twice if your implementation can't support one

string pointing into the middle of another. And again, I think

.trim should be non-destructive, and .=trim should be the

destructive version.

I see your point

How about .trim­l, :r) with both as the default?

And if the rtl crowd makes a furor, we can add :a/:o or : /:

or something.

Useful for doing infrequent things. IMO, left and right

trimming are infrequent compared to the frequency of basic

input editing.

From: Aristotle Pagaltzis <pagaltzis@gmx.de>

* Austin Hastings [2009-01-12 22:00]:

Liveable.

How about .trim­start) and .trim­end)?

Maybe :h and :t (head/tail).

'left' and 'right' are probably not the right names for functions which

trim leading and/or trailing space, since their meanings get somewhat

ambiguous if a language renders right-to-left instead of left-to-right

or vice-versa

From: jason switzer <jswitzer@gmail.com­>

If we wanted language dependent version, use :leading, :trailing, and :both.

That will require each implementation properly handle the language

variations.

By the way, good work on this. Everyone loves useful string functions.

----- Original Message ----

:both.

I think :start and :end are my favorites. Huffman++ (maybe :begin and :end

for consistency?).

"

. "

If you can't see that in your client, that's Hebrew from http://www.i18nguy.­com/unicode/shma.htm­l

and means "Hear O Israel, the Lord is our God, the Lord is One".