Re: [elm-discuss] Unrelated modules having ports with the same name

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

Re: [elm-discuss] Unrelated modules having ports with the same name

Thanks for the reply. I want to try out Elm as embedded element(s) instead of full page app, but due to the original DOM structure and CSS layout, I cannot put everything inside a single element. Then I thought it would be a good idea to create two separated modules, and "pipe" then through por

Re: [elm-discuss] Unrelated modules having ports with the same name

This is the intended behavior. The strange thing about what you are trying to do is that ModuleA and ModuleB both have a function called main. Are you intending them to be a part of the same program? Programs should only have one "main" function. If ModuleA and ModuleB are supposed to be different

[elm-discuss] Unrelated modules having ports with the same name

Hello, I find it confusing about ports in modules, I have sent an issue but didn't get notice for a month, so I'd like to post it here for discussion. I have two modules, they both have a port with the same name: port module ModuleA exposin