From: Phil Blundell <pb@pbcl.net>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/1] utils.bbclass: make FILESEXTRAPATHS colon delimited
Date: Fri, 27 May 2011 10:37:32 +0100 [thread overview]
Message-ID: <1306489052.2525.400.camel@phil-desktop> (raw)
In-Reply-To: <4DDF17A7.4010807@linux.intel.com>
On Thu, 2011-05-26 at 20:16 -0700, Darren Hart wrote:
> So by changing from split() to split(":") we change the behavior of
> split when operating on empty strings, requiring us to special case the
> output. Rather obnoxious wouldn't you say?
Yes, that is an annoying misfeature. The other related thing to watch
out for is this:
>>> print " a b ".split()
['a', 'b']
>>> print ":a:b:".split(":")
['', 'a', 'b', '']
>>>
... in other words, if you make the separator be anything other than a
space, you need to take special care to strip off any null elements that
might have been accidentally generated at the start and end.
p.
next prev parent reply other threads:[~2011-05-27 9:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-25 23:05 [PATCH 0/1] utils.bbclass: make FILESEXTRAPATHS colon delimited Darren Hart
2011-05-25 23:05 ` [PATCH 1/1] " Darren Hart
2011-05-26 23:46 ` Richard Purdie
2011-05-27 3:16 ` Darren Hart
2011-05-27 9:37 ` Phil Blundell [this message]
2011-05-27 15:45 ` Richard Purdie
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1306489052.2525.400.camel@phil-desktop \
--to=pb@pbcl.net \
--cc=openembedded-core@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox