On 09/26/11 at 11:00pm, Jordan Wilberding wrote: > Sure man. I left it in a bit of a mess, so let me regroup and see exactly > what is left on the code. >
No problem. We should be basing this probably off my latest master, with the move to term based configs and the split of config and state thats going to affect you quite a bit. You might want to take a look there. I am more then willing to take a look at the code. On a side note, with the latest escript based distribution shell doesn't work (the model has changed quite a lot) we need to take a look at that. I also noticed that the test task isn't discovering tests for some reason. Thats an easy fix and I will get on that this afternoon. The escript stuff is the hardest fix, I am not actually sure how to resolve that. here are the issues - With escript we don't have access to the startup environment for erlang. That means we cannot pass remove the -noshell flag. In any case, escript shuts down when things are done running. - We can startup a shell internally like we used to, but we will loose the nice terminal features of the usual shell (this is probably the short term solution). - we can exec another erlang with the right paths, but there is a lot of ambiguity there around execing the right erlang with the right erts etc. I have short term solution, but no long term solution as yet. Ideas? > Thanks! > JW > > On Sat, Sep 24, 2011 at 10:33 AM, Eric Merritt <[email protected]>wrote: > > > Jordan, > > > > One of things I think is really critical to the 2.0 release is > > dialyzer support. I know you did some work there and ended up making a > > patch to dialyzer itself. However, we also talked about some work > > around to make dialyzer work in the near term. It would be very, very > > good to do those work around and get the task back in place. If you > > aren't terribly interested could you push your interim work somewhere > > where I can pick it up? > > > > Eric > > > > -- > > You received this message because you are subscribed to the Google Groups > > "erlware-dev" group. > > To post to this group, send email to [email protected]. > > To unsubscribe from this group, send email to > > [email protected]. > > For more options, visit this group at > > http://groups.google.com/group/erlware-dev?hl=en. > > > > > > -- > You received this message because you are subscribed to the Google Groups > "erlware-dev" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/erlware-dev?hl=en. > -- You received this message because you are subscribed to the Google Groups "erlware-dev" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/erlware-dev?hl=en.
