On 30 September 2015 at 13:59, Justin Cormack <[email protected]> wrote:
> On 30 September 2015 at 09:15, Martin Lucina <[email protected]> wrote: > > Have you considered simplifying the syntax even more? If we remove > > everything that's redundant your example from above becomes: > > > > === snip === > > version 20150928 > > > > create hw_coolbeans "Insert coolbeans descr here" > > assimilate hw_virtio > > remove -lrumpkern_sysproxy > > add /home/pooka/startmsg.o > > === snip === > > > > For prior art in this space, take a look at FireHOL, a firewall generator > > using a shell-based DSL for configuration: http://firehol.org/#firehol > > > > Also, how about using the more conventional "include" or "import" instead > > of "assimilate"? > > I really don't see the benefit over this whole thing over a normal > command line for linking, which everyone is familiar with. > > Bake is just link, users know how to link, and making a whole language > for linking just seems over complex. > The config file could be used as a component registry (JSON should be enough) for specifying component->libs mapping and inter-component dependencies. Then it becomes private to rumpbake. The end user only has to provide the top-level component names as part of the command invocation. Something like --list-components helps a lot with discoverability of the components as well. Components outside the rumpun tree need to supply a config file providing the above mappings which can then be merged with the built-in registry at launch time. cheers, --krishna -- Programming is difficult business. It should never be undertaken in ignorance. --Douglas Crockford, "Javascript: The Good Parts"
