Menu
▾
▴
corelinux-develop — Developer centric mail list for CoreLinux++
You can subscribe to this list here.
| 2000 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(144) |
Aug
(209) |
Sep
(117) |
Oct
(44) |
Nov
(41) |
Dec
(1) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2001 |
Jan
(14) |
Feb
(64) |
Mar
(25) |
Apr
(35) |
May
(29) |
Jun
(6) |
Jul
(7) |
Aug
|
Sep
(12) |
Oct
(6) |
Nov
|
Dec
(1) |
| 2002 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(1) |
Jun
(1) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2003 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(1) |
Dec
|
| 2004 |
Jan
(1) |
Feb
|
Mar
|
Apr
|
May
(1) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(1) |
Nov
|
Dec
|
| 2006 |
Jan
(7) |
Feb
(5) |
Mar
(2) |
Apr
(1) |
May
(9) |
Jun
(11) |
Jul
(9) |
Aug
(5) |
Sep
(7) |
Oct
|
Nov
|
Dec
(9) |
| 2007 |
Jan
(3) |
Feb
(5) |
Mar
(2) |
Apr
(5) |
May
(1) |
Jun
(1) |
Jul
(5) |
Aug
(16) |
Sep
(7) |
Oct
(8) |
Nov
(8) |
Dec
(2) |
| 2008 |
Jan
(4) |
Feb
(7) |
Mar
(27) |
Apr
(26) |
May
(28) |
Jun
(17) |
Jul
(38) |
Aug
(13) |
Sep
(17) |
Oct
(12) |
Nov
(37) |
Dec
(51) |
| 2009 |
Jan
(41) |
Feb
(19) |
Mar
(30) |
Apr
(43) |
May
(138) |
Jun
(111) |
Jul
(76) |
Aug
(27) |
Sep
(28) |
Oct
(33) |
Nov
(11) |
Dec
(18) |
| 2010 |
Jan
(3) |
Feb
(5) |
Mar
(40) |
Apr
(51) |
May
(74) |
Jun
(76) |
Jul
(46) |
Aug
(41) |
Sep
(26) |
Oct
|
Nov
|
Dec
|
| 2012 |
Jan
|
Feb
(1) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Frank V. C. <fr...@co...> - 2000-09-15 15:31:17
|
Christophe Prud'homme wrote: > I can do the rpm-doc also I know if we are in a fix I can ask that as well, but it is a good thing to have more than one (1) person as a contingency, oui? > > > C. > -- > Christophe Prud'homme | > MIT, 77, Mass Ave, Rm 3-243 | He that breaks a thing to find out > Cambridge MA 02139 | what it is has left the path of wisdom. > Tel (Office) : (00 1) (617) 253 0229 | -- J.R.R. Tolkien > Fax (Office) : (00 1) (617) 258 8559 | > http://augustine.mit.edu/~prudhomm | > Following the hacker spirit > _______________________________________________ > Corelinux-develop mailing list > Cor...@li... > http://lists.sourceforge.net/mailman/listinfo/corelinux-develop |
|
From: Hans - D. <dul...@eg...> - 2000-09-15 14:04:37
|
On Fri, 15 Sep 2000, Frank V. Castellucci wrote: > Date: Fri, 15 Sep 2000 06:41:40 -0400 > From: Frank V. Castellucci <fr...@co...> > Reply-To: cor...@li... > To: cor...@li... > Subject: Re: [Corelinux-develop] just a word... > > Christophe Prud'homme wrote: > > > > On Thu, 14 Sep 2000, you wrote: > > > Hans, > > > > > > No prob with the debian or rpm builds. As I said, I am willing to just post > > > tar.gz and the rpm base and dev packages for the short-term. But, we > > > obviously are on the spot with docs and debian. > > no problem with package creation for me > > but that will be all I can do > > since it is automatic it won't take much time > > I appreciate you offering that, and I will let you know when we are > ready (although I am sure you see the message between Hans and I for the > meantime in this list). > > Hans, > > Could you run: > > ./configure > ./make rpm I'm in my office now. I forgot to start my RH Linux this morning, I could not login there now. I'll do it as soon as I got home. > > when you have a chance. I would like to know if you have the ability to > create the rpm-docs. On my system I get a failure which prevents the > generation of the ps and pdf files. > > I should take a closer look but I am swamped right now with new job > prospects, interviews, etc. > > > > > C. > > -- > > Christophe Prud'homme | > > MIT, 77, Mass Ave, Rm 3-243 | C'est de la buche? > > Cambridge MA 02139 | Non c'est kloug! > > Tel (Office) : (00 1) (617) 253 0229 | C'est colmatté avec du schpountz... > > Fax (Office) : (00 1) (617) 258 8559 | -- Le Pere Noel est une ordure > > http://augustine.mit.edu/~prudhomm | > > Following the hacker spirit > > -- 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 |
|
From: Christophe Prud'h. <pru...@MI...> - 2000-09-15 14:00:09
|
I can do the rpm-doc also C. -- Christophe Prud'homme | MIT, 77, Mass Ave, Rm 3-243 | He that breaks a thing to find out Cambridge MA 02139 | what it is has left the path of wisdom. Tel (Office) : (00 1) (617) 253 0229 | -- J.R.R. Tolkien Fax (Office) : (00 1) (617) 258 8559 | http://augustine.mit.edu/~prudhomm | Following the hacker spirit |
|
From: Frank V. C. <fr...@co...> - 2000-09-15 10:38:48
|
Christophe Prud'homme wrote: > > On Thu, 14 Sep 2000, you wrote: > > Hans, > > > > No prob with the debian or rpm builds. As I said, I am willing to just post > > tar.gz and the rpm base and dev packages for the short-term. But, we > > obviously are on the spot with docs and debian. > no problem with package creation for me > but that will be all I can do > since it is automatic it won't take much time I appreciate you offering that, and I will let you know when we are ready (although I am sure you see the message between Hans and I for the meantime in this list). Hans, Could you run: ./configure ./make rpm when you have a chance. I would like to know if you have the ability to create the rpm-docs. On my system I get a failure which prevents the generation of the ps and pdf files. I should take a closer look but I am swamped right now with new job prospects, interviews, etc. > > C. > -- > Christophe Prud'homme | > MIT, 77, Mass Ave, Rm 3-243 | C'est de la buche? > Cambridge MA 02139 | Non c'est kloug! > Tel (Office) : (00 1) (617) 253 0229 | C'est colmatté avec du schpountz... > Fax (Office) : (00 1) (617) 258 8559 | -- Le Pere Noel est une ordure > http://augustine.mit.edu/~prudhomm | > Following the hacker spirit -- Frank V. Castellucci http://corelinux.sourceforge.net OOA/OOD/C++ Standards and Guidelines for Linux http://PythPat.sourceforge.net Pythons Pattern Package |
|
From: Frank V. C. <fr...@co...> - 2000-09-15 03:24:20
|
Hans - Dulimarta wrote: > > On Thu, 14 Sep 2000, Frank V. Castellucci wrote: > > > Date: Thu, 14 Sep 2000 11:06:49 -0400 > > From: Frank V. Castellucci <fr...@co...> > > Reply-To: cor...@li... > > To: cor...@li... > > Subject: Re: [Corelinux-develop] just a word... > > > > Hans, > > > > No prob with the debian or rpm builds. As I said, I am willing to just post tar.gz > > and the rpm base and dev packages for the short-term. But, we obviously are on the > > spot with docs and debian. > > > > BTW: What distribution are you on? > > I am using RedHat. What about you? Same 6.1 and alternate between 2.2.12-20 and 2.2.14 > > > > > _______________________________________________ > > 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 |
|
From: Hans - D. <dul...@eg...> - 2000-09-15 02:58:46
|
On Thu, 14 Sep 2000, Frank V. Castellucci wrote: > Date: Thu, 14 Sep 2000 11:06:49 -0400 > From: Frank V. Castellucci <fr...@co...> > Reply-To: cor...@li... > To: cor...@li... > Subject: Re: [Corelinux-develop] just a word... > > Hans, > > No prob with the debian or rpm builds. As I said, I am willing to just post tar.gz > and the rpm base and dev packages for the short-term. But, we obviously are on the > spot with docs and debian. > > BTW: What distribution are you on? I am using RedHat. What about you? > > _______________________________________________ > 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 |
|
From: Christophe Prud'h. <pru...@MI...> - 2000-09-14 19:19:30
|
On Thu, 14 Sep 2000, you wrote: > Hans, > > No prob with the debian or rpm builds. As I said, I am willing to just post > tar.gz and the rpm base and dev packages for the short-term. But, we > obviously are on the spot with docs and debian. no problem with package creation for me but that will be all I can do since it is automatic it won't take much time C. -- Christophe Prud'homme | MIT, 77, Mass Ave, Rm 3-243 | C'est de la buche? Cambridge MA 02139 | Non c'est kloug! Tel (Office) : (00 1) (617) 253 0229 | C'est colmatté avec du schpountz... Fax (Office) : (00 1) (617) 258 8559 | -- Le Pere Noel est une ordure http://augustine.mit.edu/~prudhomm | Following the hacker spirit |
|
From: Frank V. C. <fr...@co...> - 2000-09-14 14:55:12
|
Hans, No prob with the debian or rpm builds. As I said, I am willing to just post tar.gz and the rpm base and dev packages for the short-term. But, we obviously are on the spot with docs and debian. BTW: What distribution are you on? Hans Dulimarta wrote: > "Frank V. Castellucci" wrote: > > > > Yes, now that you have us doing debian packages and pdf/dvi the scale > > that my machine can't handle, we are beholden to you to return so that > > we can package CoreLinux++. <grin> > > > > Seriously, once Han works out the wrinkles in EventSemaphore we are > > going to release at least the 0.4.28 tar ball and rpm and dev-rpm. I > > have no choices. (Unless Hans has no problems creating the debian and > > rpm-doc) > > > > Unfortunately, I never tried to build debian or rpm packages. > > > And yes, we miss you too. > > > > BTW: Just finished House Atreides (prequel to Dune), and I am impressed. > > > > Christophe Prud'homme wrote: > > > > > > just to say hello and that I miss working on corelinux > > > > > > I'll be back on work in 3~4 weeks (well I hope for the next release) > > > > > > C. > > > -- > > > Christophe Prud'homme | > > > MIT, 77, Mass Ave, Rm 3-243 | A wise person makes his own > > > Cambridge MA 02139 | decisions, > > > Tel (Office) : (00 1) (617) 253 0229 | a weak one obeys public opinion. > > > Fax (Office) : (00 1) (617) 258 8559 | -- Chinese proverb > > > http://augustine.mit.edu/~prudhomm | > > > Following the hacker spirit > > > _______________________________________________ > > > 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 > > _______________________________________________ > > 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 |
|
From: Hans D. <dul...@eg...> - 2000-09-14 14:15:07
|
"Frank V. Castellucci" wrote: > > Yes, now that you have us doing debian packages and pdf/dvi the scale > that my machine can't handle, we are beholden to you to return so that > we can package CoreLinux++. <grin> > > Seriously, once Han works out the wrinkles in EventSemaphore we are > going to release at least the 0.4.28 tar ball and rpm and dev-rpm. I > have no choices. (Unless Hans has no problems creating the debian and > rpm-doc) > Unfortunately, I never tried to build debian or rpm packages. > And yes, we miss you too. > > BTW: Just finished House Atreides (prequel to Dune), and I am impressed. > > Christophe Prud'homme wrote: > > > > just to say hello and that I miss working on corelinux > > > > I'll be back on work in 3~4 weeks (well I hope for the next release) > > > > C. > > -- > > Christophe Prud'homme | > > MIT, 77, Mass Ave, Rm 3-243 | A wise person makes his own > > Cambridge MA 02139 | decisions, > > Tel (Office) : (00 1) (617) 253 0229 | a weak one obeys public opinion. > > Fax (Office) : (00 1) (617) 258 8559 | -- Chinese proverb > > http://augustine.mit.edu/~prudhomm | > > Following the hacker spirit > > _______________________________________________ > > 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 > _______________________________________________ > 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 |
|
From: Frank V. C. <fr...@co...> - 2000-09-14 00:41:46
|
Yes, now that you have us doing debian packages and pdf/dvi the scale that my machine can't handle, we are beholden to you to return so that we can package CoreLinux++. <grin> Seriously, once Han works out the wrinkles in EventSemaphore we are going to release at least the 0.4.28 tar ball and rpm and dev-rpm. I have no choices. (Unless Hans has no problems creating the debian and rpm-doc) And yes, we miss you too. BTW: Just finished House Atreides (prequel to Dune), and I am impressed. Christophe Prud'homme wrote: > > just to say hello and that I miss working on corelinux > > I'll be back on work in 3~4 weeks (well I hope for the next release) > > C. > -- > Christophe Prud'homme | > MIT, 77, Mass Ave, Rm 3-243 | A wise person makes his own > Cambridge MA 02139 | decisions, > Tel (Office) : (00 1) (617) 253 0229 | a weak one obeys public opinion. > Fax (Office) : (00 1) (617) 258 8559 | -- Chinese proverb > http://augustine.mit.edu/~prudhomm | > Following the hacker spirit > _______________________________________________ > 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 |
|
From: Christophe Prud'h. <pru...@MI...> - 2000-09-13 23:24:08
|
just to say hello and that I miss working on corelinux I'll be back on work in 3~4 weeks (well I hope for the next release) C. -- Christophe Prud'homme | MIT, 77, Mass Ave, Rm 3-243 | A wise person makes his own Cambridge MA 02139 | decisions, Tel (Office) : (00 1) (617) 253 0229 | a weak one obeys public opinion. Fax (Office) : (00 1) (617) 258 8559 | -- Chinese proverb http://augustine.mit.edu/~prudhomm | Following the hacker spirit |
|
From: Hans D. <dul...@eg...> - 2000-09-11 05:18:00
|
"Frank V. Castellucci" wrote: > > Hans, > > You will no doubt be recieving a flurry of defects that I have found as > I tried the ex22 (which I added and should work according to reasonable > usage). > Yes.... this is what I need... really :-). I expect to receive this many "internal bug reports" because I did not test the code yet. But since I ask you to write the test suite, I had to check them in to the CVS. I'll fix them all. > The main defects have a higher priority than the standards issue > defects. > > We can work these out once I get them all in SourceForge. > > Release that when the ex22 bombs out or hangs, there is some work needed > to clean up the environment: > > 1. ipcs will show you the semaphore groups to be destroyed with ipcrm > sem XXXX > 2. in /tmp there are clsgtmp (I believe is the prefix) which should be > removed. > > then you can run again :) > > -- > 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 |
|
From: Frank V. C. <fr...@co...> - 2000-09-10 04:43:53
|
PS: I have checked all examples and changes into CVS. "Frank V. Castellucci" wrote: > > Hans, > > You will no doubt be recieving a flurry of defects that I have found as > I tried the ex22 (which I added and should work according to reasonable > usage). > > The main defects have a higher priority than the standards issue > defects. > > We can work these out once I get them all in SourceForge. > > Release that when the ex22 bombs out or hangs, there is some work needed > to clean up the environment: > > 1. ipcs will show you the semaphore groups to be destroyed with ipcrm > sem XXXX > 2. in /tmp there are clsgtmp (I believe is the prefix) which should be > removed. > > then you can run again :) > > -- > 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 -- Frank V. Castellucci http://corelinux.sourceforge.net OOA/OOD/C++ Standards and Guidelines for Linux http://PythPat.sourceforge.net Pythons Pattern Package |
|
From: Frank V. C. <fr...@co...> - 2000-09-10 04:43:30
|
Hans - Dulimarta wrote: > > On Sat, 9 Sep 2000, Frank V. Castellucci wrote: > > > Date: Sat, 09 Sep 2000 23:15:14 -0400 > > From: Frank V. Castellucci <fr...@co...> > > Reply-To: cor...@li... > > To: cor...@li... > > Subject: Re: [Corelinux-develop] ChangeLog and Feature/Defect fixes > > > > Hans - Dulimarta wrote: > > > > > > On Sat, 9 Sep 2000, Frank V. Castellucci wrote: > > > > > > > Date: Sat, 09 Sep 2000 18:33:18 -0400 > > > > From: Frank V. Castellucci <fr...@co...> > > > > Reply-To: cor...@li... > > > > To: cor...@li... > > > > Subject: Re: [Corelinux-develop] ChangeLog and Feature/Defect fixes > > > > > > > > Ok, couple of things: > > > > > > > > 1. I change the listener counters in EventSemaphore to type Counter > > > > (which is signed) from Count (which is unsigned). > > > > > > I did not know we have both Count and Counter. > > > > Yes, the compiler was warning that the comparison of Count always > > results in true because >= 0 > > Which compiler are you using? My egcs-1.1.2 did not give me this warning > message. ./configure --with-cxx=g++ which is g++ 2.95.2 (it forces the -Wall flag) > > > > > > > > > 2. I wrapped the include <sys/sem.h> in extern "C" > > > > > > > > So the code looks good there, but, question, and if you already answered > > > > this I'm sorry: > > > > > > > > Given the scenario where I have two listeners and (obviously) one > > > > controller > > > > > > > > 1. The controller creates the semaphore and it is locked > > > > 2. The listeners come in and block on the wait (wait(0)) > > > > 3. The controller releases the semaphore > > > > 4. The listeners, in a tight loop, come right back in and try to block > > > > again > > > > > > > > Because the controller has released but not regained the control (-1), > > > > this will mean that the listeners will behave as though they got another > > > > event, while in actuality they haven't, correct? > > > > > > > > > > You are correct. > > > > > > What respond should the listener get when it try to block on unlock > > > semaphore. > > > > Yes, this is not an easy answer. My first thought is to keep a queue > > state indicators which increased for each thread entering a blocked > > state, and decrements it for each one going out, zero resulting in a > > state indication that all waiting threads have been serviced. > > > > The last one out (last listener that causes zero state indicator) closes > > the door (sets semaphore value to (-1) again). > > > > The use of monitors around this activity will insure that the queue > > state indiciators are kept properly. > > > > That way, attempts to come back in and listen before all threads have > > been serviced can return UNAVAILABLE until which point you block. > > > > Thoughts? > > > > POSIX semaphores have queues somewhere in their implementation. I guess we > can take advantage of this and don't have to provide our own queue. Except we can't/won't be using the posix threads or semaphores. Otherwise we would be doing this work :). > > The 'theNumListeners' data member, I guess, resembles the "queue state > indicator" you mentioned above. When a listener is being block, it will > stay inside "waitZero()". So, the last listeners being freed from > waitZero() can be identified by decrementing theNumListeners after > returning waitZero(). Well, it will take more state indicators than just theNumListeners. > > > > > > > > > > > > Hans - Dulimarta wrote: > > > > > > > > > > On Sat, 9 Sep 2000, Frank V. Castellucci wrote: > > > > > > > > > > > Date: Sat, 09 Sep 2000 07:56:55 -0400 > > > > > > From: Frank V. Castellucci <fr...@co...> > > > > > > Reply-To: cor...@li... > > > > > > To: CoreLinux Development <cor...@li...> > > > > > > Subject: [Corelinux-develop] ChangeLog and Feature/Defect fixes > > > > > > > > > > > > I have started marking defects/features "Closed" with appropriate > > > > > > resolution as they are handled. I am keeping ChangeLog up-to-date on a > > > > > > regular basis. > > > > > > > > > > > > This will reduce the amount of work required at release time, which has > > > > > > grown exponentially between packages and the SourceForge changes (ugh). > > > > > > > > > > > > > > > > I have checked in EventSemaphore and EventSemaphoreGroup, but not the test > > > > > suite. Frank, I need your help to write an example/test code. > > > > > > > > > > Also, I fixed the bug 113103 by declaring the struct semun when > > > > > _SEM_SEMUN_UNDEFINED_ is defined. I have tested using egcs-1.1.2 on my > > > > > RedHat 6.2. The bug submitter compiled the code under Debian 2.1. I hope > > > > > it does not make any difference. > > > > > > > > > > -- > > > > > 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 > > > > > > > > > > > > > > -- > > > 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 > > > > > > -- > 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 |
|
From: Frank V. C. <fr...@co...> - 2000-09-10 04:40:40
|
Hans, You will no doubt be recieving a flurry of defects that I have found as I tried the ex22 (which I added and should work according to reasonable usage). The main defects have a higher priority than the standards issue defects. We can work these out once I get them all in SourceForge. Release that when the ex22 bombs out or hangs, there is some work needed to clean up the environment: 1. ipcs will show you the semaphore groups to be destroyed with ipcrm sem XXXX 2. in /tmp there are clsgtmp (I believe is the prefix) which should be removed. then you can run again :) -- Frank V. Castellucci http://corelinux.sourceforge.net OOA/OOD/C++ Standards and Guidelines for Linux http://PythPat.sourceforge.net Pythons Pattern Package |
|
From: Hans - D. <dul...@eg...> - 2000-09-10 04:39:22
|
On Sat, 9 Sep 2000, Frank V. Castellucci wrote: > Date: Sat, 09 Sep 2000 23:15:14 -0400 > From: Frank V. Castellucci <fr...@co...> > Reply-To: cor...@li... > To: cor...@li... > Subject: Re: [Corelinux-develop] ChangeLog and Feature/Defect fixes > > Hans - Dulimarta wrote: > > > > On Sat, 9 Sep 2000, Frank V. Castellucci wrote: > > > > > Date: Sat, 09 Sep 2000 18:33:18 -0400 > > > From: Frank V. Castellucci <fr...@co...> > > > Reply-To: cor...@li... > > > To: cor...@li... > > > Subject: Re: [Corelinux-develop] ChangeLog and Feature/Defect fixes > > > > > > Ok, couple of things: > > > > > > 1. I change the listener counters in EventSemaphore to type Counter > > > (which is signed) from Count (which is unsigned). > > > > I did not know we have both Count and Counter. > > Yes, the compiler was warning that the comparison of Count always > results in true because >= 0 Which compiler are you using? My egcs-1.1.2 did not give me this warning message. > > > > > > 2. I wrapped the include <sys/sem.h> in extern "C" > > > > > > So the code looks good there, but, question, and if you already answered > > > this I'm sorry: > > > > > > Given the scenario where I have two listeners and (obviously) one > > > controller > > > > > > 1. The controller creates the semaphore and it is locked > > > 2. The listeners come in and block on the wait (wait(0)) > > > 3. The controller releases the semaphore > > > 4. The listeners, in a tight loop, come right back in and try to block > > > again > > > > > > Because the controller has released but not regained the control (-1), > > > this will mean that the listeners will behave as though they got another > > > event, while in actuality they haven't, correct? > > > > > > > You are correct. > > > > What respond should the listener get when it try to block on unlock > > semaphore. > > Yes, this is not an easy answer. My first thought is to keep a queue > state indicators which increased for each thread entering a blocked > state, and decrements it for each one going out, zero resulting in a > state indication that all waiting threads have been serviced. > > The last one out (last listener that causes zero state indicator) closes > the door (sets semaphore value to (-1) again). > > The use of monitors around this activity will insure that the queue > state indiciators are kept properly. > > That way, attempts to come back in and listen before all threads have > been serviced can return UNAVAILABLE until which point you block. > > Thoughts? > POSIX semaphores have queues somewhere in their implementation. I guess we can take advantage of this and don't have to provide our own queue. The 'theNumListeners' data member, I guess, resembles the "queue state indicator" you mentioned above. When a listener is being block, it will stay inside "waitZero()". So, the last listeners being freed from waitZero() can be identified by decrementing theNumListeners after returning waitZero(). > > > > > > > > Hans - Dulimarta wrote: > > > > > > > > On Sat, 9 Sep 2000, Frank V. Castellucci wrote: > > > > > > > > > Date: Sat, 09 Sep 2000 07:56:55 -0400 > > > > > From: Frank V. Castellucci <fr...@co...> > > > > > Reply-To: cor...@li... > > > > > To: CoreLinux Development <cor...@li...> > > > > > Subject: [Corelinux-develop] ChangeLog and Feature/Defect fixes > > > > > > > > > > I have started marking defects/features "Closed" with appropriate > > > > > resolution as they are handled. I am keeping ChangeLog up-to-date on a > > > > > regular basis. > > > > > > > > > > This will reduce the amount of work required at release time, which has > > > > > grown exponentially between packages and the SourceForge changes (ugh). > > > > > > > > > > > > > I have checked in EventSemaphore and EventSemaphoreGroup, but not the test > > > > suite. Frank, I need your help to write an example/test code. > > > > > > > > Also, I fixed the bug 113103 by declaring the struct semun when > > > > _SEM_SEMUN_UNDEFINED_ is defined. I have tested using egcs-1.1.2 on my > > > > RedHat 6.2. The bug submitter compiled the code under Debian 2.1. I hope > > > > it does not make any difference. > > > > > > > > -- > > > > 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 > > > > > > > > > > -- > > 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 > > -- 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 |
|
From: Frank V. C. <fr...@co...> - 2000-09-10 03:12:28
|
Hans - Dulimarta wrote: > > On Sat, 9 Sep 2000, Frank V. Castellucci wrote: > > > Date: Sat, 09 Sep 2000 18:33:18 -0400 > > From: Frank V. Castellucci <fr...@co...> > > Reply-To: cor...@li... > > To: cor...@li... > > Subject: Re: [Corelinux-develop] ChangeLog and Feature/Defect fixes > > > > Ok, couple of things: > > > > 1. I change the listener counters in EventSemaphore to type Counter > > (which is signed) from Count (which is unsigned). > > I did not know we have both Count and Counter. Yes, the compiler was warning that the comparison of Count always results in true because >= 0 > > > 2. I wrapped the include <sys/sem.h> in extern "C" > > > > So the code looks good there, but, question, and if you already answered > > this I'm sorry: > > > > Given the scenario where I have two listeners and (obviously) one > > controller > > > > 1. The controller creates the semaphore and it is locked > > 2. The listeners come in and block on the wait (wait(0)) > > 3. The controller releases the semaphore > > 4. The listeners, in a tight loop, come right back in and try to block > > again > > > > Because the controller has released but not regained the control (-1), > > this will mean that the listeners will behave as though they got another > > event, while in actuality they haven't, correct? > > > > You are correct. > > What respond should the listener get when it try to block on unlock > semaphore. Yes, this is not an easy answer. My first thought is to keep a queue state indicators which increased for each thread entering a blocked state, and decrements it for each one going out, zero resulting in a state indication that all waiting threads have been serviced. The last one out (last listener that causes zero state indicator) closes the door (sets semaphore value to (-1) again). The use of monitors around this activity will insure that the queue state indiciators are kept properly. That way, attempts to come back in and listen before all threads have been serviced can return UNAVAILABLE until which point you block. Thoughts? > > > > > Hans - Dulimarta wrote: > > > > > > On Sat, 9 Sep 2000, Frank V. Castellucci wrote: > > > > > > > Date: Sat, 09 Sep 2000 07:56:55 -0400 > > > > From: Frank V. Castellucci <fr...@co...> > > > > Reply-To: cor...@li... > > > > To: CoreLinux Development <cor...@li...> > > > > Subject: [Corelinux-develop] ChangeLog and Feature/Defect fixes > > > > > > > > I have started marking defects/features "Closed" with appropriate > > > > resolution as they are handled. I am keeping ChangeLog up-to-date on a > > > > regular basis. > > > > > > > > This will reduce the amount of work required at release time, which has > > > > grown exponentially between packages and the SourceForge changes (ugh). > > > > > > > > > > I have checked in EventSemaphore and EventSemaphoreGroup, but not the test > > > suite. Frank, I need your help to write an example/test code. > > > > > > Also, I fixed the bug 113103 by declaring the struct semun when > > > _SEM_SEMUN_UNDEFINED_ is defined. I have tested using egcs-1.1.2 on my > > > RedHat 6.2. The bug submitter compiled the code under Debian 2.1. I hope > > > it does not make any difference. > > > > > > -- > > > 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 > > > > > > -- > 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 |
|
From: Hans - D. <dul...@eg...> - 2000-09-10 01:47:04
|
On Sat, 9 Sep 2000, Frank V. Castellucci wrote: > Date: Sat, 09 Sep 2000 18:33:18 -0400 > From: Frank V. Castellucci <fr...@co...> > Reply-To: cor...@li... > To: cor...@li... > Subject: Re: [Corelinux-develop] ChangeLog and Feature/Defect fixes > > Ok, couple of things: > > 1. I change the listener counters in EventSemaphore to type Counter > (which is signed) from Count (which is unsigned). I did not know we have both Count and Counter. > 2. I wrapped the include <sys/sem.h> in extern "C" > > So the code looks good there, but, question, and if you already answered > this I'm sorry: > > Given the scenario where I have two listeners and (obviously) one > controller > > 1. The controller creates the semaphore and it is locked > 2. The listeners come in and block on the wait (wait(0)) > 3. The controller releases the semaphore > 4. The listeners, in a tight loop, come right back in and try to block > again > > Because the controller has released but not regained the control (-1), > this will mean that the listeners will behave as though they got another > event, while in actuality they haven't, correct? > You are correct. What respond should the listener get when it try to block on unlock semaphore. > > Hans - Dulimarta wrote: > > > > On Sat, 9 Sep 2000, Frank V. Castellucci wrote: > > > > > Date: Sat, 09 Sep 2000 07:56:55 -0400 > > > From: Frank V. Castellucci <fr...@co...> > > > Reply-To: cor...@li... > > > To: CoreLinux Development <cor...@li...> > > > Subject: [Corelinux-develop] ChangeLog and Feature/Defect fixes > > > > > > I have started marking defects/features "Closed" with appropriate > > > resolution as they are handled. I am keeping ChangeLog up-to-date on a > > > regular basis. > > > > > > This will reduce the amount of work required at release time, which has > > > grown exponentially between packages and the SourceForge changes (ugh). > > > > > > > I have checked in EventSemaphore and EventSemaphoreGroup, but not the test > > suite. Frank, I need your help to write an example/test code. > > > > Also, I fixed the bug 113103 by declaring the struct semun when > > _SEM_SEMUN_UNDEFINED_ is defined. I have tested using egcs-1.1.2 on my > > RedHat 6.2. The bug submitter compiled the code under Debian 2.1. I hope > > it does not make any difference. > > > > -- > > 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 > > -- 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 |
|
From: Hans - D. <dul...@eg...> - 2000-09-10 01:19:04
|
On Sat, 9 Sep 2000, Frank V. Castellucci wrote: > Date: Sat, 09 Sep 2000 17:36:42 -0400 > From: Frank V. Castellucci <fr...@co...> > Reply-To: cor...@li... > To: cor...@li... > Subject: Re: [Corelinux-develop] ChangeLog and Feature/Defect fixes > > Hans - Dulimarta wrote: > > > > On Sat, 9 Sep 2000, Frank V. Castellucci wrote: > > > > > Date: Sat, 09 Sep 2000 07:56:55 -0400 > > > From: Frank V. Castellucci <fr...@co...> > > > Reply-To: cor...@li... > > > To: CoreLinux Development <cor...@li...> > > > Subject: [Corelinux-develop] ChangeLog and Feature/Defect fixes > > > > > > I have started marking defects/features "Closed" with appropriate > > > resolution as they are handled. I am keeping ChangeLog up-to-date on a > > > regular basis. > > > > > > This will reduce the amount of work required at release time, which has > > > grown exponentially between packages and the SourceForge changes (ugh). > > > > > > > I have checked in EventSemaphore and EventSemaphoreGroup, but not the test > > suite. Frank, I need your help to write an example/test code. > > Ok, I'll be writing ex22 (examp22) for this. Thanks. > > > > > Also, I fixed the bug 113103 by declaring the struct semun when > > _SEM_SEMUN_UNDEFINED_ is defined. I have tested using egcs-1.1.2 on my > > RedHat 6.2. The bug submitter compiled the code under Debian 2.1. I hope > > it does not make any difference. > > that's the one the headers say you have to define youself? Correct. > > > > > -- > > 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 > > -- 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 |
|
From: Frank V. C. <fr...@co...> - 2000-09-09 22:30:28
|
Ok, couple of things: 1. I change the listener counters in EventSemaphore to type Counter (which is signed) from Count (which is unsigned). 2. I wrapped the include <sys/sem.h> in extern "C" So the code looks good there, but, question, and if you already answered this I'm sorry: Given the scenario where I have two listeners and (obviously) one controller 1. The controller creates the semaphore and it is locked 2. The listeners come in and block on the wait (wait(0)) 3. The controller releases the semaphore 4. The listeners, in a tight loop, come right back in and try to block again Because the controller has released but not regained the control (-1), this will mean that the listeners will behave as though they got another event, while in actuality they haven't, correct? Hans - Dulimarta wrote: > > On Sat, 9 Sep 2000, Frank V. Castellucci wrote: > > > Date: Sat, 09 Sep 2000 07:56:55 -0400 > > From: Frank V. Castellucci <fr...@co...> > > Reply-To: cor...@li... > > To: CoreLinux Development <cor...@li...> > > Subject: [Corelinux-develop] ChangeLog and Feature/Defect fixes > > > > I have started marking defects/features "Closed" with appropriate > > resolution as they are handled. I am keeping ChangeLog up-to-date on a > > regular basis. > > > > This will reduce the amount of work required at release time, which has > > grown exponentially between packages and the SourceForge changes (ugh). > > > > I have checked in EventSemaphore and EventSemaphoreGroup, but not the test > suite. Frank, I need your help to write an example/test code. > > Also, I fixed the bug 113103 by declaring the struct semun when > _SEM_SEMUN_UNDEFINED_ is defined. I have tested using egcs-1.1.2 on my > RedHat 6.2. The bug submitter compiled the code under Debian 2.1. I hope > it does not make any difference. > > -- > 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 |
|
From: Frank V. C. <fr...@co...> - 2000-09-09 21:33:54
|
Hans - Dulimarta wrote: > > On Sat, 9 Sep 2000, Frank V. Castellucci wrote: > > > Date: Sat, 09 Sep 2000 07:56:55 -0400 > > From: Frank V. Castellucci <fr...@co...> > > Reply-To: cor...@li... > > To: CoreLinux Development <cor...@li...> > > Subject: [Corelinux-develop] ChangeLog and Feature/Defect fixes > > > > I have started marking defects/features "Closed" with appropriate > > resolution as they are handled. I am keeping ChangeLog up-to-date on a > > regular basis. > > > > This will reduce the amount of work required at release time, which has > > grown exponentially between packages and the SourceForge changes (ugh). > > > > I have checked in EventSemaphore and EventSemaphoreGroup, but not the test > suite. Frank, I need your help to write an example/test code. Ok, I'll be writing ex22 (examp22) for this. > > Also, I fixed the bug 113103 by declaring the struct semun when > _SEM_SEMUN_UNDEFINED_ is defined. I have tested using egcs-1.1.2 on my > RedHat 6.2. The bug submitter compiled the code under Debian 2.1. I hope > it does not make any difference. that's the one the headers say you have to define youself? > > -- > 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 |
|
From: Hans - D. <dul...@eg...> - 2000-09-09 17:15:39
|
On Sat, 9 Sep 2000, Frank V. Castellucci wrote: > Date: Sat, 09 Sep 2000 07:56:55 -0400 > From: Frank V. Castellucci <fr...@co...> > Reply-To: cor...@li... > To: CoreLinux Development <cor...@li...> > Subject: [Corelinux-develop] ChangeLog and Feature/Defect fixes > > I have started marking defects/features "Closed" with appropriate > resolution as they are handled. I am keeping ChangeLog up-to-date on a > regular basis. > > This will reduce the amount of work required at release time, which has > grown exponentially between packages and the SourceForge changes (ugh). > I have checked in EventSemaphore and EventSemaphoreGroup, but not the test suite. Frank, I need your help to write an example/test code. Also, I fixed the bug 113103 by declaring the struct semun when _SEM_SEMUN_UNDEFINED_ is defined. I have tested using egcs-1.1.2 on my RedHat 6.2. The bug submitter compiled the code under Debian 2.1. I hope it does not make any difference. -- 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 |
|
From: Frank V. C. <fr...@co...> - 2000-09-09 11:54:07
|
I have started marking defects/features "Closed" with appropriate resolution as they are handled. I am keeping ChangeLog up-to-date on a regular basis. This will reduce the amount of work required at release time, which has grown exponentially between packages and the SourceForge changes (ugh). -- Frank V. Castellucci |
|
From: Frank V. C. <fr...@co...> - 2000-09-07 00:50:37
|
Christophe Prud'homme wrote: > > ---------- Forwarded Message ---------- > Subject: Comments and question on the corelinux++ coding standards > Date: Tue, 5 Sep 2000 14:52:48 +0100 (GMT+01:00) > From: Robert Marshall <ra...@fs...> > To: pru...@us... > > I've used this document as a basis for designing our own standards (thanks > very much). I hope you don't mind if I ask some questions and make a few > comments on that document. > > - standard 1 referes to the Venice coding standards. Is this a publically > available document? I couldn't find any references to it on the internet. - Man, this is what happens when I take the dust off of things that were new back then :). I will have to find something more timeless. > Guideline 16 is really a rationale for the previous standard (33) rather > than a guideline in itself. Guideline 16 is a typo, should be Rationale > > - the formatting of the html makes the examples in standards 34-36 > meaningless. Agree > - Standard 60 and guideline 40 seem to be in conflict These are some of the compromises made from other feedback. Basically it is saying "avoid it as people may turn of RTTI", but at the same time if working around it means crap code, then use it. > - standard 67, I'd add the words `and unimplemented' to the second sentence > for clarity. Umm, we still would "implement" them even if they are private. We do not want the compiler defaults to take over. > - the reference to sourceware.cygnus.com is dated with the > takeover by redhat. Again couldn't find the template standards being > referred to here, if you could point me in the right direction I'd be very > grateful! Agreed. will have to track it down. > - Have grave doubts about standard 114 with the current state of > exception specification support. But getting better all the time! This is also a compiler vendor issue, as we are mapping to the standard. > I'm curious that namespace and template > mention is very scant but there's this reference. - The bibliography appears > to reference itself (I suppose though it tells you where to get the > original) - I'm looking at developing standards for the use of the STL do > you know of any existing guidelines for this. - the comments to webmaster at > the foot of the page refers to sourcefforge. (apologies if this was a > deliberate spam beater) - miscellaneous typographical errors. Typo, as _at_ foils the agents. > > Thanks for reading this far! > > Robert > > _______________________________________________________________________ > FSmail - Get your free web-based email from Freeserve: www.fsmail.net > > ------------------------------------------------------- > > -- > Christophe Prud'homme | > MIT, 77, Mass Ave, Rm 3-243 | If it doesn't work, force it. > Cambridge MA 02139 | If it breaks, it needed > Tel (Office) : (00 1) (617) 253 0229 | replacing anyway. > Fax (Office) : (00 1) (617) 258 8559 | > http://augustine.mit.edu/~prudhomm | > Following the hacker spirit > _______________________________________________ > 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 |
|
From: Frank V. C. <fr...@co...> - 2000-09-06 23:48:16
|
I believe you have the sense of it.
A general UML of the abstraction is:
Ontology <>----> MetaClass <>----->MetaAttributes <>--|
^ |
| |
-------------------------------
So an Onotlogy has MetaClasses
MetaClasses are defined MetaAttributes
MetaAttributes are constrained (restricted) by MetaClasses
So, in psuedo-think :)
MetaClass
declares TypeOf MetaClass
declares Name String
declares ClassType Entity
declares Description String
Going along this line, and instance model could be
MetaTypeRoot
defines TypeOf {0}
defines Name "MetaTypeRoot"
defines Description "Root of the ontology"
MetaTypeNumber
defines TypeOf {MetaTypeRoot}
defines Name "MetaTypeNumber"
defines ClassType Number
defines Description "Number Type"
MetaTypeInteger
defines TypeOf {MetaTypeNumber}
defines Name "MetaTypeInteger"
defines ClassType Integer
etc.
Which would map to:
class Entity;
class Number : public Entity;
class Integer : public Number;
of course at some point in the MetaType hierarchy you determine when to
add attributes which, in effect, specialize it from it's parent(s).
Christophe Prud'homme wrote:
>
> Hie
> my understanding of the requirements for meta class is that
> it provides :
> 1- traits: static features of a type (traits were originally defined by
> Nathan Meyers)
> 2- more sophisticated RTTI
>
> it my codes I have, I think, something like that for point 2
> all objects are clearly defined within a hierarchy of class and each of them
> defines isTypeOf(char*), getClassName() , isA(char*) and the parent,child is
> defined.
>
> for point 1 traits are a very powerful and simple technique to store static
> features and I use them very often.
>
> here is a simple example
>
> template<int Dim, int charSize=8, typename T=double>
> class traits
> {
> public:
> enum { dimension = Dim };
> enum { char_size = charSize };
> typedef T T_numtype;
> };
>
> template<typename Traits>
> class A
> {
> public:
> enum { dimension = Traits::dimension };
> enum { char_size = Traits::char_size };
> typedef typename Traits::T_numtype T_numtype;
> };
>
> template<int Dim>
> class B: public A<traits<Dim> >
> {
> public:
> typedef A<Traits<Dim> > super;
> enum { dimension = super::dimension };
> enum { char_size = super::char_size };
> typedef typename super::T_numtype T_numtype;
> };
>
>
> am I correct in that it is providing 1 and 2 ?
> C.
>
> --
> Christophe Prud'homme |
> MIT, 77, Mass Ave, Rm 3-243 | C'est de la buche?
> Cambridge MA 02139 | Non c'est kloug!
> Tel (Office) : (00 1) (617) 253 0229 | C'est colmatté avec du schpountz...
> Fax (Office) : (00 1) (617) 258 8559 | -- Le Pere Noel est une ordure
> http://augustine.mit.edu/~prudhomm |
> Following the hacker spirit
> _______________________________________________
> 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
|
1115 messages has been excluded from this view by a project administrator.
