Re: [Boost-build] SHELL and trailing newlines

From: Rene Rivera (grafikrobot_at_[hidden])
Date: 2006-10-04 21:48:46

Johan Nilsson wrote:
> "Rene Rivera" <grafikrobot_at_[hidden]> skrev i meddelandet 
> news:45240ADA.5090902_at_gmail.com...
>> Johan Nilsson wrote:
>>> "Rene Rivera" <grafikrobot_at_[hidden]> skrev i meddelandet
>>> news:452406C8.6010104_at_gmail.com...
>>>
>>>> SHELL/COMMAND to act as the CLI shell do. Perhaps an
>>>> "eol-delimited-output":
>>>>
>>>>   LIBXML_INCLUDES = [ SHELL "pkg-config --cflags libxml-2.0" :
>>>> eol-delimited-output ] ;
>>>>
>>>> One might want to implement a 'ws-delimited-output' at the same time :-)
>>> Why not use MATCH on the output to remove whatever you want? Or am I 
>>> missing
>>> something?
>> Not missing anything :-) One advantage to doing this at the SHELL level
>> is that it will use less memory, because it can parse the output as it
>> comes in and hence saves of having the possibly big output string around.
> 
> Ok, how about simply allowing a regex expression as the delimiter parameter, 

Sure. I suppose you have some use cases? And hence why you are 
suggesting it. Personally I have a need for smarter parsing of SHELL 
output than just regex delimited.

> with eol as the default (or perhaps the default should be to get the 
> complete output)?

To keep backward compatibility it would have to be an extra argument 
with the default being the current behavior.

-- 
-- Grafik - Don't Assume Anything
-- Redshift Software, Inc. - http://redshift-software.com
-- rrivera/acm.org - grafik/redshift-software.com
-- 102708583/icq - grafikrobot/aim - grafikrobot/yahoo