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: Hans - D. <dul...@eg...> - 2000-11-15 21:57:02
|
On Wed, 15 Nov 2000, Frank V. Castellucci wrote: > Date: Wed, 15 Nov 2000 13:18:21 -0500 > From: Frank V. Castellucci <fr...@co...> > Reply-To: cor...@li... > To: cor...@li... > Subject: Re: [Corelinux-develop] Comments and documentation > > With Christophe's comments and yours we can begin to weed through this > jungle > > I think that we should only add the magical doxygen tags in the header > files where we need to use what JavaDoc does not provide, for macros, > enums, etc. > > By doxygen specific I mean those tags that have: > > /*! > */ > > instead of > > /** > */ > > And Hans, I meant consistent with the CoreLinux++ comment style > > As far as the source inclusion, I believe the inclusion of header and > source files in the documentation is overkill and redundant as the > curious user can download the tarball which has the real thing! > Oh..., I misunderstood your point. Now, I understand that what you mean is the inclusion of the TEXT of the source code/headers. In this case, I agree with you. The TEXT of the source code/headers should not be included. I believe Doxygen can be configured to replace them with a hyperlink instead. I thought you meant inclusion/exclusion of source codes in Doxygen search path controlled by the INPUT, FILE_PATTERNS, EXCLUDE, and EXCLUDE_PATTERNS Doxygen options. > Most programmers reference don't include the source code in the > reference or the headers, what I am familiar with is a general > description with a method by method break down. Some example code to > emphasize usage, and an overview (which will become very important in > the frameworks). > > More thoughts? > -- 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-11-15 18:14:20
|
With Christophe's comments and yours we can begin to weed through this jungle I think that we should only add the magical doxygen tags in the header files where we need to use what JavaDoc does not provide, for macros, enums, etc. By doxygen specific I mean those tags that have: /*! */ instead of /** */ And Hans, I meant consistent with the CoreLinux++ comment style As far as the source inclusion, I believe the inclusion of header and source files in the documentation is overkill and redundant as the curious user can download the tarball which has the real thing! Most programmers reference don't include the source code in the reference or the headers, what I am familiar with is a general description with a method by method break down. Some example code to emphasize usage, and an overview (which will become very important in the frameworks). More thoughts? Hans - Dulimarta wrote: > > On Wed, 15 Nov 2000, Frank V. Castellucci wrote: > > > Date: Wed, 15 Nov 2000 09:57:20 -0500 > > From: Frank V. Castellucci <fr...@co...> > > Reply-To: cor...@li... > > To: CoreLinux Development <cor...@li...> > > Subject: [Corelinux-develop] Comments and documentation > > > > > > Christophe introduced a new form of documentation for code (headers and > > modules). > > > > A couple of issues with this > > > > 1. It is not consistent with the majority of the code and makes > > readability a problem. > > Do you mean the majority of the code in our corelinux project > or majority of the code in other projects as well? > > > 2. By including all the source code and all the headers, documentation > > is growing and is redundant. > > I think there should be two different kinds of manual: user's guide and > programmer reference. What we have now is a programmer reference manual, > which is usually huge in size. For completeness we should not leave out > any source code at all but to minimize redundancy trimming the doxygen > comments in our source codes might be necessary. > > > > > Thoughts? > > > > _______________________________________________ > > 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: Christophe Prud'h. <pru...@an...> - 2000-11-15 15:47:31
|
Another comment about source documentation : normally doxygen strips out the documentation from the source file when it creates the html source code. so that the source code is more readable. if not then that is bad and clearly redundant with the extracted and generated doc ! Ijsut checked my debian corelinux doc and the documentation is removed by doxygen before creating the corresponding html file However some comments don't disappear like the GNU LICENSE and non javadoc/doxygen comments best regards C. -- Christophe Prud'homme MIT -- 77 Mass Ave 02215 Cambridge MA |
|
From: Christophe Prud'h. <pru...@an...> - 2000-11-15 15:40:56
|
I was thinking about the inclusion of the source code + headers in the html doc. > What about the syntax of using > /*! > */ > > in the headers? is it at the very beginning of the file with the \file flag, or for macro documentation? normally the doxygen specific flags appear when there is no javadoc equivalent if not then I made a mistake I think that doxygen introduces some interesting features that enables to extract relevant and useful informations depending on the context. if it happens that javadoc is extended then it is likely that doxygen provides a similar feature then it is just a matter of modifying the tag(perl script) and I guess that the doxygen team will try to implement the new javadoc features. > > BTW: It is my intent to open this for discussion, not to abolish. I was > pointing out the downsides. Is there a happy medium? that is a good one I think :) -- Christophe Prud'homme MIT -- 77 Mass Ave 02215 Cambridge MA |
|
From: Hans - D. <dul...@eg...> - 2000-11-15 15:31:14
|
On Wed, 15 Nov 2000, Frank V. Castellucci wrote: > Date: Wed, 15 Nov 2000 09:55:23 -0500 > From: Frank V. Castellucci <fr...@co...> > Reply-To: cor...@li... > To: cor...@li... > Subject: Re: [Corelinux-develop] Semaphores > > > > Hans - Dulimarta wrote: > > > On Wed, 15 Nov 2000, Frank V. Castellucci wrote: > > > > > Date: Wed, 15 Nov 2000 09:02:37 -0500 > > > From: Frank V. Castellucci <fr...@co...> > > > Reply-To: cor...@li... > > > To: CoreLinux Development <cor...@li...> > > > Subject: [Corelinux-develop] Semaphores > > > > > > Hans, > > > > > > How are we looking? > > > > > > I'm getting ready (today) to release another libclfw++ and was wondering > > > about libcorelinux. > > > > > > > I finished adding and testing the EventSemaphore::post() method. I have > > not cheched them in yet, I need to clean up the debugging lines and try to > > reformat the source code to comply with the corelinux C++ coding standard. > > > > I'll clean them up and check them in tonight. > > Ok, did you change any interface/signatures to existing methods? > I guess I did on one of them (forgot which one). I added throw (SemOpStat) to the declaration for consistency with the others. Other that that, the function signatures remain the same. > > > > > > Could either you or Christophe teach me how to setup gdb 5.0 to be > > thread aware? I'm using gdb 5.0 that comes with RedHat 7.0 but it looks > > like it is not thread aware. > > No idea, sorry? And let me note that it is not clear if gdb is POSIX thread > aware or "clone" thread aware. > > > > > > > > Thanks > > > > > > > > > > -- > > 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 > > _______________________________________________ > 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-11-15 15:26:05
|
On Wed, 15 Nov 2000, Frank V. Castellucci wrote: > Date: Wed, 15 Nov 2000 09:57:20 -0500 > From: Frank V. Castellucci <fr...@co...> > Reply-To: cor...@li... > To: CoreLinux Development <cor...@li...> > Subject: [Corelinux-develop] Comments and documentation > > > Christophe introduced a new form of documentation for code (headers and > modules). > > A couple of issues with this > > 1. It is not consistent with the majority of the code and makes > readability a problem. Do you mean the majority of the code in our corelinux project or majority of the code in other projects as well? > 2. By including all the source code and all the headers, documentation > is growing and is redundant. I think there should be two different kinds of manual: user's guide and programmer reference. What we have now is a programmer reference manual, which is usually huge in size. For completeness we should not leave out any source code at all but to minimize redundancy trimming the doxygen comments in our source codes might be necessary. > > Thoughts? > > _______________________________________________ > 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-11-15 15:24:13
|
Christophe Prud'homme wrote: > On Wednesday 15 November 2000 14:57, you wrote: > > Christophe introduced a new form of documentation for code (headers and > > modules). > > > > A couple of issues with this > > > > 1. It is not consistent with the majority of the code and makes > > readability a problem. > > 2. By including all the source code and all the headers, documentation > > is growing and is redundant. > > > > Thoughts? > change the doxygen configuration file > do not include headers and source code > I don't remember the exact name of the options but you should be able to find > it easily (look for SOURCE/CODE and HEADER) What about the syntax of using /*! */ in the headers? BTW: It is my intent to open this for discussion, not to abolish. I was pointing out the downsides. Is there a happy medium? > > > C. > -- > Christophe Prud'homme > MIT -- 77 Mass Ave > 02215 Cambridge MA > _______________________________________________ > Corelinux-develop mailing list > Cor...@li... > http://lists.sourceforge.net/mailman/listinfo/corelinux-develop |
|
From: Christophe Prud'h. <pru...@an...> - 2000-11-15 15:10:01
|
On Wednesday 15 November 2000 14:57, you wrote: > Christophe introduced a new form of documentation for code (headers and > modules). > > A couple of issues with this > > 1. It is not consistent with the majority of the code and makes > readability a problem. > 2. By including all the source code and all the headers, documentation > is growing and is redundant. > > Thoughts? change the doxygen configuration file do not include headers and source code I don't remember the exact name of the options but you should be able to find it easily (look for SOURCE/CODE and HEADER) C. -- Christophe Prud'homme MIT -- 77 Mass Ave 02215 Cambridge MA |
|
From: Frank V. C. <fr...@co...> - 2000-11-15 14:56:11
|
Christophe introduced a new form of documentation for code (headers and modules). A couple of issues with this 1. It is not consistent with the majority of the code and makes readability a problem. 2. By including all the source code and all the headers, documentation is growing and is redundant. Thoughts? |
|
From: Frank V. C. <fr...@co...> - 2000-11-15 14:54:14
|
Hans - Dulimarta wrote: > On Wed, 15 Nov 2000, Frank V. Castellucci wrote: > > > Date: Wed, 15 Nov 2000 09:02:37 -0500 > > From: Frank V. Castellucci <fr...@co...> > > Reply-To: cor...@li... > > To: CoreLinux Development <cor...@li...> > > Subject: [Corelinux-develop] Semaphores > > > > Hans, > > > > How are we looking? > > > > I'm getting ready (today) to release another libclfw++ and was wondering > > about libcorelinux. > > > > I finished adding and testing the EventSemaphore::post() method. I have > not cheched them in yet, I need to clean up the debugging lines and try to > reformat the source code to comply with the corelinux C++ coding standard. > > I'll clean them up and check them in tonight. Ok, did you change any interface/signatures to existing methods? > > > Could either you or Christophe teach me how to setup gdb 5.0 to be > thread aware? I'm using gdb 5.0 that comes with RedHat 7.0 but it looks > like it is not thread aware. No idea, sorry? And let me note that it is not clear if gdb is POSIX thread aware or "clone" thread aware. > > > > Thanks > > > > > > -- > 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: Frank V. C. <fr...@co...> - 2000-11-15 14:53:01
|
Christophe Prud'homme wrote: > > I'm getting ready (today) to release another libclfw++ and was wondering > > about libcorelinux. > ok I am online, do you want me to generate the deb ? > Not yet, waiting to hear back from Hans concerning the semaphores, and I have some last minute touch ups to do for libclfw++. But, glad to hear you back in the saddle! > > best regards > C. > -- > Christophe Prud'homme > MIT -- 77 Mass Ave > 02215 Cambridge MA > _______________________________________________ > Corelinux-develop mailing list > Cor...@li... > http://lists.sourceforge.net/mailman/listinfo/corelinux-develop |
|
From: Hans - D. <dul...@eg...> - 2000-11-15 14:29:43
|
On Wed, 15 Nov 2000, Frank V. Castellucci wrote: > Date: Wed, 15 Nov 2000 09:02:37 -0500 > From: Frank V. Castellucci <fr...@co...> > Reply-To: cor...@li... > To: CoreLinux Development <cor...@li...> > Subject: [Corelinux-develop] Semaphores > > Hans, > > How are we looking? > > I'm getting ready (today) to release another libclfw++ and was wondering > about libcorelinux. > I finished adding and testing the EventSemaphore::post() method. I have not cheched them in yet, I need to clean up the debugging lines and try to reformat the source code to comply with the corelinux C++ coding standard. I'll clean them up and check them in tonight. Could either you or Christophe teach me how to setup gdb 5.0 to be thread aware? I'm using gdb 5.0 that comes with RedHat 7.0 but it looks like it is not thread aware. > Thanks > > -- 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...@an...> - 2000-11-15 14:07:04
|
> I'm getting ready (today) to release another libclfw++ and was wondering > about libcorelinux. ok I am online, do you want me to generate the deb ? best regards C. -- Christophe Prud'homme MIT -- 77 Mass Ave 02215 Cambridge MA |
|
From: Frank V. C. <fr...@co...> - 2000-11-15 13:58:38
|
Hans, How are we looking? I'm getting ready (today) to release another libclfw++ and was wondering about libcorelinux. Thanks -- 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-11-07 00:17:06
|
Christophe Prud'homme wrote: > > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > > Heh, I was wondering about that. > the 0.4.29 corelinux in packages/debian is for potato > > > > I take it that woody debs are not readable by potato systems? > no, the problem comes from the libc which is not the same > otherwise the installation will be fine. > potato debs works on woody > but the reverse might not be true. I added the debian libclfw that were on /corelinux/packages/debian. I didn't reload the libcorelinux 0.4.29 because we already had them. > > > > > If they are, then I would say we replace the current with the woody built, > the potato built you mean ? > I think it is not possible to replace, on sourceforge, released files with > the new ones with the same name. It has to be different. Am I wrong? No, I can delete the ones that are there and then add the new ones with the same name. > > > otherwise we will need -2 with a reasonable change to the download.php. > I can do that. > tell me ASAP > I'll be here late. Whatever you want, I can do the -2 or just replace what we have. It is easy to upload from the shell to ftp. BUT, if you are uploading to shell, you may as well just ftp to download.sourceforge.net/incoming and let me know. > > C. > - -- > Christophe Prud'homme | Its name is Public Opinion. > MIT, 77, Mass Ave, Rm 3-243 | It is held in reverence. > Cambridge MA 02139 | It settles everything. > Tel (Office) : (00 1) (617) 253 0229 | Some think it is the voice of God. > Fax (Office) : (00 1) (617) 258 8559 | -- Mark Twain > http://augustine.mit.edu/~prudhomm | > Following the hacker spirit > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.0.4 (GNU/Linux) > Comment: For info see http://www.gnupg.org > > iEYEARECAAYFAjoHJ0oACgkQ4iUvDP8XyZLszQCfWwkQVnjcUTPlOgBVOwNXHWLC > 5bgAn18ppI73mDUtXN2/KXA7my02mm+O > =oTFO > -----END PGP SIGNATURE----- > _______________________________________________ > 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-11-06 21:49:37
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 > Heh, I was wondering about that. the 0.4.29 corelinux in packages/debian is for potato > > I take it that woody debs are not readable by potato systems? no, the problem comes from the libc which is not the same otherwise the installation will be fine. potato debs works on woody but the reverse might not be true. > > If they are, then I would say we replace the current with the woody built, the potato built you mean ? I think it is not possible to replace, on sourceforge, released files with the new ones with the same name. It has to be different. Am I wrong? > otherwise we will need -2 with a reasonable change to the download.php. I can do that. tell me ASAP I'll be here late. C. - -- Christophe Prud'homme | Its name is Public Opinion. MIT, 77, Mass Ave, Rm 3-243 | It is held in reverence. Cambridge MA 02139 | It settles everything. Tel (Office) : (00 1) (617) 253 0229 | Some think it is the voice of God. Fax (Office) : (00 1) (617) 258 8559 | -- Mark Twain http://augustine.mit.edu/~prudhomm | Following the hacker spirit -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4 (GNU/Linux) Comment: For info see http://www.gnupg.org iEYEARECAAYFAjoHJ0oACgkQ4iUvDP8XyZLszQCfWwkQVnjcUTPlOgBVOwNXHWLC 5bgAn18ppI73mDUtXN2/KXA7my02mm+O =oTFO -----END PGP SIGNATURE----- |
|
From: Frank V. C. <fr...@co...> - 2000-11-06 20:11:02
|
Heh, I was wondering about that. I take it that woody debs are not readable by potato systems? If they are, then I would say we replace the current with the woody built, otherwise we will need -2 with a reasonable change to the download.php. Frank Christophe Prud'homme wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > frank I realize that there might be a problem with corelinux deb update > the files are the same ! > tell me if I have to create 0.4.29-2 > > C. > - -- > Christophe Prud'homme | > MIT, 77, Mass Ave, Rm 3-243 | The Second Law of Thermodynamics: > Cambridge MA 02139 | If you think things are in a mess > Tel (Office) : (00 1) (617) 253 0229 | now, just wait! > Fax (Office) : (00 1) (617) 258 8559 | -- Jim Warner > http://augustine.mit.edu/~prudhomm | > Following the hacker spirit > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.0.4 (GNU/Linux) > Comment: For info see http://www.gnupg.org > > iEYEARECAAYFAjoHCdkACgkQ4iUvDP8XyZKtfQCbBFhSHWhFFJAYsprU4e4BJ2/C > H08Amwf/tSFx8jMzBSSnB+L3KmhVI5Bo > =0n7g > -----END PGP SIGNATURE----- > _______________________________________________ > Corelinux-develop mailing list > Cor...@li... > http://lists.sourceforge.net/mailman/listinfo/corelinux-develop |
|
From: Christophe Prud'h. <pru...@MI...> - 2000-11-06 19:43:30
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 frank I realize that there might be a problem with corelinux deb update the files are the same ! tell me if I have to create 0.4.29-2 C. - -- Christophe Prud'homme | MIT, 77, Mass Ave, Rm 3-243 | The Second Law of Thermodynamics: Cambridge MA 02139 | If you think things are in a mess Tel (Office) : (00 1) (617) 253 0229 | now, just wait! Fax (Office) : (00 1) (617) 258 8559 | -- Jim Warner http://augustine.mit.edu/~prudhomm | Following the hacker spirit -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4 (GNU/Linux) Comment: For info see http://www.gnupg.org iEYEARECAAYFAjoHCdkACgkQ4iUvDP8XyZKtfQCbBFhSHWhFFJAYsprU4e4BJ2/C H08Amwf/tSFx8jMzBSSnB+L3KmhVI5Bo =0n7g -----END PGP SIGNATURE----- |
|
From: Christophe Prud'h. <pru...@MI...> - 2000-11-06 19:33:24
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 debian update: the deb packages for clfw(0.2.4) have been uploaded the deb packages for corelinux(0.4.29) updated for potato so deb packages work for woody(unstable) and potato(stable). regards C. - -- Christophe Prud'homme | MIT, 77, Mass Ave, Rm 3-243 | I respect faith, but doubt is Cambridge MA 02139 | what gives you an education. Tel (Office) : (00 1) (617) 253 0229 | -- Wilson Mizner Fax (Office) : (00 1) (617) 258 8559 | http://augustine.mit.edu/~prudhomm | Following the hacker spirit -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4 (GNU/Linux) Comment: For info see http://www.gnupg.org iEYEARECAAYFAjoHB4EACgkQ4iUvDP8XyZLILQCgrJVN4aQcAkrNMayo1zVVmG8b YUMAnRtivjXVr3ZfQK0okF3T+ZnSWOdC =xNXq -----END PGP SIGNATURE----- |
|
From: Frank V. C. <fr...@co...> - 2000-11-06 15:50:26
|
Yes, I keep thinking you are gone (stupid me), feel free to create them. When I get back home I will ftp them to sourceforge and update the download.php Thanks, Frank PS: No, no one contacted me but I think I realized that debian compresses the files into the *.deb package, no? Christophe Prud'homme wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > new release ? > > shall I make the deb ? > > did you receive words from debian users that the packages are bad ? > > 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 > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.0.4 (GNU/Linux) > Comment: For info see http://www.gnupg.org > > iEYEARECAAYFAjoGx88ACgkQ4iUvDP8XyZL9/QCggxelxRkKurrUW2TysZh8qr3F > prsAn25t9yQCe7mxIu+1S6Se4pmoUnMu > =qBjU > -----END PGP SIGNATURE----- > _______________________________________________ > Corelinux-develop mailing list > Cor...@li... > http://lists.sourceforge.net/mailman/listinfo/corelinux-develop |
|
From: Christophe Prud'h. <pru...@MI...> - 2000-11-06 15:05:16
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 new release ? shall I make the deb ? did you receive words from debian users that the packages are bad ? 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 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4 (GNU/Linux) Comment: For info see http://www.gnupg.org iEYEARECAAYFAjoGx88ACgkQ4iUvDP8XyZL9/QCggxelxRkKurrUW2TysZh8qr3F prsAn25t9yQCe7mxIu+1S6Se4pmoUnMu =qBjU -----END PGP SIGNATURE----- |
|
From: Frank V. C. <fr...@co...> - 2000-11-04 21:10:00
|
Hans, Sounds about right. But I admit my mind has been elsewhere. When you come up with a pseudo block or something lets hash it out. Hans - Dulimarta wrote: > > I have been working on fixing the EventSemaphore bug again. The deadlock > occured when the event listeners do a lock while the event owner is > exiting. > > Going back to Frank's mail I found in September archive convinced me that > "EvenSemaphore::Post" method has to written. This method also serves as an > "agreement" between the event owner and listeners that the owner will > eventually trigger the event. > > What do you guys think? > > -- > 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-11-04 20:59:15
|
I have been working on fixing the EventSemaphore bug again. The deadlock occured when the event listeners do a lock while the event owner is exiting. Going back to Frank's mail I found in September archive convinced me that "EvenSemaphore::Post" method has to written. This method also serves as an "agreement" between the event owner and listeners that the owner will eventually trigger the event. What do you guys think? -- 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-11-03 22:45:22
|
Christophe Prud'homme wrote: > > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On Tuesday 31 October 2000 11:39, you wrote: > > Christophe managed to build the packages, I don't know if he is flying > > over Spain or huddled in some shack in the swamps of Jersey, but he came > > through! > :) > > actually I am very silent these days because unfortunately I am not as > scalable as I wish :( > but once I am on vacation I will have my brain back :) > and it happens at the end of next week > > C. > - -- Not to worry. I have a few releases coming up in about a week, the debians can lag a bit. The REAL QUESTION is: There are some great coding opportunties in all of this if you want to take and run with the ball with them on your vacation. -- Frank V. Castellucci |
|
From: Christophe Prud'h. <pru...@MI...> - 2000-11-03 21:46:50
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Tuesday 31 October 2000 11:39, you wrote: > Christophe managed to build the packages, I don't know if he is flying > over Spain or huddled in some shack in the swamps of Jersey, but he came > through! :) actually I am very silent these days because unfortunately I am not as scalable as I wish :( but once I am on vacation I will have my brain back :) and it happens at the end of next week C. - -- Christophe Prud'homme | Its name is Public Opinion. MIT, 77, Mass Ave, Rm 3-243 | It is held in reverence. Cambridge MA 02139 | It settles everything. Tel (Office) : (00 1) (617) 253 0229 | Some think it is the voice of God. Fax (Office) : (00 1) (617) 258 8559 | -- Mark Twain http://augustine.mit.edu/~prudhomm | Following the hacker spirit -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4 (GNU/Linux) Comment: For info see http://www.gnupg.org iEYEARECAAYFAjoDMkQACgkQ4iUvDP8XyZJ6JwCdGVpvLsHCS/YOlF1x0WI4aWCu JTQAmQFelMNiiDkj2KRTjaiKDW9z4QEG =q4vg -----END PGP SIGNATURE----- |
1115 messages has been excluded from this view by a project administrator.
