[jsr294-modularity-eg] Module Use Cases

[Peter Kriens]

I tried to create different use cases, trying hard to not solve the  
problem :-) The primary purpose is to have a vocabulary so when I talk  
about the "merging" model, or "siblings" then we can share the same  
mental model. One (unfortunate) conclusion could be to limit to only  
the "hello-world" model. But I think that would miss out on a lot of  
features that I see heavily used in practice.

Kind regards,

	Peter Kriens


On 5 mrt 2009, at 19:41, Michal Cierniak wrote:

> Thanks, Peter!
>
> Apologies for missing the phone call yesterday, so perhaps my question
> has already been answered.  The slides talk both about language
> features and deployment of modules, right?  How does this interact
> with versioning?  What happens in the last slide ("Merging") when the
> two versions of Felix are different?
>
> On Thu, Mar 5, 2009 at 1:52 AM, Peter Kriens  
> <peter.kriens at aqute.biz> wrote:
>> After last call I think we need a terminology for the different  
>> ways modules
>> can be used. At Alex request, I made this a presentation because  
>> documents
>> over 5 pages is deemed too complicated. :-)
>>
>>
>> If people have more variations, or even better, actual uses cases  
>> for the
>> different ways you can use modules, let me know. I will include them.
>>
>> Kind regards,
>>
>>       Peter Kriens
>>
>>
>>
>>
>>
>>
>> _______________________________________________
>> jsr294-modularity-eg mailing list
>> jsr294-modularity-eg at cs.oswego.edu
>> http://cs.oswego.edu/mailman/listinfo/jsr294-modularity-eg
>>
>>
> _______________________________________________
> jsr294-modularity-eg mailing list
> jsr294-modularity-eg at cs.oswego.edu
> http://cs.oswego.edu/mailman/listinfo/jsr294-modularity-eg