[kepler-dev] dynamic typed relation

[Edward A. Lee]

This would be challenging, but not impossible.

The issue is that type inference is a global process.
Type constraints in one place in the model can affect things
in quite a different part of the model (consider for example
adding a field to a record).

I would suggest a scheme more like what Eclipse does, which
is to highlight errors while you are editing.  This would be
far better than forbidding errors (not allowing the connection
to be made).  Imagine if Eclipse would not let you type any
character that results in a syntax error in your file...

Edward


tkd wrote:
> Hello everybody,
> 
> I'm looking for a way to create a dynamic relation between actors, which 
> will verify the types compatibility between the output port and the 
> input port. If types between ports are not compatible, the relation must 
> not be allowed to be created by the user.
> This process has to be active during the workflow design by the user and 
> not at the execution time.
> 
> Does someone have an idea please ?
> Thanks in advance
> 
> tkd
> 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: eal.vcf
Type: text/x-vcard
Size: 351 bytes
Desc: not available
URL: <http://mercury.nceas.ucsb.edu/kepler/pipermail/kepler-dev/attachments/20090909/52435f9a/attachment.vcf>