Sent from my non-google-device
> On Jan 11, 2015, at 16:45, Emacs the Viking <[email protected]> wrote: > > > >> On Sunday, 11 January 2015 21:37:54 UTC, Kai Janson wrote: >> I just re-read your issues; the recompiling works ... as long as you don't >> add new functions. >> If you perform a code change on ANYTHING existing, it works. > > Well, adding new functions is kind of what development mode is all about > isn't it! > Totally agree. It should be a no-brainer, but I do recall that due to the > parameterized modules (and Erlang's lack of support now) the compilation is a > lot more taxing. > That also explains why your code did not work when compiled from within > Emacs. > All the magic is done in the ChicagoBoss compiler chain for the module to > work. >> >> Controllers: >> There is actually a ticket open to fix this very annoying bug. I >> troubleshot this even with Evan and it's a pesky error. I hope that someone >> in the core team fixes this very soon. >> Elixir is able to recompile and pick up the newly added function(s), so it >> is not a short coming of the Erlang VM itself, it's ChicagoBoss dropping the >> ball somewhere in the modified compiler-chain(s). >> > Bummer. > Yup, I'd say so. See above, CB compilation is a non-trivial task. > >> Other code directories (lib and others): >> The reloader doesn't pickup added functions up as well (see above). >> Adding new modules works, but again, newly added functions are >> skipped/ignored. >> > Why is it apparently so complicated to just reload a changed file? I am also > finding it hard to create debuggable BEAM files too. I think I may end up > porting to yaws at this rate despite the great vibe CB ives me. :( > > Yaws is great, but ... it's a tank! I love yaws, but it might not fit your > bill 100% either. You will still need to add database support and the like. > But, performance-wise it is awesome and it offers a lot for the so inclined > developer. Your mileage might vary. > > >> Also, I think I had seen that you had referred to one of the controllers >> just by _web_controller and not smsengine_web:* ; if that's the case, that >> would be a user error. That could also explain why it does not work in >> either mode, development as well as production. >> > > I spotted that and fixed it shortly after I posted but the problem persists. > Good call! > > -- > You received this message because you are subscribed to the Google Groups > "ChicagoBoss" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > Visit this group at http://groups.google.com/group/chicagoboss. > To view this discussion on the web visit > https://groups.google.com/d/msgid/chicagoboss/8f6b21dc-01ae-459a-98b4-869d4c29863c%40googlegroups.com. > For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "ChicagoBoss" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. Visit this group at http://groups.google.com/group/chicagoboss. To view this discussion on the web visit https://groups.google.com/d/msgid/chicagoboss/91F587CF-D821-4DBA-AA78-9F5B2FFA6549%40gmail.com. For more options, visit https://groups.google.com/d/optout.
