Space in the path / kdevelop 3.0.4

[Andy Cedilnik]

Hi Fred,

That is why we do nightly testing of CMake (and other software). I do
agree with you though that there will be problems and when you (or
somebody else) finds the problem, it will be found probably when you do
not have time for it.

What I would suggest, and this is just a suggestion, is that we
(KDevelop developers and CMake developers) find a way to cooperate to
overcome these kind of limitations. I personally do not use spaces in
the paths for my work, but I can imagine somebody wanting to do that, so
all our testing is done on systems with spaces and without spaces. 

Now, I do not want to single out KDevelop, since Sun's linker I think
also does not supports spaces in the path. Also, as you pointed out, you
have to be able to get things through various shells...

Anyway, I think adding support for spaces in the paths does not hurt
anybody and as long as it is implemented the right way the only time it
will break is on the project with spaces in the path and not on the
project without.

Thank you.

			Andy

On Tue, 2004-11-02 at 12:46, Fred wrote:
> On Monday 01 November 2004 16:11, Andy Cedilnik wrote:
> I'm aware that quotes will solve the problem *here*.
> It's good that CMake has a good implementation, which I'll take your word for.
> 
> My experience (over more years than I'd sometimes prefer),
> in various environments from IBM Mainframes through Middleware
> right down to PCs, is:
> 
> - it *will* cause problems somewhere eventually
> - that will happen when I have *no* time for it
> - it will happen in code I've never seen
> - if the environment isn't open source it will probably
>   happen in code I can neither see nor change
> 
> It's just my 2 cents worth - I'm happy to use underlines or dashes instead,
> but that's my own choice for my own reasons.
> 
> - if you've managed to solve the associated problems in your environment,
>   more power to you!



-
to unsubscribe from this list send an email to kdevelop-request at kdevelop.org with the following body:
unsubscribe »your-email-address«