Re: [MirageOS-devel] Remove DEVICE.connect?

[Thomas Leonard <talex5@xxxxxxxxx>]

On 22 January 2015 at 11:10, Nicolas Ojeda Bar <no263@xxxxxxxxxxxxxxx> wrote:
> On Thu, Jan 22, 2015 at 11:04 AM, Thomas Gazagnaire
> <thomas@xxxxxxxxxxxxxx> wrote:
>>>> So, I propose removing connect from the type signatures (but keeping
>>>> it in the implementations). Then, being given a device only implies
>>>> the ability to use it, not the ability to create more devices.
>>
>> Can you still easily compose devices together if you don't have a way to 
>> connect? Who will be responsible for calling the implementation-dependant 
>> connect function? Only the mirage tool in main.ml? (I guess that's already 
>> the case)
>
> Not quite - for example `Tcpip_stack_direct.Make(...).connect` calls
> the `connect` of its arguments, which are only known by their
> signatures.  But it would be easy for the mirage tool to generate code
> to make these calls and pass their results to the `connect` of the
> stack.
>
> In general I think this is an excellent idea!  I will gladly help make
> this change as soon as I'm done with the configuration keys stuff.

If you want to help with the stackv4 changes, that would be great! I'm
tracking progress here:

https://github.com/mirage/mirage/pull/350


-- 
Dr Thomas Leonard        http://0install.net/
GPG: 9242 9807 C985 3C07 44A6  8B9A AE07 8280 59A5 3CC1
GPG: DA98 25AE CAD0 8975 7CDA  BD8E 0713 3F96 CA74 D8BA

_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@xxxxxxxxxxxxxxxxxxxx
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel