corelinux-public Mailing List for CoreLinux++ (Page 22)

SourceForge Headquarters 1320 Columbia Street Suite 310 San Diego, CA 92101 +1 (858) 422-6466

I have put the Composite pattern model, reports, etc. into CVS and
updated the web pages.

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

While thinking about the reference count requirement it occured to be
that we should deal with an important issue up front:

As an example, lets assume we have a reference class that has the
behavior of incrementing a count as long as additional constructs
(through copy constructor or assignment) are read-only. The question is,
should the state changes in the Reference class be protected by a mutual
exclusion semaphore? If so, a) is it one (1) semaphore for all
instances? b) One semaphore per instance? c) Shared pools of semaphores
(Flyweight pattern) shared by the Reference class?

Each has their pros and cons (simplified):

Pros A: Small memory ( one semaphore for the class )
Cons A: Low degree of concurrency ( only one access at a time )

Pros B: High degree of concurrency ( only references to the same object
blocked )
Cons B: Large memory, possible semaphore exhaustion 

Pros C: High degree of concurrency ( See Pros B )
Cons C: More code and memory to manage pools ( maps, indirection,
extents, etc. )

The same applies to other types we have waiting in the wings.

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

As I am working through some of the analysis it is becoming apparent
that some of the requirements will reference work done elsewhere. 

For example, in the Bridge requirement we are going to provide the base
Bridge class and a derivation that enables reference counting. The
ReferenceCount class will be used (projecting here) by the Bridge
derivation. It seems reasonable that in the SRS for Bridge there is a
reference to the SRS for ReferenceCount (or whatever).

I can make the change to the template and the existing requirement
documents without much hassle at this point.

Any objections, issues, etc?

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

I added the Bridge analysis model,reports, and diagrams to the web and
CVS .

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

I updated the web-site to try out the previous posts.

The process.html is updated
The req2872.html is updated (Adapter Pattern SRS has links to reports
and images)

The main page (index.html) is updated. I included a counter and changed
the update icon. 

Does anyone know if JavaScript or PHP can read another pages modified
date and use that has a way to indicate WHEN a page is updated instead
of me moving that ugly little image around?

Corelinux++ Process Details - Last Modified - ......

would be more informative.

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

I am getting sick of the Back to Earth title so let me wrap it up with a
codification of what I have been speaking about in the previous posts.

I have attached an updated (but not checked in or posted to the web)
process.html page. I use Star Office to create these things but you can
just load it into your browser of choice.

-- 
Frank V. Castellucci
http://corelinux.sourceforge.net
OOA/OOD/C++ Standards and Guidelines for Linux
Another issue has reared a nasty head...

Assume (using Adapter Pattern) analysis effort is underway:

/corelinux/doc/models/2872.mdf
/corelinux/doc/models/2872.mdr

We generate a Use Case Report:

/corelinux/doc/models/analysis/2872uc.html

We then go and add a sequence diagram to the Instantiate Adapter Use
Case (use imagination) and want to generate it:

/corelinux/doc/models/analysis/2872sq.png (sq=Sequence, uc=Use Case,etc)

We realize that the Adapter instantiated needs to be returned. We add
the use case in the main document, and we add a sequence diagram to
that, regen the Use Case report and now gen the diagram image:

/corelinux/doc/models/analysis/2872sq.png [SLAM!!!]

Couple of thoughts:

1. We could name the images like XXXXsq-Y.png (where XXXX is Requirement
ID and Y is numeric identifier)
2. We could name the images like XXXXsq-Instantiate.png (avoids KNOWING
what Y is from case 1)

Thoughts?

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

Note that in MagicDraw UML when you generate a Use-Case report, the
actors get the documentation that was put in the specification, but use
cases don't. This is an acknowledged bug by NoMagic (fix is in 3.51 when
available).

There is some consolation in that the Data Dictionary will have the
specification documentation for the use case, just not as convenient in
the body of the document.

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

Forgot to mention that the scenario I put forth was presented by Jim
Koontz, I just doctored it up...so blame him for the problems.

But there are a couple of issues I thought of after I hit the send on
the last message:

1. For people who are pulling down the CVS tree there will be no reports
or images with invalid links from the SRS documents. They will have no
way to generate them either. This may force us to consider CVSing the
genned items.

2. There doesn't seem to be a way to save the settings about naming
conventions on the reports and images. This is really a process issue
(which will be documented online) but I thought I'd mention it.

3. MagicDraw UML currently has two (2) formats it saves in: MagicDraw
and Rose (the 98 version NOT the 98i). A third is on the way (XMI -
which is a modeling interchange DTD for XML). The MagicDraw format
insures we preserve any of the more advanced aspects of the model we
incorporate that Rose does not have support for in 98. But Rose is a
common tool.

My thoughts for these issues are:

#1 - CVS the reports and images (we deal with space and Source Forge
when that problem arises).
#2 - Follow process (needless comment I guess)
#3 - Use MagicDraw format. I'd rather we have all the UML features
available to us in our models over time and let Rose catch up. I agree
with Jim that the #1 response takes care of people without MagicDraw
UML.

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

Now that the new year has started, I am back in working form. Having
survived the flu, Christmas, new years weekend with my mother-in-law and
going back to work: I hope everyone else had it easier.

I first thought that the solution for the Analysis phase model, report,
and image naming convention seemed best served by:

A. Analysis models will be named by the RequirementID and placed in the
corelinux/doc/analysis directory as XXXX.md? for the model files. These
files are added and committed to CVS just like any other file.

B. Analysis Use-Case reports will be named XXXXuc.html and images
XXXXuc.png where:
        XXXX - Requirement ID
        uc = use-case
        sq = sequence
        co = collaboration

These files will NOT be put into CVS (because we can gen them at
anytime) but WILL be part of the release distribution. This will enable
non-MagicDraw users to view them.

The SRS document will need to be updated to link in the respective
reports and/or images.

C. Design will follow the same naming conventions with models and output
put in the /corelinux/doc/design although this brings up an issue :

When we recognize a opportunity that would change the analysis we would
then have the problem of having to update the design model as well.

So my final thoughts are:

    /corelinux/docs/models   -    For the XXXX.md? file, to be used for
Analysis and Design modeling
    /corelinux/docs/analysis  -    For the Analysis Reports and Images
    /corelinux/docs/design    -    For the Design Reports and Images

The reason for the segregation of a & d is that you may want/need to
generate images for class diagrams that are used to embellish the
Analysis which is a different class diagram for a detailed Design.

Anyone? Bueller?

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

On Wed, 29 Dec 1999, Frank V. Castellucci wrote:

> The opportunity:
> 
> 1. We have a Requirement document id that works fine for the SRS
> 2. In analysis, and subsequently for design, there is the potential for
> an explosion of reports and images.
> 
> So for, as an simple example, the Adapter pattern we have:
> 
> 1. The model files (there are two for each "project" in MagicDraw *.mdf
> and *.mdr) which includes all diagrams and work
> 2. Generated report files (number depending on what reports are
> generated).
> 3. Generated images.
> 
> Here is the issue(s):
> 
> A) How do we contain this so that references to any web-files (reports
> and images) can be accessed in a uniform way, either through a document
> template we describe or through a script-like capability?
> 
> B) Do we CVS the reports and images? I don't know about space
> restrictions per project on Source Forge but I would imagine over time
> that we would chew it up. There are other things we need to do with the
> space (MySQL, project data, forums, etc).
> 
> I will toy around with "A" as I have the tool and can determine if we
> should just generate one (1) report and a page of images, so on and so
> forth...
> 
> -- 
> Frank V. Castellucci
> http://corelinux.sourceforge.net
> OOA/OOD/C++ Standards and Guidelines for Linux
> http://www.colconsulting.com 
> Object Oriented Analysis and Design |Java and C++ Development

We need a single document repository.

As far as the datafiles from MagicDraw go, we can define each requirement
as a "project" in order to keep a versionable granularity.  

If libcorelinux as a whole is stored as a single monolithic
MagicDraw project, it will not be versionable, because it will not be
trivial to merge changes. Thus the path of least resistance would seem to
be to make each requirement a MagicDraw project.   The Corelinux++ project
as a whole can be divided between participants to decrease the likelihood
of a merge conflict in CVS.

If images and reports can be stored in MagicDraw projects and generated
on demand, we can CVS MagicDraw projects - or store them on the ftp
server, if version control is not appropriate for these files. Once a
project has been completed, images and reports can be generated and posted
to the web for review by participants that do not have MagicDraw.  

--Jim

Excellent news!

--Jim

On Wed, 29 Dec 1999, Frank V. Castellucci wrote:

> I have completed the SRS for the Structural Patterns and have updated
> the web site. It became to much work for me to post the SRS here (albeit
> HTML tags) and on the web-site and cvs and...
> 
> If there are any issues with the SRS certainly bring it up here.
> 
> I have tested the downloaded procedure that NoMagic has put in place for
> us. I have run the product, generated reports and images (PNG are much
> smaller than JPEG).
> 
> In a conversation with NoMagic we came to the understanding that only
> project members that are actuall DOING analysis or design work need a
> copy. Each project member that will be doing so needs to:
> 
> 1. Let me know, so I can e-mail NoMagic about your Source Forge user id.
> They will want to keep you updated to changes, etc.
> 2. Wait for the download instructions from me via e-mail.
> 
> I am awaiting their written approval to post their URL on our web-pages
> (as per the original "gratis" agreement).
> 
> -- 
> Frank V. Castellucci
> http://corelinux.sourceforge.net
> OOA/OOD/C++ Standards and Guidelines for Linux
> http://www.colconsulting.com 
> Object Oriented Analysis and Design |Java and C++ Development
> 
> _______________________________________________
> Corelinux-public mailing list
> Cor...@li...
> http://lists.sourceforge.net/mailman/listinfo/corelinux-public
> 

On Tue, 28 Dec 1999, Frank V. Castellucci wrote:

> Jim Koontz wrote:
> > 
> > Okay, I tried to login using ssh, and yes, I have my own home directory,
> > and can find our group directory with the project html docs.  Cool!
> > 
> > I looked at the server logs, and found out why the Corelinux++ project
> > had such a high download rate for a while:  Someone has been busy
> > posting project announcements on some popular Linux sites, and touched
> > off a few C vs C++ flame wars too!
> > 
> > Anyway, I have ssh working to its fullest extent on my machine, and it
> > looks like I am set up properly on SourceForge as well.
> > 
> > --Jim
> > 
> 
> Great. Did you use some kind of tool for the logs?
>

No, just vi.

[snip] 
> 
> I saw the flames in the Linux Today announcement. People down right
> don't want C++ on Linux?!?!?! 
>

Some people don't.  They are of the opinion that C++ programs are bloated
and slow. I loved the comment that evidence of the "C++ bloat effect" could be 
seen in Windows programs written in C++!  What were they looking at...Microsoft
Word?!? 

If I didn't think C++ on Linux was worth while, I wouldn't be here. If
others don't like C++ they don't have to use it -- its that simple.

--Jim

The opportunity:

1. We have a Requirement document id that works fine for the SRS
2. In analysis, and subsequently for design, there is the potential for
an explosion of reports and images.

So for, as an simple example, the Adapter pattern we have:

1. The model files (there are two for each "project" in MagicDraw *.mdf
and *.mdr) which includes all diagrams and work
2. Generated report files (number depending on what reports are
generated).
3. Generated images.

Here is the issue(s):

A) How do we contain this so that references to any web-files (reports
and images) can be accessed in a uniform way, either through a document
template we describe or through a script-like capability?

B) Do we CVS the reports and images? I don't know about space
restrictions per project on Source Forge but I would imagine over time
that we would chew it up. There are other things we need to do with the
space (MySQL, project data, forums, etc).

I will toy around with "A" as I have the tool and can determine if we
should just generate one (1) report and a page of images, so on and so
forth...

-- 
Frank V. Castellucci
http://corelinux.sourceforge.net
OOA/OOD/C++ Standards and Guidelines for Linux
http://www.colconsulting.com 
Object Oriented Analysis and Design |Java and C++ Development

I have completed the SRS for the Structural Patterns and have updated
the web site. It became to much work for me to post the SRS here (albeit
HTML tags) and on the web-site and cvs and...

If there are any issues with the SRS certainly bring it up here.

I have tested the downloaded procedure that NoMagic has put in place for
us. I have run the product, generated reports and images (PNG are much
smaller than JPEG).

In a conversation with NoMagic we came to the understanding that only
project members that are actuall DOING analysis or design work need a
copy. Each project member that will be doing so needs to:

1. Let me know, so I can e-mail NoMagic about your Source Forge user id.
They will want to keep you updated to changes, etc.
2. Wait for the download instructions from me via e-mail.

I am awaiting their written approval to post their URL on our web-pages
(as per the original "gratis" agreement).

-- 
Frank V. Castellucci
http://corelinux.sourceforge.net
OOA/OOD/C++ Standards and Guidelines for Linux
http://www.colconsulting.com 
Object Oriented Analysis and Design |Java and C++ Development

Jim Koontz wrote:
> 
> Okay, I tried to login using ssh, and yes, I have my own home directory,
> and can find our group directory with the project html docs.  Cool!
> 
> I looked at the server logs, and found out why the Corelinux++ project
> had such a high download rate for a while:  Someone has been busy
> posting project announcements on some popular Linux sites, and touched
> off a few C vs C++ flame wars too!
> 
> Anyway, I have ssh working to its fullest extent on my machine, and it
> looks like I am set up properly on SourceForge as well.
> 
> --Jim
> 

Great. Did you use some kind of tool for the logs?

Yes, I update freshmeat, appwatch, linuxapps, and icewalkers whenever we
have a new release. I also made some project announcements in other
places that just point to the home page.

I saw the flames in the Linux Today announcement. People down right
don't want C++ on Linux?!?!?! 

-- 
Frank

Okay, I tried to login using ssh, and yes, I have my own home directory,
and can find our group directory with the project html docs.  Cool!

I looked at the server logs, and found out why the Corelinux++ project
had such a high download rate for a while:  Someone has been busy
posting project announcements on some popular Linux sites, and touched
off a few C vs C++ flame wars too!

Anyway, I have ssh working to its fullest extent on my machine, and it
looks like I am set up properly on SourceForge as well.

--Jim

Jim Koontz wrote:
> 
> On Tue, 28 Dec 1999, Frank V. Castellucci wrote:
> 
> >
> >
> > "Koontz, Jim" wrote:
> > >
> > > Frank wrote:
> > > [snip]
> > > ---
> > > So these documents can be generated by the trial version of MagicDraw?  Any
> > > response on the request for the "controlled donation"?  I am concerned that
> > > after the trial period expires, it will not be possible to use the tool
> > > again.
> >
> > Good news received today. NoMagic has agreed to donate a limited number
> > of copies for our efforts. The version they are donating is the
> > professional version. I am awaiting instructions from the NoMagic
> > contact for download and accountability issue.
> 
> Yay NoMagic, those guys are all right!  Good work Frank!
> 
> >
> >
> > > Incidentally, I finally had time to get CVS and ssh working on my machine,
> > > and was able to checkout the latest version of CoreLinux++ from CVS.
> > > Everything seems to be working just fine for me.
> >
> > Great. When you log in with SSH, do you have your own home directory?
> >
> 
> Hmm, I  used CVS and ssh to get the source code, but I haven't logged in
> using ssh directly. I don't really know what host to connect to, although
> I have seen in the SourceForge doc that I should have access to our web
> directory.  I'll have to give that a try tonight.
> 
> --Jim

Jim, you should be able to:

ssh corelinx.sourceforge.net

and it will prompt for you sourceforge user id and password.

-- 
Frank V. Castellucci
http://corelinux.sourceforge.net
OOA/OOD/C++ Standards and Guidelines for Linux
http://www.colconsulting.com 
Object Oriented Analysis and Design |Java and C++ Development

On Tue, 28 Dec 1999, Frank V. Castellucci wrote:

> 
> 
> "Koontz, Jim" wrote:
> > 
> > Frank wrote:
> > [snip]
> > ---
> > So these documents can be generated by the trial version of MagicDraw?  Any
> > response on the request for the "controlled donation"?  I am concerned that
> > after the trial period expires, it will not be possible to use the tool
> > again.
> 
> Good news received today. NoMagic has agreed to donate a limited number
> of copies for our efforts. The version they are donating is the
> professional version. I am awaiting instructions from the NoMagic
> contact for download and accountability issue.

Yay NoMagic, those guys are all right!  Good work Frank!

> 
> 
> > Incidentally, I finally had time to get CVS and ssh working on my machine,
> > and was able to checkout the latest version of CoreLinux++ from CVS.
> > Everything seems to be working just fine for me.
> 
> Great. When you log in with SSH, do you have your own home directory?
> 

Hmm, I  used CVS and ssh to get the source code, but I haven't logged in
using ssh directly. I don't really know what host to connect to, although
I have seen in the SourceForge doc that I should have access to our web
directory.  I'll have to give that a try tonight.

--Jim

"Koontz, Jim" wrote:
> 
> Frank wrote:
> [snip]
> ---
> So these documents can be generated by the trial version of MagicDraw?  Any
> response on the request for the "controlled donation"?  I am concerned that
> after the trial period expires, it will not be possible to use the tool
> again.

Good news received today. NoMagic has agreed to donate a limited number
of copies for our efforts. The version they are donating is the
professional version. I am awaiting instructions from the NoMagic
contact for download and accountability issue.

> Incidentally, I finally had time to get CVS and ssh working on my machine,
> and was able to checkout the latest version of CoreLinux++ from CVS.
> Everything seems to be working just fine for me.

Great. When you log in with SSH, do you have your own home directory?

> On to requirements....
> 
> --Jim

Great 

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

Frank wrote:
>Right, In the past, the Analysis and Design documentation was the model.
MagicDraw generates reports >for Use-case and Class/Object Models (and I
think for coll. and seq.) which I don`t know if we can control. Another
interesting fact about MagicDraw is that it can save and restore as Rose
petal files. This >may be the format of choice until we find functional XMI
exchanging tools. MD also can generate PNG >files of the diagrams. That is
the next step for me, document the process with these diagrams and reports. 
>Holding up through the holidays, 
>Frank 
---
So these documents can be generated by the trial version of MagicDraw?  Any
response on the request for the "controlled donation"?  I am concerned that
after the trial period expires, it will not be possible to use the tool
again.

Incidentally, I finally had time to get CVS and ssh working on my machine,
and was able to checkout the latest version of CoreLinux++ from CVS.
Everything seems to be working just fine for me.

On to requirements....

--Jim

The following was put into the CodeCraft mailing list newsletter. It's
focus is Linux users and developers:
----------------------------------

Frank V. Castellucci sent me the address of the CoreLinux
web site a while ago, but I've only just now got around to
checking it out. It was definitely worth the click!

CoreLinux is a group of programmers helping to standardize
conventions for C++ development under Linux environments.
They are developing C++ class libraries to help developers
take advantage of the features and performance offered by
Linux. Their libraries are aiming to be portable across
different Linux distributions and platforms, while avoiding
the code bloat and compromises that would be required to
make them portable to other operating systems.

All of the source code for the libraries will be available
under the Free Software Foundation (FSF) Lesser General
Public License (LGPL).

I was especially interested in the C++ and Object Oriented
Design standards and guidelines pages. I'll definitely be
returning regularly to refer to them!

Darren Collins

---
Frank V. Castellucci
http://corelinux.sourceforge.net
OOA/OOD/C++ Standards and Guidelines for Linux
http://www.colconsulting.com
Object Oriented Analysis and Design |Java and C++ Development

> > [snip]
>
> Okay, so we already have provisions for document templates, and  we
only
> have one standard document.   :-}
>
> Jim Koontz

Right, In the past, the Analysis and Design documentation was the model.
MagicDraw generates reports for Use-case and Class/Object Models (and I
think for coll. and seq.) which I don't know if we can control.

Another interesting fact about MagicDraw is that it can save and restore
as Rose petal files. This may be the format of choice until we find
functional XMI exchanging tools. MD also can generate PNG files of the
diagrams. That is the next step for me, document the process with these
diagrams and reports.

Holding up through the holidays,
Frank

"Frank V. Castellucci" wrote:

> > "Frank V. Castellucci" wrote:
> >
> > > --
> -- Original Message -----
> > > > We should have an area for document templates.  I am assuming that
> our
> > > file
> > > > format will be HTML.  It would be convenient to have these on the
> web,
> > > or in
> > > > CVS, or both.
> > > >
> > > > I know that the design documentation will be dictated largely by
> UML,
> > > but it
> > > > would be nice to have templates for these documents, and for the
> > > > requirements documents as well.
> > > >
> > > > Jim Koontz
> > > > jrk...@us...
> > > >
> > >
> > > Do you mean cascading style sheets?
> > >
> > > ---
> > > Frank V. Castellucci
> >
> > Hmm...I actually meant a template for each document type containing
> the
> > headings in the appropriate type style, but a style sheet that
> controls the
> > formatting of all documentation is a good idea too.
> >
> > Jim Koontz
> > jrk...@us...
>
> Well, we have the SRS template already in CVS and located in the
> /corelinux/doc directory. What other document templates were you
> thinking of.
> ---
> Frank V. Castellucci
> http://corelinux.sourceforge.net
>
> _______________________________________________
> Corelinux-public mailing list
> Cor...@li...
> http://lists.sourceforge.net/mailman/listinfo/corelinux-public

Okay, so we already have provisions for document templates, and  we only
have one standard document.   :-}

Jim Koontz
jrk...@us...

I added the Bridge,Composite and Decorator pattern SRS to the web. They
are also in CVS and have Features open for them.

If anyone wants to start on the other pattern sets:

1. You need to be a project member*
2. You need to create individual requirements in the Forum so they have
unique identifiers.
3. Just follow the process document at that point.

* To join the project I need:

1. Your Source Forge User Name
2. Your area of interest
3. Your Linux distribution
4. Your hardware setup
5. Optionally your strongest and weakest areas of experience

So far we have myself, Ace, jrkoontz, and tmaguire

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

1999	Jan	Feb	Mar	Apr	May	Jun	Jul	Aug	Sep	Oct	Nov	Dec (79)
2000	Jan (91)	Feb (50)	Mar (27)	Apr (12)	May (41)	Jun (17)	Jul (12)	Aug (7)	Sep (6)	Oct (10)	Nov (9)	Dec (1)
2001	Jan (3)	Feb	Mar (6)	Apr (8)	May (4)	Jun (4)	Jul	Aug	Sep	Oct (7)	Nov	Dec
2002	Jan	Feb	Mar	Apr	May	Jun	Jul	Aug	Sep	Oct (3)	Nov	Dec
2003	Jan (1)	Feb	Mar	Apr	May	Jun	Jul	Aug	Sep	Oct (1)	Nov	Dec
2004	Jan (1)	Feb	Mar	Apr	May (1)	Jun	Jul	Aug	Sep	Oct (2)	Nov	Dec
2006	Jan (4)	Feb (4)	Mar (3)	Apr (1)	May (8)	Jun (8)	Jul (7)	Aug (3)	Sep (7)	Oct (19)	Nov (28)	Dec (5)
2007	Jan (25)	Feb (9)	Mar (15)	Apr (6)	May (1)	Jun (2)	Jul (4)	Aug (12)	Sep (10)	Oct (12)	Nov (5)	Dec (2)
2008	Jan (3)	Feb (5)	Mar (28)	Apr (23)	May (19)	Jun (13)	Jul (31)	Aug (12)	Sep (21)	Oct (14)	Nov (48)	Dec (39)
2009	Jan (10)	Feb (15)	Mar (12)	Apr (19)	May (40)	Jun (24)	Jul (34)	Aug (12)	Sep (4)	Oct	Nov	Dec (13)
2010	Jan (5)	Feb (5)	Mar (4)	Apr (3)	May	Jun	Jul (3)	Aug (1)	Sep (1)	Oct (3)	Nov	Dec

corelinux-public Mailing List for CoreLinux++ (Page 22)

corelinux-public — General discussions of CoreLinux++