[ 
http://dev.sourcefabric.org/browse/LS-123?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16307#action_16307
 ] 

David Baelde commented on LS-123:
---------------------------------

I'm leaning towards keeping an active_source type, to stick to the actually 
meaningful concepts.

Another issue that I realized just today by chance: the clock function is 
currently (source)->source but we commonly use it for active source, eg. 
clock(sync=false,output.dummy(...)) in which case it is passed an active_source 
but it still returns a source so we get an error because the resulting source 
is unused. One easy solution to implement would be to restrict clock to 
(active_source)->active_source but it'd probably rule out some things we want 
to write -- for example, out(add([buffer(clock(s1)),buffer(clock(s2))])) which 
is a bit artificial, allowing s1 and s2 to be executed/streamed concurrently. 
Another solution is to make it (source)->unit which would force to write things 
differently, but essentially allow the same things.

> Unused variables
> ----------------
>
>                 Key: LS-123
>                 URL: http://dev.sourcefabric.org/browse/LS-123
>             Project: Liquidsoap
>          Issue Type: New Feature
>          Components: Liquidsoap
>            Reporter: David Baelde
>            Assignee: David Baelde
>
> Add a warning for unused variables. This would be useful for users who don't 
> understand the let-in style of definitions. One problem is that the warning 
> would be issued a lot for utils.liq.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://dev.sourcefabric.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

------------------------------------------------------------------------------
EditLive Enterprise is the world's most technically advanced content
authoring tool. Experience the power of Track Changes, Inline Image
Editing and ensure content is compliant with Accessibility Checking.
http://p.sf.net/sfu/ephox-dev2dev
_______________________________________________
Savonet-devl mailing list
Savonet-devl@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/savonet-devl

Répondre à