|
From: Frank V. C. <fr...@co...> - 2000-08-19 16:38:04
|
Hans Dulimarta wrote: > > "Frank V. Castellucci" wrote: > > > > Then demand we slow down. Seriously, I'd rather you be involved in some > > I don't want to slow down the project just because a rookie (that is me) > came in.... Bull dung!!! The faster you all come up to speed, the less time it will be me doing the code <grin>, and more time I can spend on <shudder> LaTex, <yipes> PHP, and <dare I say> writing documentation. > > of the neat stuff that we are just getting into a position to do. Of > > course I think things like frameworks, excercising the language, and > > providing some very serious implementation aids to other developers is > > neat. :) > > > > The core is a jumping off point. Throw some conversation about Threads, > > Semaphores, Frameworks around. We really can do so cool things at this > > point. > > I am an RTM kinda person. If it is documented somewhere, I'll read it and > then ask if something is not clear. [It may seem that I have been too > quiet, > not responsive enough to comments that you guys sent to the mailing list. > In fact, I've been studying how the implemented classes relate to the model > (UML > diagram stuffs)]. Now, if only there where a M for you to RTM of :) > So far my exploration into the deep space > of Semaphore "family tree" has given me enough understanding of it. > > I infer the following: > o All requirements for Semaphore (& co.) have been transfered into design. check > o A large portion of this design has been implemented check > o When the design mentions "SemaphoreIdentifier", the implementation views > this as > SemGroupId + SemId. Either or, correct > o Low level system calls used for the implementation are semget, semctl, > and semop. check > Some questions I'd like to ask. > When I open an *.mdf file using MagicDraw, the left window pane shows a > tree of > clickable nodes. Which part of the (sub)tree(s) should I concentrate on > browsing > during the implementation. > I understand that for the implementation of EventSemaphore (which is what > I'm doing now) > Many-To-One is one of the things I should concentrate. What else? Besides the implementations of Gateway and Mutex, EventSemaphores are probably going to need some help from timers and signals, and you may find we need to implement those first. Which of course is based on Analysis and Design work in those areas. > What guide(s) should I follow when writing a test driver? Really something that could be considered a unit test (each interface being somehow excercised is the goal). > In the implementation I saw SemaphoreCommon but not in the diagram? Any > explanation? Yes, I was getting to the point that the SemaphoreCommon was much needed because of the "shared" requirement between address space hole. Now that it is done, I can update the diagrams, unless that is something you want to do to get used to the tools. > Oops.....I ask too much...better stop here... :-) No, I would rather you keep asking questions. It will get you up to speed faster. I have alot I can say on any facet of the library that doesn't always come out in the current documentation. > > > > > I don't think we have the boundry for the universe of discourse defined > > yet :) > > > > I'd rather leave it open.... > > > > > -- > > Frank V. Castellucci > > http://corelinux.sourceforge.net > > OOA/OOD/C++ Standards and Guidelines for Linux > > http://PythPat.sourceforge.net > > Pythons Pattern Package > > > > _______________________________________________ > > Corelinux-develop mailing list > > Cor...@li... > > http://lists.sourceforge.net/mailman/listinfo/corelinux-develop > > -- > Hans Dulimarta, Ph.D. dul...@co... > P: 517-432-7589 http://www.egr.msu.edu/~dulimart > F: 760-281-7691 http://corelinux.sourceforge.net > Elec. & Comp. Engg., Mich. State Univ., E. Lansing, MI 48824 > > _______________________________________________ > Corelinux-develop mailing list > Cor...@li... > http://lists.sourceforge.net/mailman/listinfo/corelinux-develop -- Frank V. Castellucci http://corelinux.sourceforge.net OOA/OOD/C++ Standards and Guidelines for Linux http://PythPat.sourceforge.net Pythons Pattern Package |