Re: [Boost-build] [future] Implementation language(s)..

Subject: Re: [Boost-build] [future] Implementation language(s)..
From: Stefan Seefeld (stefan_at_[hidden])
Date: 2016-10-25 15:07:37

On 25.10.2016 14:57, Vladimir Prus wrote:
>
>
> On 25-Oct-16 9:47 PM, Stefan Seefeld wrote:
>> On 25.10.2016 14:45, Klemens Morgenstern wrote:
>>> Yes, I do in fact envision two languages here and this thread is about
>>> the implementation, NOT the usage, i.e. the target-declarations. So if
>>> you only use the features provided by the system, you'd neither need
>>> python nor C++. But if you need an extension you write in in Python or
>>> C++. I.e. if you have a small one, use python, if you have a big one
>>> (e.g. Java) use C++.
>>
>> So if I start a new project and I want to use Boost.Build for it, how
>> many languages do I need to know to write the build system ? (I'd find
>> anything other than '1' unacceptable.)
>
> I think the answer depends on whether people will like Python syntax
> for declaring targets. If I recall, SCons syntax was not very nice,
> but then in Javascript land, there are tools like Gulp and Grunt that
> are basically using chained function calls or maps to describe targets,
> and apparently doing fine.
>
> Do you have any ideas how Python syntax might look?
>

Not right now; it requires some prototyping. I could try to play around
over the next couple of weeks to see what I can come up with.
(Didn't we have this very same discussion already many years ago ? :-) )

        Stefan

-- 
      ...ich hab' noch einen Koffer in Berlin...