Hi, 2009/2/18 Rob Hamerling <[email protected]>: > > I suppose the application programmer chooses the interface layer (with > the appropriate include), and all interface layers include the control > layer? I don't know yet what is the best way. I already see 4 interface layers and 2 control layers, which give 8 combinations. I don't like the idea to have a lib for each combination. But I think it is worse to have the user handle this, so maybe we should have all those combinations...
> Also I assume the interface layer is 'hidden' to the user, has no > user-(application) callable functions/procedures (= all names should > start with an underscore)? I agree that the interface is hidden to the user. But if it provides functions for an other lib, then it are not internal functions for that lib. So should they have an underscore??? > Do you already have a description of how the layers should communicate? I did not look in detail yet, but I think we need init, write_data and write_control. And we could choose to combine the two write functions and add a param to indicate data/control Joep --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "jallib" 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/jallib?hl=en -~----------~----~----~----~------~----~------~--~---
