There is as I understand it nothing wrong with compiling multiple modules with a main function using one command. It's very useful if you want many separate Elm widgtts that share the same runtime and library code. As I understand you can do:
Foo.hs: module Foo main = HTML.App.Program... Bar.hs: module Bar main = HTML.App.Program... elm-make Foo.elm Bar.elm --output combined.JS And combined.JS will expose Elm.Foo and Elm.Bar, which can separately be instantiated but share the same runtime and things. All of this to say, I would assume that ports should be scoped by the main module that imports them and that this is a bug. -- You received this message because you are subscribed to the Google Groups "Elm Discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to elm-discuss+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
