You can subscribe to this list here.
| 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
|
|
From: Frank V. C. <fr...@co...> - 2000-01-24 06:17:43
|
Joe Nelson wrote: > > > Unlike the patterns I have been working on, this one has some work to > > do. Even if no one wants to grab the Analysis bull by the horns, we > > should at least be discussing aspects of this like the detailed use > > cases, like the std::basic_string interface where the type can be > > ignored. I think this is a good chance to flex some of MagicDraw UML as > > well once we enumerate the use cases. > > How about making all strings be unicode? > Thats why we thought that a String abstraction would be useful, and anyone wanting Unicode or Utf and still use whatever we have could just adapt the string of choice to the CoreLinux++ string. This keeps us from being tied to a particular implementation (see Adapter or Bridge) and being flexible enough so we don't tie the developer down either. -- Frank V. Castellucci |
|
From: Jim K. <jrk...@li...> - 2000-01-24 02:06:16
|
"Frank V. Castellucci" wrote: > I applied the following to the /home/groups/corelinux/htdocs and all the > files and subdirectories: > > chmod -R g+rw *.* > > This may have fixed the problems with SCP and permissions. > > Could someone test this just by scp'ing a dummy file like > > scp us...@co...:/home/groups/corelinux/htdocs > > -- > Frank V. Castellucci > http://corelinux.sourceforge.net > OOA/OOD/C++ Standards and Guidelines for Linux > > _______________________________________________ > Corelinux-public mailing list > Cor...@li... > http://lists.sourceforge.net/mailman/listinfo/corelinux-public Thanks Frank, I was able to upload a test file via scp. --Jim |
|
From: Frank V. C. <fr...@co...> - 2000-01-23 18:08:57
|
Rik Hemsley wrote: > > #if Frank V. Castellucci > > Anyone have an example idea? My brain has turned to mush. > > The 'Design Patterns' book suggests a C compiler. > > Cheers, > Rik > > -- > 2. Implicate yourself in every interpretation. > LOL: Yeah, well, that would be some sample. Anything else along the lines of a proof-of-concept? -- Frank V. Castellucci |
|
From: Rik H. <ri...@kd...> - 2000-01-23 17:46:10
|
#if Frank V. Castellucci > Anyone have an example idea? My brain has turned to mush. The 'Design Patterns' book suggests a C compiler. Cheers, Rik -- 2. Implicate yourself in every interpretation. |
|
From: Frank V. C. <fr...@co...> - 2000-01-23 17:38:13
|
Anyone have an example idea? My brain has turned to mush. -- Frank V. Castellucci http://corelinux.sourceforge.net OOA/OOD/C++ Standards and Guidelines for Linux |
|
From: Frank V. C. <fr...@co...> - 2000-01-23 16:40:44
|
CVS and web updated Working on implementation -- Frank V. Castellucci http://corelinux.sourceforge.net OOA/OOD/C++ Standards and Guidelines for Linux |
|
From: Frank V. C. <fr...@co...> - 2000-01-23 15:59:59
|
Joe Nelson wrote:
>
> > If we just use Unicode then we either have to use another library, or
> > create one. What we originally proposed was to abstract the interface
> > and then provide some means to let users (developers) adapt another
> > string implementation to our interface. This is more complex but allows
> >
> > 1. For CoreLinux++ we can implement classes that use the String
> > abstraction. This way we are confident (as much as can be) that the
> > developers choice of string implementation won't break us (see Adapter).
> >
> > 2. String implementations that haven't been developed yet to be use
> > later on (ditto Adapter).
> >
> > 3. Dynamic string changes in some cases (see Bridge).
>
> So corelinux++ is only aiming to be an interface, rather than provide
> any implementations?
>
> --Joe
>
No, we need to at least provide a String derivation that works with
straight char.
For example, lets drop to a implementation for discussion:
AbstractString {abstract}
AbstractStringAdapter {abstract} isA Adapter, isAbstractString
StringUtf8 isA AbstractStringAdapter and hasA std::string
then StringUtf8 delegates to the string implementation when a
AbstractString method is invoked.
Meanwhile, any of our other classes (libcorelinux++, libcoreframework++)
that use a string would use AbstractString and would work with whatever
string( char, wchar, Unicde, etc) was adapted to our interface.
--
Frank V. Castellucci
http://corelinux.sourceforge.net
OOA/OOD/C++ Standards and Guidelines for Linux
|
|
From: Joe N. <3ne...@pr...> - 2000-01-23 15:41:55
|
> If we just use Unicode then we either have to use another library, or > create one. What we originally proposed was to abstract the interface > and then provide some means to let users (developers) adapt another > string implementation to our interface. This is more complex but allows > > 1. For CoreLinux++ we can implement classes that use the String > abstraction. This way we are confident (as much as can be) that the > developers choice of string implementation won't break us (see Adapter). > > 2. String implementations that haven't been developed yet to be use > later on (ditto Adapter). > > 3. Dynamic string changes in some cases (see Bridge). So corelinux++ is only aiming to be an interface, rather than provide any implementations? --Joe |
|
From: Frank V. C. <fr...@co...> - 2000-01-23 14:59:36
|
Joe Nelson wrote: > > > Unlike the patterns I have been working on, this one has some work to > > do. Even if no one wants to grab the Analysis bull by the horns, we > > should at least be discussing aspects of this like the detailed use > > cases, like the std::basic_string interface where the type can be > > ignored. I think this is a good chance to flex some of MagicDraw UML as > > well once we enumerate the use cases. > > How about making all strings be unicode? > My mail keeps getting whacked. Joe, If we just use Unicode then we either have to use another library, or create one. What we originally proposed was to abstract the interface and then provide some means to let users (developers) adapt another string implementation to our interface. This is more complex but allows 1. For CoreLinux++ we can implement classes that use the String abstraction. This way we are confident (as much as can be) that the developers choice of string implementation won't break us (see Adapter). 2. String implementations that haven't been developed yet to be use later on (ditto Adapter). 3. Dynamic string changes in some cases (see Bridge). -- 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 |
|
From: Joe N. <3ne...@pr...> - 2000-01-23 00:20:27
|
> Unlike the patterns I have been working on, this one has some work to > do. Even if no one wants to grab the Analysis bull by the horns, we > should at least be discussing aspects of this like the detailed use > cases, like the std::basic_string interface where the type can be > ignored. I think this is a good chance to flex some of MagicDraw UML as > well once we enumerate the use cases. How about making all strings be unicode? |
|
From: Frank V. C. <fr...@co...> - 2000-01-22 19:58:29
|
I removed Jim from the Feature (he completed the Requirement) Changed the Feature Status to Open Created Analysis task for String (open) Created Design task for String (open) Created Implementation task for String (open). Unlike the patterns I have been working on, this one has some work to do. Even if no one wants to grab the Analysis bull by the horns, we should at least be discussing aspects of this like the detailed use cases, like the std::basic_string interface where the type can be ignored. I think this is a good chance to flex some of MagicDraw UML as well once we enumerate the use cases. -- Frank V. Castellucci http://corelinux.sourceforge.net OOA/OOD/C++ Standards and Guidelines for Linux |
|
From: Frank V. C. <fr...@co...> - 2000-01-22 19:41:12
|
Implementation and test code. I will be working on design for Facade (although there is no real implementation other than a very base type), Flyweight, and Proxy. Proxy and Flyweight are the tough ones for obvious, or not so obvious reasons. At anyrate I am looking to put out 0.4.5 by Monday AM. so if there is anything else that someone wants in... -- Frank V. Castellucci http://corelinux.sourceforge.net OOA/OOD/C++ Standards and Guidelines for Linux |
|
From: Frank V. C. <fr...@co...> - 2000-01-22 18:41:45
|
I applied the following to the /home/groups/corelinux/htdocs and all the files and subdirectories: chmod -R g+rw *.* This may have fixed the problems with SCP and permissions. Could someone test this just by scp'ing a dummy file like scp us...@co...:/home/groups/corelinux/htdocs -- Frank V. Castellucci http://corelinux.sourceforge.net OOA/OOD/C++ Standards and Guidelines for Linux |
|
From: Frank V. C. <fr...@co...> - 2000-01-21 15:48:36
|
Ok, This is where my Linus administration is weak. What can I do to give you access to the directories? If that doesn't work, whatever THAT is, I will get SourceForge to make it happen. Jim Koontz wrote: > > "Frank V. Castellucci" wrote: > > > Jim Koontz wrote: > > > > > > "Frank V. Castellucci" wrote: > > > > > > > Includes update to Bridge pattern to remove RTTI, I basically > > > > templatized it. > > > > Includes updates to Composite Design > > > > Include Composite implementation and test source. > > > > > > > > Hows everyone doing here? > > > > > > I've updated the reqs.html to include a link to the string requirements > > > document, and the "updated" graphic. > > > > > > > You might want to upload them both to the web site: > > > > scp reqs.html > > jk...@co...:/home/groups/corelinux/htdocs/doc > > scp req????.html > > jk...@co...:/home/groups/corelinux/htdocs/doc/requirements > > > > it will prompt for your password. > > > > I HAVE tried to upload the files, but both the reqs.html, and the requirements > directory are owned by frankc as both the owner, and the group -- world having > read-only access... > > _______________________________________________ -- Frank V. Castellucci http://corelinux.sourceforge.net OOA/OOD/C++ Standards and Guidelines for Linux |
|
From: Jim K. <jrk...@li...> - 2000-01-21 15:37:57
|
"Frank V. Castellucci" wrote: > Jim Koontz wrote: > > > > "Frank V. Castellucci" wrote: > > > > > Includes update to Bridge pattern to remove RTTI, I basically > > > templatized it. > > > Includes updates to Composite Design > > > Include Composite implementation and test source. > > > > > > Hows everyone doing here? > > > > I've updated the reqs.html to include a link to the string requirements > > document, and the "updated" graphic. > > > > You might want to upload them both to the web site: > > scp reqs.html > jk...@co...:/home/groups/corelinux/htdocs/doc > scp req????.html > jk...@co...:/home/groups/corelinux/htdocs/doc/requirements > > it will prompt for your password. > > -- > Frank V. Castellucci > http://corelinux.sourceforge.net > OOA/OOD/C++ Standards and Guidelines for Linux > > _______________________________________________ > Corelinux-public mailing list > Cor...@li... > http://lists.sourceforge.net/mailman/listinfo/corelinux-public I HAVE tried to upload the files, but both the reqs.html, and the requirements directory are owned by frankc as both the owner, and the group -- world having read-only access... |
|
From: Frank V. C. <fr...@co...> - 2000-01-21 06:14:18
|
Jim Koontz wrote: > > "Frank V. Castellucci" wrote: > > > Includes update to Bridge pattern to remove RTTI, I basically > > templatized it. > > Includes updates to Composite Design > > Include Composite implementation and test source. > > > > Hows everyone doing here? > > I've updated the reqs.html to include a link to the string requirements > document, and the "updated" graphic. > You might want to upload them both to the web site: scp reqs.html jk...@co...:/home/groups/corelinux/htdocs/doc scp req????.html jk...@co...:/home/groups/corelinux/htdocs/doc/requirements it will prompt for your password. -- Frank V. Castellucci http://corelinux.sourceforge.net OOA/OOD/C++ Standards and Guidelines for Linux |
|
From: Jim K. <jrk...@li...> - 2000-01-21 04:58:48
|
"Frank V. Castellucci" wrote: > Includes update to Bridge pattern to remove RTTI, I basically > templatized it. > Includes updates to Composite Design > Include Composite implementation and test source. > > Hows everyone doing here? > > -- > Frank V. Castellucci > http://corelinux.sourceforge.net > OOA/OOD/C++ Standards and Guidelines for Linux > > _______________________________________________ > Corelinux-public mailing list > Cor...@li... > http://lists.sourceforge.net/mailman/listinfo/corelinux-public I've updated the reqs.html to include a link to the string requirements document, and the "updated" graphic. |
|
From: Frank V. C. <fr...@co...> - 2000-01-21 04:26:23
|
Includes update to Bridge pattern to remove RTTI, I basically templatized it. Includes updates to Composite Design Include Composite implementation and test source. Hows everyone doing here? -- Frank V. Castellucci http://corelinux.sourceforge.net OOA/OOD/C++ Standards and Guidelines for Linux |
|
From: Frank V. C. <fr...@co...> - 2000-01-18 05:36:04
|
Jim Koontz wrote: > > I've checked in the String requirements document (req4568.html). > Please give me your comments... > Jim, Looks good to me. You might want to referesh your /corelinux/doc/reqs.html before posting on the web and adding that nasty UpDaTeD blip. -- Frank V. Castellucci http://corelinux.sourceforge.net OOA/OOD/C++ Standards and Guidelines for Linux |
|
From: Frank V. C. <fr...@co...> - 2000-01-18 05:31:53
|
The design for the Composite pattern is uploaded and posted. It needed Iterator which is cross-referenced in the SRS. -- Frank V. Castellucci http://corelinux.sourceforge.net OOA/OOD/C++ Standards and Guidelines for Linux |
|
From: Jim K. <jrk...@li...> - 2000-01-18 03:59:28
|
I've checked in the String requirements document (req4568.html). Please give me your comments... Jim Koontz jrk...@us... |
|
From: Frank V. C. <fr...@co...> - 2000-01-18 02:41:49
|
I have released the Iterator implementation and test code. It was really a 0.4.2 release but I messed up on the Source Forge side, must need sleep. -- Frank V. Castellucci http://corelinux.sourceforge.net OOA/OOD/C++ Standards and Guidelines for Linux |
|
From: Frank V. C. <fr...@co...> - 2000-01-17 02:23:48
|
I have checked in the Iterator Pattern analysis and design work. I need it to complete the Composite pattern design. FYI : Iterator is designed as a template, with a CoreLinux derivation called CoreLinuxIterator that is aware of the STL nature of collections. I also removed myself as assigned for the other structural pattern Design and Implementation tasks as per loosening up the process flow for picking and choosing, or if you want to move on to requirements... Anyone have a feeling for Threads, Sempahores, Signals? -- Frank V. Castellucci http://corelinux.sourceforge.net OOA/OOD/C++ Standards and Guidelines for Linux |
|
From: Frank V. C. <fr...@co...> - 2000-01-15 17:23:50
|
I have updated the code standard to reflect the Exception issue posted earlier. Of course now I have to update existing code. -- Frank V. Castellucci http://corelinux.sourceforge.net OOA/OOD/C++ Standards and Guidelines for Linux |
|
From: Frank V. C. <fr...@co...> - 2000-01-15 16:32:05
|
I have checked in and uploaded the change of ownership granularity we discussed. So at this point we employ a Shopping Cart metaphore with the option to pick and choose the area you want to work in. -- Frank V. Castellucci http://corelinux.sourceforge.net OOA/OOD/C++ Standards and Guidelines for Linux |