Re: [Boost-build] [python] Python build description

Subject: Re: [Boost-build] [python] Python build description
From: Rene Rivera (grafikrobot_at_[hidden])
Date: 2010-07-20 12:45:04

On 7/20/2010 11:12 AM, Vladimir Prus wrote:
> On Wednesday 14 July 2010 22:50:01 Spencer E. Olson wrote:
>
>> project('/myLib',
>>    define('POUND_DEFINE=blah'),
>>    include('src/'),
>>    client_requirements=[
>>      include('src/'),
>>      define('CLIENT_POUND_DEFINE=blar'),
>>    ]
>> );
>>
>> library('library',
>>    'src/myLib/func.cpp',
>>    define('OTHER_POUND_DEFINE=hahaha'),
>>    'src/myLib/other.cpp',
>> );
>
> Spencer,
>
> this looks pretty nice. I have one design question though --
> what is the guideline when to use function (e.g. 'define') and when to
> use keyword arguments (like 'client_requirements')? How can this be
> explained to users, so that there's no confusion?

Haven't chimed in about this subject.. But I'm not fond of using Python 
as the description language. Sorry, but it's just not suited for the 
job. I'd rather keep something like the Jam syntax, but integrated with 
Python. I.e. writing the parser in Python would be fine. But it's just 
that I think Python is the wrong tool for writing declarations.

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