I am looking forward to seeing the finished blog - how close is it? On Sun, Apr 3, 2011 at 6:17 AM, Torben Hoffmann <[email protected]> wrote: > > > On Sun, Apr 3, 2011 at 00:36, Eric Merritt <[email protected]> wrote: >> >> What does that mean for us, not having dializer support is annoying, >> but maybe it effects the testing? > > I think the best approach is to stay with the polymorphic type, but make it > a -type instead of -opaque and add a @todo stating that it will change when > dialyzer gets support for polymorphic opaque types. > > I rate the ability to state what the types of the keys and values are higher > than the data encapsulation from opaque/type - especially since it is a > problem that will go away with time. > > Cheers, > Torben > > >> >> On Sat, Apr 2, 2011 at 5:05 PM, Torben Hoffmann <[email protected]> >> wrote: >> > It does not fly... so the opaqueness has to wait for dialyzer support. >> > >> > -- sent from my Android >> > >> > On 2 Apr 2011 23:59, "Eric Merritt" <[email protected]> wrote: >> >>> >> >>> The types in general looks alright - I read somewhere that dialyzer >> >>> does >> >>> not >> >>> support parameterised opaque types. I am in the process of rebuilding >> >>> my >> >>> .dialyzer_plt, so I will check tomorrow. >> >> >> >> Let me know what your findings are. I am very curious. >> >> >> >>>> >> >>>> Right now the name 'proper' is completely non-googleable. Its almost >> >>>> impossible to find information about the project unless know exactly >> >>>> where to look for it. I wonder if the proper folks would be willing >> >>>> to >> >>>> consider a name change to something that is more amenable to finding >> >>>> information. I would like to suggest that to them, what do you think? >> >>> >> >>> That sounds like a good idea - I also went through the google dead >> >>> end... >> >>> though "proper erlang" does show the right links, but that could be >> >>> due >> >>> to >> >>> my search history. >> >> >> >> do you know any of the proper folks. Otherwise I am just going to >> >> contact them through github. >> >>> >> >>> Cheers, >> >>> Torben >> >>> >> >>>> >> >>>> Eric >> >>>> >> >>>> On Thu, Mar 31, 2011 at 3:57 PM, Eric Merritt >> >>>> <[email protected]> >> >>>> wrote: >> >>>> >>> >> >>>> >>> This document is a great start, and I think it covers basically >> >>>> >>> most >> >>>> >>> of >> >>>> >>> the things that need to be covered. I however offer a few >> >>>> >>> suggestions: >> >>>> >>> 1. Remove references to both Martin and Eric. I am sure they will >> >>>> >>> be >> >>>> >>> nice >> >>>> >>> enough to let you use your words verbatim(or close to) without >> >>>> >>> putting >> >>>> >>> up a >> >>>> >>> fight. Just focus on the concepts, not where the idea came from. >> >>>> >> >> >>>> >> I have no problem with that - a quick nod from Martin and Eric >> >>>> >> will >> >>>> >> do >> >>>> >> the >> >>>> >> trick for me! >> >>>> > >> >>>> > Thats just fine with me. No need for attribution here, its a group >> >>>> > document. >> >>>> > >> >>>> >> >>>> -- >> >>>> 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. >> >>>> >> >>> >> >>> >> >>> >> >>> -- >> >>> http://www.linkedin.com/in/torbenhoffmann >> >>> >> > > > > > -- > http://www.linkedin.com/in/torbenhoffmann > > -- > 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. >
-- Martin Logan Erlang & OTP in Action (Manning) http://manning.com/logan http://twitter.com/martinjlogan http://erlware.org -- 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.
