corelinux-develop — Developer centric mail list for CoreLinux++

[Corelinux-develop] problem in CoreLinuxGuardPool

[Christophe Prud'h. <pru...@MI...>]

Hi all

I have a problem in CoreLinuxGuardPool
I don't use semaphores in the current code but since there are lots
of static initialisation occuring in this class, the program goes through them

the program crashes immediately!
The thing is that it used to work without any problem except that the program 
was crashing at the end of the execution. 
Would it be possible that some cleanup in the static variable may not have 
occured and after a while the system is unstable ? (corelinux + linux)

any ideas where I should look ?


note that the code is encapsulated in a try/catch 

here is the backtrace in gdb



Program received signal SIGABRT, Aborted.
0x4013e931 in kill () from /lib/libc.so.6
(gdb) bt
#0  0x4013e931 in kill () from /lib/libc.so.6
#1  0x4013e618 in raise () from /lib/libc.so.6
#2  0x4013fc71 in abort () from /lib/libc.so.6
#3  0x400e1f58 in __terminate () from /usr/lib/libstdc++-libc6.1-2.so.3
#4  0x400e2ebd in terminate () from /usr/lib/libstdc++-libc6.1-2.so.3
#5  0x400e2ed8 in set_terminate () from /usr/lib/libstdc++-libc6.1-2.so.3
#6  0x400e2f3b in unexpected () from /usr/lib/libstdc++-libc6.1-2.so.3
#7  0x400e31f0 in __check_eh_spec () from /usr/lib/libstdc++-libc6.1-2.so.3
#8  0x4008b9f9 in corelinux::CoreLinuxGuardPool::CoreLinuxGuardPool ()
   from /usr/lib/libcl++.so.0
#9  0x4008d19c in corelinux::CoreLinuxGuardPool::destroyPoolGroup ()
   from /usr/lib/libcl++.so.0
#10 0x4008d33e in corelinux::CoreLinuxGuardPool::destroyPoolGroup ()
   from /usr/lib/libcl++.so.0
#11 0x400a13d7 in __pure_virtual () from /usr/lib/libcl++.so.0
#12 0x40085026 in _init () from /usr/lib/libcl++.so.0                   

Re: [Corelinux-develop] xml and zipped formats

[Christophe Prud'h. <pru...@MI...>]

> Christophe, once you update the MagicDraw uml you will see that they
should i get it from No magic web site

> support XMI (XML UML interchange dtd), as well as reading and writing to
> a nice tidy little zip file!
Ok why not

> you guys think about us agreeing that new models are in *.xml.zip
> format?
are you not living around NY?
I thought that DSL would be first installed in such an area :)

Re: [Corelinux-develop] xml and zipped formats

[Hans D. <dul...@eg...>]

"Frank V. Castellucci" wrote:
> 
> Ok,
> 
> Christophe, once you update the MagicDraw uml you will see that they
> support XMI (XML UML interchange dtd), as well as reading and writing to
> a nice tidy little zip file!
> 
> Hans and Christophe,
> 
> While I am not concerned with the SourceForge CVS space, as the models
> grow the check-in time becomes a bit much on my lowly 56kb modem. Yes,
> yes, I am waiting for DSL to come around (couple of months), but what do
> you guys think about us agreeing that new models are in *.xml.zip
> format?
> 

My MagicDraw 3.6 is up and running now.
I'll do "cvs co models" soon after this e-mail is sent.


> --
> 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...
Vis. Research Assoc.                 
http://www.egr.msu.edu/~dulimart   
Ph: 517-432-7589  Fax: 760-281-7691  
http://corelinux.sourceforge.net
Elec. & Comp. Engg., Michigan State University, East
Lansing, MI 48824

Re: [Corelinux-develop] xml and zipped formats

[Hans D. <dul...@eg...>]

"Frank V. Castellucci" wrote:
> 
> Ok,
> 
> Christophe, once you update the MagicDraw uml you will see that they
> support XMI (XML UML interchange dtd), as well as reading and writing to
> a nice tidy little zip file!
> 
> Hans and Christophe,
> 
> While I am not concerned with the SourceForge CVS space, as the models
> grow the check-in time becomes a bit much on my lowly 56kb modem. Yes,
> yes, I am waiting for DSL to come around (couple of months), but what do
> you guys think about us agreeing that new models are in *.xml.zip
> format?
> 

Personally, I prefer the CVS tree contains text files only. But, I guess
for this particular case, the XML files are "semi human-readable". So,
for the sake of speed, I agree on the xml.zip format.

> --
> 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...
Vis. Research Assoc.                  http://www.egr.msu.edu/~dulimart   
Ph: 517-432-7589  Fax: 760-281-7691   http://corelinux.sourceforge.net
Elec. & Comp. Engg., Michigan State University, East Lansing, MI 48824

[Corelinux-develop] xml and zipped formats

[Frank V. C. <fr...@co...>]

Ok,

Christophe, once you update the MagicDraw uml you will see that they
support XMI (XML UML interchange dtd), as well as reading and writing to
a nice tidy little zip file!

Hans and Christophe,

While I am not concerned with the SourceForge CVS space, as the models
grow the check-in time becomes a bit much on my lowly 56kb modem. Yes,
yes, I am waiting for DSL to come around (couple of months), but what do
you guys think about us agreeing that new models are in *.xml.zip
format?

-- 
Frank V. Castellucci
http://corelinux.sourceforge.net
OOA/OOD/C++ Standards and Guidelines for Linux
http://PythPat.sourceforge.net
Pythons Pattern Package

Re: [Corelinux-develop] Re: Symbol in UML diagrams

[Hans D. <dul...@eg...>]

"Frank V. Castellucci" wrote:
> 
> Hans,
> 
> Did you get my direct e-mail as to the location and setup of the tool?
> 
> PS: Christophe, I think you know where to go to get the same, oui?
> 


Yes, I did and I finished downloading. I tested the zip file
and 
found no error. I have not installed in though.


-- 
Hans Dulimarta, Ph.D.                           
dul...@co...
Vis. Research Assoc.                 
http://www.egr.msu.edu/~dulimart   
Ph: 517-432-7589  Fax: 760-281-7691  
http://corelinux.sourceforge.net
Elec. & Comp. Engg., Michigan State University, East
Lansing, MI 48824

Re: [Corelinux-develop] Re: Symbol in UML diagrams

[Frank V. C. <fr...@co...>]

Hans,

Did you get my direct e-mail as to the location and setup of the tool?

PS: Christophe, I think you know where to go to get the same, oui?

Hans Dulimarta wrote:
> 
> "Frank V. Castellucci" wrote:
> >
> > Hans Dulimarta wrote:
> > >
> > > "Frank V. Castellucci" wrote:
> > > >
> > > > Which diagrams and header files are you talking about?
> > > >
> > >
> > > Interface implentation has 'const', diagram does not have
> > > '@'
> > >    AbstractSemaphore::getGroupId
> > >    Synchronized::access
> > >
> > > My references are  htdoc/doc/design/*.png and
> > > corelinux/corelinux/*.hpp.
> > >
> > > I know the CVS tree has 'models' module but I do not have
> > > MagicDraw
> > > to open the files.
> >
> > Oops, ok I forget to tell you, my apologies.
> >
> > We have a six license contribution of MagicDrawUML, would you like a
> > copy?
> >
> 
> Yes, please. Are the model files more up-to-date than the *.png files?
> Should I refer to the model files as the base documents for
> implementation?
> 
> > Here is the thing, the newest version is 3.6 which has the ability to
> > store data in XML/XMI (which I was waiting for a very long time), but
> > the current models are in 3.51 (which 3.6 can read). I just want to make
> > sure that 3.6 can save 3.51 without corrupting the data.
> >
> 
> I assume that files within the 'models' module were generated using
> 3.51?
> > >
> > > > Hans Dulimarta wrote:
> > > > >
> > > > > --- "Frank V. Castellucci" <fr...@co...>
> > > > > wrote:
> > > > > > Of course, those marked as const member functions in
> > > > > > the diagram but not
> > > > > > declared as such in the header files being?
> > > > > >
> > > > >
> > > > > Being what? I don't understand your answer.
> > > > >
> > > > > >
> > > > > > Hans Dulimarta wrote:
> > > > > >
> > > > > > > I found a "non-standard" symbol in the UML class
> > > > > diagrams in
> > > > > > > the .PNG files.
> > > > > > > What is the meaning of "@" symbol? I thought it
> > > > > was used to
> > > > > > > denote "const member function", but then when I
> > > > > compared
> > > > > > > with other files, that's not the case. The class
> > > > > diagram
> > > > > > > shows the '@' symbol but the header file does
> > > > > not have the
> > > > > > > "const" attribute in the member function.
> > > > > > >
> > > > >
> >
> > --
> > Frank V. Castellucci
> >
> > _______________________________________________
> > Corelinux-develop mailing list
> > Cor...@li...
> > http://lists.sourceforge.net/mailman/listinfo/corelinux-develop
> 
> --
> Hans Dulimarta, Ph.D.                            dul...@co...
> Vis. Research Assoc.                  http://www.egr.msu.edu/~dulimart
> Ph: 517-432-7589  Fax: 760-281-7691   http://corelinux.sourceforge.net
> Elec. & Comp. Engg., Michigan State University, East 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

Re: [Corelinux-develop] Re: Symbol in UML diagrams

[Hans D. <dul...@eg...>]

"Frank V. Castellucci" wrote:
> 
> Hans Dulimarta wrote:
> >
> > "Frank V. Castellucci" wrote:
> > >
> > > Which diagrams and header files are you talking about?
> > >
> >
> > Interface implentation has 'const', diagram does not have
> > '@'
> >    AbstractSemaphore::getGroupId
> >    Synchronized::access
> >
> > My references are  htdoc/doc/design/*.png and
> > corelinux/corelinux/*.hpp.
> >
> > I know the CVS tree has 'models' module but I do not have
> > MagicDraw
> > to open the files.
> 
> Oops, ok I forget to tell you, my apologies.
> 
> We have a six license contribution of MagicDrawUML, would you like a
> copy?
> 

Yes, please. Are the model files more up-to-date than the *.png files?
Should I refer to the model files as the base documents for
implementation?

> Here is the thing, the newest version is 3.6 which has the ability to
> store data in XML/XMI (which I was waiting for a very long time), but
> the current models are in 3.51 (which 3.6 can read). I just want to make
> sure that 3.6 can save 3.51 without corrupting the data.
> 

I assume that files within the 'models' module were generated using
3.51?
> >
> > > Hans Dulimarta wrote:
> > > >
> > > > --- "Frank V. Castellucci" <fr...@co...>
> > > > wrote:
> > > > > Of course, those marked as const member functions in
> > > > > the diagram but not
> > > > > declared as such in the header files being?
> > > > >
> > > >
> > > > Being what? I don't understand your answer.
> > > >
> > > > >
> > > > > Hans Dulimarta wrote:
> > > > >
> > > > > > I found a "non-standard" symbol in the UML class
> > > > diagrams in
> > > > > > the .PNG files.
> > > > > > What is the meaning of "@" symbol? I thought it
> > > > was used to
> > > > > > denote "const member function", but then when I
> > > > compared
> > > > > > with other files, that's not the case. The class
> > > > diagram
> > > > > > shows the '@' symbol but the header file does
> > > > not have the
> > > > > > "const" attribute in the member function.
> > > > > >
> > > >
> 
> --
> Frank V. Castellucci
> 
> _______________________________________________
> Corelinux-develop mailing list
> Cor...@li...
> http://lists.sourceforge.net/mailman/listinfo/corelinux-develop

-- 
Hans Dulimarta, Ph.D.                            dul...@co...
Vis. Research Assoc.                  http://www.egr.msu.edu/~dulimart   
Ph: 517-432-7589  Fax: 760-281-7691   http://corelinux.sourceforge.net
Elec. & Comp. Engg., Michigan State University, East Lansing, MI 48824

Re: [Corelinux-develop] Re: Symbol in UML diagrams

[Frank V. C. <fr...@co...>]

Hans Dulimarta wrote:
> 
> "Frank V. Castellucci" wrote:
> >
> > Which diagrams and header files are you talking about?
> >
> 
> Interface implentation has 'const', diagram does not have
> '@'
>    AbstractSemaphore::getGroupId
>    Synchronized::access
> 
> My references are  htdoc/doc/design/*.png and
> corelinux/corelinux/*.hpp.
> 
> I know the CVS tree has 'models' module but I do not have
> MagicDraw
> to open the files.

Oops, ok I forget to tell you, my apologies.

We have a six license contribution of MagicDrawUML, would you like a
copy?

Here is the thing, the newest version is 3.6 which has the ability to
store data in XML/XMI (which I was waiting for a very long time), but
the current models are in 3.51 (which 3.6 can read). I just want to make
sure that 3.6 can save 3.51 without corrupting the data.

> 
> > Hans Dulimarta wrote:
> > >
> > > --- "Frank V. Castellucci" <fr...@co...>
> > > wrote:
> > > > Of course, those marked as const member functions in
> > > > the diagram but not
> > > > declared as such in the header files being?
> > > >
> > >
> > > Being what? I don't understand your answer.
> > >
> > > >
> > > > Hans Dulimarta wrote:
> > > >
> > > > > I found a "non-standard" symbol in the UML class
> > > diagrams in
> > > > > the .PNG files.
> > > > > What is the meaning of "@" symbol? I thought it
> > > was used to
> > > > > denote "const member function", but then when I
> > > compared
> > > > > with other files, that's not the case. The class
> > > diagram
> > > > > shows the '@' symbol but the header file does
> > > not have the
> > > > > "const" attribute in the member function.
> > > > >
> > >

-- 
Frank V. Castellucci

Re: [Corelinux-develop] Re: Symbol in UML diagrams

[Hans D. <dul...@eg...>]

"Frank V. Castellucci" wrote:
> 
> Which diagrams and header files are you talking about?
> 

Interface implentation has 'const', diagram does not have
'@'
   AbstractSemaphore::getGroupId
   Synchronized::access

My references are  htdoc/doc/design/*.png and
corelinux/corelinux/*.hpp.

I know the CVS tree has 'models' module but I do not have
MagicDraw
to open the files.

> Hans Dulimarta wrote:
> >
> > --- "Frank V. Castellucci" <fr...@co...>
> > wrote:
> > > Of course, those marked as const member functions in
> > > the diagram but not
> > > declared as such in the header files being?
> > >
> >
> > Being what? I don't understand your answer.
> >
> > >
> > > Hans Dulimarta wrote:
> > >
> > > > I found a "non-standard" symbol in the UML class
> > diagrams in
> > > > the .PNG files.
> > > > What is the meaning of "@" symbol? I thought it
> > was used to
> > > > denote "const member function", but then when I
> > compared
> > > > with other files, that's not the case. The class
> > diagram
> > > > shows the '@' symbol but the header file does
> > not have the
> > > > "const" attribute in the member function.
> > > >
> >
> > > --
> > > Frank V. Castellucci
> > >
> > > _______________________________________________
> > > Corelinux-develop mailing list
> > > Cor...@li...
> > >
> > http://lists.sourceforge.net/mailman/listinfo/corelinux-develop
> >
> > =====
> > Hans Dulimarta, Ph.D.                            dul...@co...
> > Vis. Research Assoc.                  http://www.egr.msu.edu/~dulimart
> > Ph: 517-432-7589  Fax: 760-281-7691   http://corelinux.sourceforge.net
> > Elec. & Comp. Engg., Michigan State University, East Lansing, MI 48824
> >
> > __________________________________________________
> > Do You Yahoo!?
> > Kick off your party with Yahoo! Invites.
> > http://invites.yahoo.com/
> >
> > _______________________________________________
> > 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...
Vis. Research Assoc.                 
http://www.egr.msu.edu/~dulimart   
Ph: 517-432-7589  Fax: 760-281-7691  
http://corelinux.sourceforge.net
Elec. & Comp. Engg., Michigan State University, East
Lansing, MI 48824

Re: [Corelinux-develop] Caution

[Frank V. C. <fr...@co...>]

Christophe Prud'homme wrote:
> 
>     Frank> In a brief ping, Christophe mentioned the KDE-2 mini-declaration idl capability.
> a really brief one
> I am very busy these days

:)

> [snip]
> 
>     Frank> Now, when we (CoreLinux++) publish OUR frameworks, it is extremely likely that we will
>     Frank> make heavy use of the Library Load mini-framework to facilitate the component
>     Frank> architecture. At this point, a parser for definition interchange is a likely
>     Frank> requirement. And IDL is clearly a very suitable fit specifically for
>     Frank> ExecutionObjectDefinitions, but just as clearly useless in any other type library
>     Frank> (images, etc.).
> I agree on that.
> I guess that you will not use the idl from CORBA but rather a smaller subset and specifically
> designed for the frameworks. If so I would like to work on that.

It may be good to consider a RDF, but we can start a thread on
frameworks as well to nail this down.

> Otherwise, IMO, the LibraryType should be a class type as you mentioned in an earlier mail.
> 
> as for the loader you specify 1..*, is it wise to be able to have multiple loader instances?
> shouldn't we use the singleton pattern to ensure uniqueness of the instance and make sure that libs
> are loaded once while keeping track of what is loaded?
> I don't know if it makes sense or not?

Actually the cardinality is 0..*, because I am allowed to have many
loaders concurrently active in the system. I might have a shared
function library loader, an image loader, a RDBMS loader, and a CORBA
loader active all at once. So the base Loader should NOT be a singleton
as it won't allow that many instantiations. 

-- 
Frank V. Castellucci

Re: [Corelinux-develop] Caution

[Christophe Prud'h. <pru...@MI...>]

    Frank> In a brief ping, Christophe mentioned the KDE-2 mini-declaration idl capability.
a really brief one
I am very busy these days

    Frank> The actual ExecutionObjects and respective definitions is in the solution space of the
    Frank> application domain. It is up to "them" to define what a ExecutionObjectDefinition IS,
    Frank> what it contains, and so on. It is impossible for us to do that for them, after all we
    Frank> don't know which libraries they will be using. Of course I will be providing an example
    Frank> that leverages the framework, but I won't be needing a parser or grammar for that.
yes

    Frank> Now, when we (CoreLinux++) publish OUR frameworks, it is extremely likely that we will
    Frank> make heavy use of the Library Load mini-framework to facilitate the component
    Frank> architecture. At this point, a parser for definition interchange is a likely
    Frank> requirement. And IDL is clearly a very suitable fit specifically for
    Frank> ExecutionObjectDefinitions, but just as clearly useless in any other type library
    Frank> (images, etc.).
I agree on that.
I guess that you will not use the idl from CORBA but rather a smaller subset and specifically
designed for the frameworks. If so I would like to work on that.

Otherwise, IMO, the LibraryType should be a class type as you mentioned in an earlier mail.

as for the loader you specify 1..*, is it wise to be able to have multiple loader instances?
shouldn't we use the singleton pattern to ensure uniqueness of the instance and make sure that libs
are loaded once while keeping track of what is loaded?
I don't know if it makes sense or not?

regards and good night
C.

Re: [Corelinux-develop] Re: Symbol in UML diagrams

[Frank V. C. <fr...@co...>]

Which diagrams and header files are you talking about? 

Hans Dulimarta wrote:
> 
> --- "Frank V. Castellucci" <fr...@co...>
> wrote:
> > Of course, those marked as const member functions in
> > the diagram but not
> > declared as such in the header files being?
> >
> 
> Being what? I don't understand your answer.
> 
> >
> > Hans Dulimarta wrote:
> >
> > > I found a "non-standard" symbol in the UML class
> diagrams in
> > > the .PNG files.
> > > What is the meaning of "@" symbol? I thought it
> was used to
> > > denote "const member function", but then when I
> compared
> > > with other files, that's not the case. The class
> diagram
> > > shows the '@' symbol but the header file does
> not have the
> > > "const" attribute in the member function.
> > >
> 
> > --
> > Frank V. Castellucci
> >
> > _______________________________________________
> > Corelinux-develop mailing list
> > Cor...@li...
> >
> http://lists.sourceforge.net/mailman/listinfo/corelinux-develop
> 
> =====
> Hans Dulimarta, Ph.D.                            dul...@co...
> Vis. Research Assoc.                  http://www.egr.msu.edu/~dulimart
> Ph: 517-432-7589  Fax: 760-281-7691   http://corelinux.sourceforge.net
> Elec. & Comp. Engg., Michigan State University, East Lansing, MI 48824
> 
> __________________________________________________
> Do You Yahoo!?
> Kick off your party with Yahoo! Invites.
> http://invites.yahoo.com/
> 
> _______________________________________________
> 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

Re: [Corelinux-develop] Sourceforge Task Manager

[Frank V. C. <fr...@co...>]

Hans Dulimarta wrote:
> 
> Today in my first day to browse the Task Manager after
> actively joining SourceForge since May of this year.
> [Sorry for my incognizance].
> 
> Specifically, I looked at the libcorelinux++
> implementation section. I responded this this group
> that I'll work on Semaphore and Thread.
> Assuming the information on the web page is update,
> I'd like to know what is the remaining 20% needs to be
> done on Semaphore and 75% on Thread.

We don't have an EventSemaphore
We don't have Signal Management for Threads 

-- 
Frank V. Castellucci

[Corelinux-develop] Re: Symbol in UML diagrams

[Hans D. <dul...@ya...>]

--- "Frank V. Castellucci" <fr...@co...>
wrote:
> Of course, those marked as const member functions in
> the diagram but not
> declared as such in the header files being?
>

Being what? I don't understand your answer.

> 
> Hans Dulimarta wrote:
> 
> > I found a "non-standard" symbol in the UML class
diagrams in
> > the .PNG files.
> > What is the meaning of "@" symbol? I thought it
was used to
> > denote "const member function", but then when I
compared
> > with other files, that's not the case. The class
diagram
> > shows the '@' symbol but the header file does
not have the
> > "const" attribute in the member function.
> >

> -- 
> Frank V. Castellucci
> 
> _______________________________________________
> Corelinux-develop mailing list
> Cor...@li...
>
http://lists.sourceforge.net/mailman/listinfo/corelinux-develop


=====
Hans Dulimarta, Ph.D.                            dul...@co...
Vis. Research Assoc.                  http://www.egr.msu.edu/~dulimart
Ph: 517-432-7589  Fax: 760-281-7691   http://corelinux.sourceforge.net
Elec. & Comp. Engg., Michigan State University, East Lansing, MI 48824

__________________________________________________
Do You Yahoo!?
Kick off your party with Yahoo! Invites.
http://invites.yahoo.com/

[Corelinux-develop] Sourceforge Task Manager

[Hans D. <dul...@ya...>]

Today in my first day to browse the Task Manager after
actively joining SourceForge since May of this year.
[Sorry for my incognizance].

Specifically, I looked at the libcorelinux++
implementation section. I responded this this group
that I'll work on Semaphore and Thread.
Assuming the information on the web page is update,
I'd like to know what is the remaining 20% needs to be
done on Semaphore and 75% on Thread.

=====
Hans Dulimarta, Ph.D.                            dul...@co...
Vis. Research Assoc.                  http://www.egr.msu.edu/~dulimart
Ph: 517-432-7589  Fax: 760-281-7691   http://corelinux.sourceforge.net
Elec. & Comp. Engg., Michigan State University, East Lansing, MI 48824

__________________________________________________
Do You Yahoo!?
Kick off your party with Yahoo! Invites.
http://invites.yahoo.com/

Re: [Corelinux-develop] [Fwd: Symbol in UML diagrams]

[Frank V. C. <fr...@co...>]

Of course, those marked as const member functions in the diagram but not
declared as such in the header files being?

Hans Dulimarta wrote:
> 
> Hans Dulimarta wrote:
> 
> > I found a "non-standard" symbol in the UML class diagrams in
> > the .PNG files.
> > What is the meaning of "@" symbol? I thought it was used to
> > denote "const member function", but then when I compared
> > with other files, that's not the case. The class diagram
> > shows the '@' symbol but the header file does not have the
> > "const" attribute in the member function.
> >

-- 
Frank V. Castellucci

[Corelinux-develop] [Fwd: Symbol in UML diagrams]

[Hans D. <dul...@eg...>]

Hans Dulimarta wrote:

> I found a "non-standard" symbol in the UML class diagrams in
> the .PNG files.
> What is the meaning of "@" symbol? I thought it was used to
> denote "const member function", but then when I compared
> with other files, that's not the case. The class diagram
> shows the '@' symbol but the header file does not have the
> "const" attribute in the member function.
>
> --
> Hans Dulimarta, Ph.D.                            dul...@co...
> Vis. Research Assoc.                 http://www.egr.msu.edu/~dulimart
> Ph: 517-432-7589  Fax: 760-281-7691   http://corelinux.sourceforge.net
> Elec. & Comp. Engg., Michigan State University, East Lansing, MI 48824

--
Hans Dulimarta, Ph.D.                            dul...@co...
Vis. Research Assoc.                  http://www.egr.msu.edu/~dulimart
Ph: 517-432-7589  Fax: 760-281-7691   http://corelinux.sourceforge.net
Elec. & Comp. Engg., Michigan State University, East Lansing, MI 48824

[Corelinux-develop] Caution

[Frank V. C. <fr...@co...>]

In a brief ping, Christophe mentioned the KDE-2 mini-declaration idl
capability.

I would like to put a flag of caution up for a second to consider a few
things in regards to the Library Loader.

The libcorelinux (libcl++.so) should contain:

1. The mimimal framework component abstractions (currently the Library
Load design)
2. Some level of behavior that will be common across all possible domain
specializations.
3. A first level derivation of the abstraction to types for dynamic
shared function libraries, with the exception of defining actual
ExecutionObjectDefinitions.

But realize that:

The actual ExecutionObjects and respective definitions is in the
solution space of the application domain. It is up to "them" to define
what a ExecutionObjectDefinition IS, what it contains, and so on. It is
impossible for us to do that for them, after all we don't know which
libraries they will be using. Of course I will be providing an example
that leverages the framework, but I won't be needing a parser or grammar
for that.

Now, when we (CoreLinux++) publish OUR frameworks, it is extremely
likely that we will make heavy use of the Library Load mini-framework to
facilitate the component architecture. At this point, a parser for
definition interchange is a likely requirement. And IDL is clearly a
very suitable fit specifically for ExecutionObjectDefinitions, but just
as clearly useless in any other type library (images, etc.).

Thoughts? Anyone?

-- 
Frank V. Castellucci

Re: [Corelinux-develop] Library discussion

[Frank V. C. <fr...@co...>]

Ok,

So one of the fundemental issues raised are on those types that have a
need to be reason with, for example LibraryType.

A LibraryType is a member of a ontology which describes, well, types of
libraries that are applicable to the loader. 

We can accomplish in more than one way:

1. We make it a numeric identifier (1 - ?)
2. We make it name bound ("FunctionLibraryType")
3. We make it a class type (as described below)

Now I will list some of the problems with these options:

1. Numeric identifier - Hard coded numbers are not a nice thing when
considering type ontologies because there is no reasonable scheme to
describe even simple single inheritence hierarchies of types.

2. Name Bindings - These are better in that we can describe a single
inheritence hierarchy of types (LibraryType.FunctionLibrary, or
LibraryType.CORBALibrary), but they leave us stranded when/if someone
wants to describe a type with multiple inheritence properties.

3. Class Type - To me this is the optimal solution in that we can
describe any type through it's parents. It is, of course, up to those
that would use it for reasoning to traverse the RTTI information (for
lack of a Class class).

Please respond to this in the context of the current design, or if you
feel the current design is no good or missing something. If this seems
reasonable, I can move on to the discussion of the
LibraryObjectDefinitions.


"Frank V. Castellucci" wrote:
> 
> Christophe brought up a question about the Library Loader framework
> implementation.
> 
> It may be useful to read this along side the design diagram
> 
> For the purposes of our discussion:
> 
> Library - This is really a registration point for users (developers) to
> register (at run time) a loader. To register a loader you need two (2)
> things: A Loader instance, and a LibraryType instance. Assuming there is
> no conflict, the Library now has a Loader service which can begin work.
> When a user calls the Library to create a LibraryInstance, they must
> include two things, the name of the library, and the type of loader that
> should handle the actual loading. At this point, a LibraryInstance is
> given back to the caller.
> 
> Loader - Besides the physical resolution and loading of a library, the
> Loader is a factory for LibraryInstances.
> 
> LibraryInstance - is the in memory object that represents, for all
> intents and purposes the library that was loaded. The responsibility for
> the LibraryInstance is to create, upon request, a LibraryObject. The
> LibraryInstance interacts with a ObjectDefinitionRegistry to determine,
> at run time, which type of LibraryObject derivation to instantiate. This
> is done by the caller registering a series of LibraryObjectDefinitions
> that describe what LibraryObject derivation should be instantiated upon
> request. This works by using the key from the LibraryInstance as
> associating LibraryObjectDefinitions to it.
> 
> ObjectDefinitionRegistry - an manager of the associations between a
> library and the LibraryObjectDefinitions that it contains.
> 
> LibraryObjectDefinition - a prototype which describes the interface and
> behavior of the actual LibraryObject instance. These are a sort of Class
> class, or meta-model which can be reasoned with at run time.
> 
> LibraryObject - is what the client actually interacts with to do
> whatever work with the object that the library type has described.
> 
> ---- end
> 
> Because it is a framework, it is required that the developer extend a
> number of the components to work together. We will actually be
> implementing the first extension which will handle loading dynamic
> shared libraries whose functions have a C calling convention. To do
> this, we will provide:
> 
> FunctionLibraryType (LibraryType) - fairly vacuous type derivation.
> FunctionLibraryLoader (Loader) - utilizes dlopen and dlclose to open
> libraries.
> FunctionLibrary (LibraryInstance) - exposes interface for getting and
> returning ExecutionObjects.
> ExecutionObjectDefinitions (LibraryObjectDefinition) - used to describe
> ExecutionObjects
> ExecutionObject (LibraryObject) - exposes the ability to "execute" with
> arguments and return values.
> 
> What the user will be responsible for to utilize the FunctionLibrary
> series is to create whatever ExecutionObjectDefinitions are needed at
> run time to serve up useable objects.
> 
> Now, this is a big "small" step for CoreLinux++ in that we are getting
> more into a framework type component, than the general patterns or IPC
> objects to date. There is a few issues that need to be cleared up as
> well, for example, like "HOW" do we describe arguments and return
> semantics? I have done this before but in a big way, maybe there is a
> better way.
> 

-- 
Frank V. Castellucci
http://corelinux.sourceforge.net
OOA/OOD/C++ Standards and Guidelines for Linux
http://PythPat.sourceforge.net
Pythons Pattern Package

Re: [Corelinux-develop] Man pages

[Frank V. C. <fr...@co...>]

Christophe Prud'homme wrote:
> 
>     Frank> /usr/man/man3
>     >> Oops I didn't see that bug thanks I will fix it ASAP
> cvs is updated now they are in /usr/man/man3
> 
>     Frank> BTW: I installed all of it, and then copied the examples as per the instructions and it
>     Frank> works like a charm!
> cool!
> 

Also, uninstall works correct now, no errors! Looks real good. Did you
see the Library Loader message?

-- 
Frank V. Castellucci

Re: [Corelinux-develop] Man pages

[Christophe Prud'h. <pru...@MI...>]

    Frank> /usr/man/man3
    >> Oops I didn't see that bug thanks I will fix it ASAP
cvs is updated now they are in /usr/man/man3

    Frank> BTW: I installed all of it, and then copied the examples as per the instructions and it
    Frank> works like a charm!
cool!

Re: [Corelinux-develop] Man pages

[Frank V. C. <fr...@co...>]

Christophe Prud'homme wrote:
> 
> >>>>> "Frank" == Frank V Castellucci <fr...@co...> writes:
> 
>     Frank> C., The man pages are being put into:
> 
>     Frank> /usr/man/man3/man3
> 
>     Frank> and I didn't know if they were supposed to go to:
> 
>     Frank> /usr/man/man3
> Oops I didn't see that bug thanks
> I will fix it ASAP
> 
> C.

BTW: I installed all of it, and then copied the examples as per the
instructions and it works like a charm! 

-- 
Frank V. Castellucci
http://corelinux.sourceforge.net
OOA/OOD/C++ Standards and Guidelines for Linux
http://PythPat.sourceforge.net
Pythons Pattern Package

Re: [Corelinux-develop] Man pages

[Christophe Prud'h. <pru...@MI...>]

>>>>> "Frank" == Frank V Castellucci <fr...@co...> writes:

    Frank> C., The man pages are being put into:

    Frank> /usr/man/man3/man3

    Frank> and I didn't know if they were supposed to go to:

    Frank> /usr/man/man3
Oops I didn't see that bug thanks
I will fix it ASAP

C.

[Corelinux-develop] Man pages

[Frank V. C. <fr...@co...>]

C.,

The man pages are being put into:

/usr/man/man3/man3

and I didn't know if they were supposed to go to:

/usr/man/man3

they are not found otherwise unless the man search is set, but there is
no indication to the user that they must do this, or it is not
automatically happening.

Thoughts?

-- 
Frank V. Castellucci