No, edoc hasn't caught up with reality. Therefore the best way is to look at the files or the diffs.
El Oct 11, 2010, a las 1:42 PM, Jordan Wilberding escribió: > So the best way to review this is to look at the generated edoc? Is there any > other documentation? > > JW > > On Sun, Oct 10, 2010 at 11:33 PM, Eric Merritt <[email protected]> wrote: > Guys, > > I have just made a fair number of changes to ktuo specs and > documentation. This should show the direction I am planning to go with > erlware standards, not to mention making ktuo more useful. > > 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.
