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

[Corelinux-develop] meta class

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

Hie
my understanding of the requirements for meta class is that
it provides :
1- traits: static features of a type (traits were originally defined by    
Nathan   Meyers)
2- more sophisticated RTTI

it my codes I have, I think, something like that for point 2
all objects are clearly defined within a hierarchy of class and each of them
defines isTypeOf(char*), getClassName() , isA(char*) and the parent,child is 
defined.

for point 1 traits are a very powerful and simple technique to store static 
features and I use them very often.

here is a simple example

template<int Dim, int charSize=8, typename T=double>
class traits
{
public:
 enum { dimension = Dim };
 enum { char_size  = charSize };
 typedef T T_numtype;
};

template<typename Traits>
class A
{
 public:
 enum { dimension = Traits::dimension };
 enum { char_size = Traits::char_size };
 typedef typename Traits::T_numtype T_numtype;
};
	
template<int Dim>
class B: public A<traits<Dim> >
{
 public:
 typedef  A<Traits<Dim> > super;
 enum { dimension = super::dimension };
 enum { char_size = super::char_size };
 typedef typename super::T_numtype T_numtype;
};
	


am I correct in that it is providing 1 and 2 ?
C.

-- 
 Christophe Prud'homme                |
 MIT, 77, Mass Ave, Rm 3-243          |  C'est de la buche?
 Cambridge MA 02139                   |  Non c'est kloug!
 Tel (Office) : (00 1) (617) 253 0229 |  C'est colmatté avec du schpountz...
 Fax (Office) : (00 1) (617) 258 8559 |  -- Le Pere Noel est une ordure
 http://augustine.mit.edu/~prudhomm   |
                          Following the hacker spirit

[Corelinux-develop] Fwd: Comments and question on the corelinux++ coding standards

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

----------  Forwarded Message  ----------
Subject: Comments and question on the corelinux++ coding standards
Date: Tue, 5 Sep 2000 14:52:48 +0100 (GMT+01:00)
From: Robert Marshall <ra...@fs...>
To: pru...@us...


I've used this document as a basis for designing our own standards (thanks
 very much). I hope you don't mind if I ask some questions and make a few
 comments on that document.

- standard 1 referes to the Venice coding standards. Is this a publically
 available document? I couldn't find any references to it on the internet. -
 Guideline 16 is really a rationale for the previous standard (33) rather
 than a guideline in itself.

- the formatting of the html makes the examples in standards 34-36
 meaningless. - Standard 60 and guideline 40 seem to be in conflict
- standard 67, I'd add the words `and unimplemented' to the second sentence
 for clarity. - the reference to sourceware.cygnus.com is dated with the
 takeover by redhat. Again couldn't find the template standards being
 referred to here, if you could point me in the right direction I'd be very
 grateful! - Have grave doubts about standard 114 with the current state of
 exception specification support. I'm curious that namespace and template
 mention is very scant but there's this reference. - The bibliography appears
 to reference itself (I suppose though it tells you where to get the
 original) - I'm looking at developing standards for the use of the STL do
 you know of any existing guidelines for this. - the comments to webmaster at
 the foot of the page refers to sourcefforge. (apologies if this was a
 deliberate spam beater) - miscellaneous typographical errors.

Thanks for reading this far!

Robert





_______________________________________________________________________
FSmail - Get your free web-based email from Freeserve: www.fsmail.net

-------------------------------------------------------

-- 
  Christophe Prud'homme                  |
  MIT, 77, Mass Ave, Rm 3-243            |   If it doesn't work, force it.
  Cambridge MA 02139                     |   If it breaks, it needed
  Tel (Office) : (00 1) (617) 253 0229   |   replacing anyway.
  Fax (Office) : (00 1) (617) 258 8559   |
  http://augustine.mit.edu/~prudhomm     |
                          Following the hacker spirit

Re: [Corelinux-develop] don't find the problem with pdf or ps

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

Hans - Dulimarta wrote:
> 
> On Mon, 4 Sep 2000, Frank V. Castellucci wrote:
> 
> > Date: Mon, 04 Sep 2000 16:17:46 -0400
> > From: Frank V. Castellucci <fr...@co...>
> > Reply-To: cor...@li...
> > To: cor...@li...
> > Subject: Re: [Corelinux-develop] don't find the problem with pdf or ps
> >
> > Hans, please hold back any check-ins until I have a chance to tag the
> > current tree with rel-0-4-27. I won't do this until I have a release up
> > on SourceForge.
> >
> 
> OK, I'll wait for your cue.

Ok, 0.4.27 is tagged, I updated configure.in to hold the 0.4.28 build
number so you are free to check-in at any time.

> 
>  > I really wish SourceForge provided a more robust configuration
> > management system, but it didn't. Oh well.
> >
> > Thanks
> >
> > PS: I was able to do the same, although the pdf and ps are (by C.
> > definition) handled differently.
> >
> 
> --
> 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

Re: [Corelinux-develop] don't find the problem with pdf or ps

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

On Mon, 4 Sep 2000, Frank V. Castellucci wrote:

> Date: Mon, 04 Sep 2000 16:17:46 -0400
> From: Frank V. Castellucci <fr...@co...>
> Reply-To: cor...@li...
> To: cor...@li...
> Subject: Re: [Corelinux-develop] don't find the problem with pdf or ps
> 
> Hans, please hold back any check-ins until I have a chance to tag the
> current tree with rel-0-4-27. I won't do this until I have a release up
> on SourceForge.
>

OK, I'll wait for your cue.

 > I really wish SourceForge provided a more robust configuration
> management system, but it didn't. Oh well.
> 
> Thanks
> 
> PS: I was able to do the same, although the pdf and ps are (by C.
> definition) handled differently.
> 

-- 
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] corelinux 0.4.27 and clfw 0.1.0 announce

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

Hie all,

The corelinux library 0.4.27 and the initial release of the corelinux 
framework library 0.1.0 has been released.

Soooo What's New? 

** Corelinux 0.4.27
===================
o Feature 113271 : added a libcorelinux-dbg package for debian
o Feature 112855 : Conformance of libcorelinux macros, this will break your   
  code if you used the CORELINUX macros               
(DECLARE_TYPE,DECLARE_CLASS,CORELINUX_LIST, CORELINUX_VECTOR, 
CORELINUX_STACK, CORELINUX_QUEUE, CORELINUX_SET, CORELINUX_MULTISET, 
CORELINUX_MAP, CORELINUX_MULTIMAP) please have a look at the developer manual 
which has been updated.
o Defect 112703 : Changes for gcc 2.96.x conformance
o Feature 112020 : added the examples documentation into the ref manual

** clfw 0.1.0
=============
o the Initial release of the LibLoad module has been released in clfw.

** The future
=============
o Work has started also on metaclass.
o Event semaphore in corelinux (thanks to Hans)

Don't hesitate to drop some comments, ideas ....

For the debian users here is a cool apt line:

deb http://augustine.mit.edu/~prudhomm/debian ./ 

best regards
C.
-- 
 Christophe Prud'homme                | Pierre: Je suis désolé Thérèse, je ne
 MIT, 77, Mass Ave, Rm 3-243          |         sais pas ce qui m'a pris...
 Cambridge MA 02139                   |         c'est une catastrophe.
 Tel (Office) : (00 1) (617) 253 0229 | Thérèse: Ce n'est rien Pierre,
 Fax (Office) : (00 1) (617) 258 8559 |          je n'ai rien senti....
 http://augustine.mit.edu/~prudhomm   | -- Le Pere Noel est une ordure
                          Following the hacker spirit

Re: [Corelinux-develop] don't find the problem with pdf or ps

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

Hans, please hold back any check-ins until I have a chance to tag the
current tree with rel-0-4-27. I won't do this until I have a release up
on SourceForge.

I really wish SourceForge provided a more robust configuration
management system, but it didn't. Oh well.

Thanks

PS: I was able to do the same, although the pdf and ps are (by C.
definition) handled differently.

Hans - Dulimarta wrote:
> 
> On Sat, 2 Sep 2000, Frank V. Castellucci wrote:
> 
> > Date: Sat, 02 Sep 2000 23:50:02 -0400
> > From: Frank V. Castellucci <fr...@co...>
> > Reply-To: cor...@li...
> > To: cor...@li...
> > Subject: Re: [Corelinux-develop] don't find the problem with pdf or ps
> >
> > Christophe Prud'homme wrote:
> > >
> > > On Sat, 02 Sep 2000, you wrote:
> > > > Christophe Prud'homme wrote:
> > > > > > Where do I remod the batch file?
> > > > >
> > > > > what is remod ?
> > > >
> > > > I don't know, that was your original note "remod the \batchmode"
> > > :)
> > > remod=remove
> > >
> > > > But all the files are removed as the *.rpms are written, everything is
> > > > cleaned up.
> > >
> > > and if you just do a configure and go in doc/ and try the doxygen command
> > > does it work correctly or does it fail as well as the rpm ?
> > >
> >
> > Yes it fails, I have attached the log (I removed \batchmode as you
> > suggested). There seems to be a large number of errors which I can't
> > discern due to my incompetence with tex stuff.
> >
> >
> 
> Everything seems ok on my machine. This is what I did:
> 
> cd corelinux/doc
> doxygen corelinux.cfg
> cd latex
> [remove \batchmode from refman.tex]
> make
> 
> --
> 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

Re: [Corelinux-develop] don't find the problem with pdf or ps

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

On Sat, 2 Sep 2000, Frank V. Castellucci wrote:

> Date: Sat, 02 Sep 2000 23:50:02 -0400
> From: Frank V. Castellucci <fr...@co...>
> Reply-To: cor...@li...
> To: cor...@li...
> Subject: Re: [Corelinux-develop] don't find the problem with pdf or ps
> 
> Christophe Prud'homme wrote:
> > 
> > On Sat, 02 Sep 2000, you wrote:
> > > Christophe Prud'homme wrote:
> > > > > Where do I remod the batch file?
> > > >
> > > > what is remod ?
> > >
> > > I don't know, that was your original note "remod the \batchmode"
> > :)
> > remod=remove
> > 
> > > But all the files are removed as the *.rpms are written, everything is
> > > cleaned up.
> > 
> > and if you just do a configure and go in doc/ and try the doxygen command
> > does it work correctly or does it fail as well as the rpm ?
> > 
> 
> Yes it fails, I have attached the log (I removed \batchmode as you
> suggested). There seems to be a large number of errors which I can't
> discern due to my incompetence with tex stuff.
> 
> 

Everything seems ok on my machine. This is what I did:

cd corelinux/doc
doxygen corelinux.cfg
cd latex
[remove \batchmode from refman.tex]
make

-- 
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] ok found the problem

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

The problem is not doxygen but your tex configuration

corelinux++ documentation is SO big that your TeX config cannot handle it 
anymore. 

Frank: Argh!
Christophe: no no problem we have to change your tex config
Frank: is that some strange TeX arcane ?
Christophe: Ugh yes it is but we can meet on irc and do this togoether
  I have the config on my machine

by config I mean a file called texmf.cnf 
we have to change certains settings (memory settings)

do you want to do that?

going back to the previous version may work since there are less classes and 
graphics to handle but you will have the problem in the future since the 
documentation is growing constantly

C.
-- 
   Christophe Prud'homme                  |
   MIT, 77, Mass Ave, Rm 3-243            |   Un prud'homme était un homme
   Cambridge MA 02139                     |   d'honneur et de valeur,
   Tel (Office) : (00 1) (617) 253 0229   |   sage et loyal.
   Fax (Office) : (00 1) (617) 258 8559   |   -- Chateaubriand
   http://augustine.mit.edu/~prudhomm     |
                          Following the hacker spirit

Re: [Corelinux-develop] don't find the problem with pdf or ps

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

Christophe Prud'homme wrote:
> 
> On Sat, 02 Sep 2000, you wrote:
> > Christophe Prud'homme wrote:
> > > > Where do I remod the batch file?
> > >
> > > what is remod ?
> >
> > I don't know, that was your original note "remod the \batchmode"
> :)
> remod=remove
> 
> > But all the files are removed as the *.rpms are written, everything is
> > cleaned up.
> 
> and if you just do a configure and go in doc/ and try the doxygen command
> does it work correctly or does it fail as well as the rpm ?
> 

Yes it fails, I have attached the log (I removed \batchmode as you
suggested). There seems to be a large number of errors which I can't
discern due to my incompetence with tex stuff.

-- 
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] don't find the problem with pdf or ps

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

Christophe Prud'homme wrote:
> 
> On Sat, 02 Sep 2000, you wrote:
> > Christophe Prud'homme wrote:
> > > > Where do I remod the batch file?
> > >
> > > what is remod ?
> >
> > I don't know, that was your original note "remod the \batchmode"
> :)
> remod=remove
> 
> > But all the files are removed as the *.rpms are written, everything is
> > cleaned up.
> 
> and if you just do a configure and go in doc/ and try the doxygen command
> does it work correctly or does it fail as well as the rpm ?

Ah, ok, forgive my ignorance, I will try that.

-- 
Frank V. Castellucci

Re: [Corelinux-develop] don't find the problem with pdf or ps

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

On Sat, 02 Sep 2000, you wrote:
> Christophe Prud'homme wrote:
> > > Where do I remod the batch file?
> >
> > what is remod ?
>
> I don't know, that was your original note "remod the \batchmode"
:)
remod=remove



> But all the files are removed as the *.rpms are written, everything is
> cleaned up.

and if you just do a configure and go in doc/ and try the doxygen command
does it work correctly or does it fail as well as the rpm ?

-- 
 Christophe Prud'homme                |
 MIT, 77, Mass Ave, Rm 3-243          |  C'est de la buche?
 Cambridge MA 02139                   |  Non c'est kloug!
 Tel (Office) : (00 1) (617) 253 0229 |  C'est colmatté avec du schpountz...
 Fax (Office) : (00 1) (617) 258 8559 |  -- Le Pere Noel est une ordure
 http://augustine.mit.edu/~prudhomm   |
                          Following the hacker spirit

Re: [Corelinux-develop] don't find the problem with pdf or ps

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

Christophe Prud'homme wrote:
> 
> > Where do I remod the batch file?
> what is remod ?

I don't know, that was your original note "remod the \batchmode"

> you go in latex/
> edit refman.tex
> remove the \batchmode (first line)
> and try again

But all the files are removed as the *.rpms are written, everything is
cleaned up.

> 
> >
> > Let me ask you this first, if I restore the earlier version of
> > corelinux.cfg.in and re-run, do you think that would matter as, again, I
> > am running 1.2.0 of doxygen. It was working prior to this change.
> I don't think it is version related but well may be
> could you try to update? I just changed a few options in doxygen.cfg.in

Ok, I have 1.2.1 tar.gz, you want me to make doxygen, install, and try
building rpm again?

> 
> if you restore the file that should work for you
> but we lose the examples and the macros expansion
> 
> C.
> --
>   Christophe Prud'homme                 |
>   MIT, 77, Mass Ave, Rm 3-243           |   A wise person makes his own
>   Cambridge MA 02139                    |   decisions,
>   Tel (Office) : (00 1) (617) 253 0229  |   a weak one obeys public opinion.
>   Fax (Office) : (00 1) (617) 258 8559  |   -- Chinese proverb
>   http://augustine.mit.edu/~prudhomm    |
>                           Following the hacker spirit
> _______________________________________________
> Corelinux-develop mailing list
> Cor...@li...
> http://lists.sourceforge.net/mailman/listinfo/corelinux-develop

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

Re: [Corelinux-develop] don't find the problem with pdf or ps

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

> Where do I remod the batch file?
what is remod ?
you go in latex/
edit refman.tex
remove the \batchmode (first line)
and try again

>
> Let me ask you this first, if I restore the earlier version of
> corelinux.cfg.in and re-run, do you think that would matter as, again, I
> am running 1.2.0 of doxygen. It was working prior to this change.
I don't think it is version related but well may be
could you try to update? I just changed a few options in doxygen.cfg.in

if you restore the file that should work for you
but we lose the examples and the macros expansion

C.
-- 
  Christophe Prud'homme                 |
  MIT, 77, Mass Ave, Rm 3-243           |   A wise person makes his own
  Cambridge MA 02139                    |   decisions,
  Tel (Office) : (00 1) (617) 253 0229  |   a weak one obeys public opinion.
  Fax (Office) : (00 1) (617) 258 8559  |   -- Chinese proverb
  http://augustine.mit.edu/~prudhomm    |
                          Following the hacker spirit

Re: [Corelinux-develop] don't find the problem with pdf or ps

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

Christophe Prud'homme wrote:
> 
> ok
> everything is fine for me so far
> dvi ps and pdf are working fine
> argh I don't like this when the behavior is not uniform
> 
> could you send me the log file compressed ?
> what you can do also is remod the \batchmode at the beginning of the tex file
> and rerun interactively
> you should see where it fails
> 

Where do I remod the batch file?

Let me ask you this first, if I restore the earlier version of
corelinux.cfg.in and re-run, do you think that would matter as, again, I
am running 1.2.0 of doxygen. It was working prior to this change.

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

[Corelinux-develop] debian packages

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

I am building the packages from scratch
and I am testing them locally

/home/groups/corelinux/packages/debian/

C.
-- 
  Christophe Prud'homme                  |
  MIT, 77, Mass Ave, Rm 3-243            |   As flies to wanton boys are we
  Cambridge MA 02139                     |   to the gods; they kill us for
  Tel (Office) : (00 1) (617) 253 0229   |   their sport.
  Fax (Office) : (00 1) (617) 258 8559   |   -- Shakespeare, "King Lear"
  http://augustine.mit.edu/~prudhomm     |
                          Following the hacker spirit

[Corelinux-develop] don't find the problem with pdf or ps

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

ok 
everything is fine for me so far
dvi ps and pdf are working fine
argh I don't like this when the behavior is not uniform

could you send me the log file compressed ?
what you can do also is remod the \batchmode at the beginning of the tex file
and rerun interactively
you should see where it fails

C.
-- 
   Christophe Prud'homme                  |
   MIT, 77, Mass Ave, Rm 3-243            |    Do nothing unless you must,
   Cambridge MA 02139                     |    and when you must act
   Tel (Office) : (00 1) (617) 253 0229   |    -- hesitate.
   Fax (Office) : (00 1) (617) 258 8559   |
   http://augustine.mit.edu/~prudhomm     |
                          Following the hacker spirit

Re: [Corelinux-develop] MetaClass feature opened

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

Hans Dulimarta wrote:
> 
> "Frank V. Castellucci" wrote:
> >
> > Ok,
> > I opened the MetaClass feature, metaclasses being classes of classes
> > <grin>.
> >
> > The clfw first release will not wait for this though, as it is not an
> > easy undertaking, but the FunctionLoader framework implementation WILL
> > have to wait.
> >
> > So,
> >
> > Hans  - should we go 0.4.27 with or without the initial EventSemaphore
> > work?
> 
> Go without EventSemaphore. I am in the middle of writing
> EventSemaphoreGroup
> and writing test suite. After everything is OK, I will
> commit the code.

Ok.

I hope I didn't mess up the works with the issues. I didn't mean for
them to imply that they should all be addressed before implementation of
what you were going with.

> 
> > Christophe - ready when you are, although the pdf and ps thingy is still
> > dangling out there.
> >
> > --
> > Frank V. Castellucci
> > http://corelinux.sourceforge.net
> > OOA/OOD/C++ Standards and Guidelines for Linux
> > http://PythPat.sourceforge.net
> > Pythons Pattern Package
> > _______________________________________________
> > Corelinux-develop mailing list
> > Cor...@li...
> > http://lists.sourceforge.net/mailman/listinfo/corelinux-develop
> 
> --
> Hans Dulimarta, Ph.D.                  dul...@co...
> P: 517-432-7589
> http://www.egr.msu.edu/~dulimart
> F: 760-281-7691             http://corelinux.sourceforge.net
> Elec. & Comp. Engg., Mich. State Univ., E. Lansing, MI 48824
> _______________________________________________
> Corelinux-develop mailing list
> Cor...@li...
> http://lists.sourceforge.net/mailman/listinfo/corelinux-develop

-- 
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] MetaClass feature opened

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

"Frank V. Castellucci" wrote:
> 
> Ok,
> I opened the MetaClass feature, metaclasses being classes of classes
> <grin>.
> 
> The clfw first release will not wait for this though, as it is not an
> easy undertaking, but the FunctionLoader framework implementation WILL
> have to wait.
> 
> So,
> 
> Hans  - should we go 0.4.27 with or without the initial EventSemaphore
> work?

Go without EventSemaphore. I am in the middle of writing
EventSemaphoreGroup
and writing test suite. After everything is OK, I will
commit the code.

> Christophe - ready when you are, although the pdf and ps thingy is still
> dangling out there.
> 
> --
> Frank V. Castellucci
> http://corelinux.sourceforge.net
> OOA/OOD/C++ Standards and Guidelines for Linux
> http://PythPat.sourceforge.net
> Pythons Pattern Package
> _______________________________________________
> Corelinux-develop mailing list
> Cor...@li...
> http://lists.sourceforge.net/mailman/listinfo/corelinux-develop

-- 
Hans Dulimarta, Ph.D.                  dul...@co...
P: 517-432-7589            
http://www.egr.msu.edu/~dulimart   
F: 760-281-7691             http://corelinux.sourceforge.net
Elec. & Comp. Engg., Mich. State Univ., E. Lansing, MI 48824

[Corelinux-develop] MetaClass feature opened

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

Ok,
I opened the MetaClass feature, metaclasses being classes of classes
<grin>.

The clfw first release will not wait for this though, as it is not an
easy undertaking, but the FunctionLoader framework implementation WILL
have to wait.

So,

Hans  - should we go 0.4.27 with or without the initial EventSemaphore
work?
Christophe - ready when you are, although the pdf and ps thingy is still
dangling out there.

-- 
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] Recursion of EventSemaphore is impossible

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

Hans - Dulimarta wrote:
> 
> On Fri, 1 Sep 2000, Frank V. Castellucci wrote:
> 
> > Date: Fri, 01 Sep 2000 07:09:28 -0400
> > From: Frank V. Castellucci <fr...@co...>
> > Reply-To: cor...@li...
> > To: cor...@li...
> > Subject: Re: [Corelinux-develop] Recursion of EventSemaphore is impossible
> >
> > Hans - Dulimarta wrote:
> > >
> > >
> > > I forgot to tell you that the implementation of the EventSemaphore
> > > is now different from what I proposed earlier.
> > >
> > > It was like this:
> > >
> > > Owner/Creator holds    --> setValue(1)   --> initialize sem to 1
> > > Listener waits         --> lock<XYZ>()   --> Z(s)
> > > Owner/Creator triggers --> release()     --> P(s)
> > >
> > > It is now like this:
> > >
> > > Owner/Creator holds    --> setValue(-1)  --> initialize sem to -1
> > > Listener waits         --> lock<XYZ>()   --> Z(s)
> > > Owner/Creator triggers --> release()     --> V(s)
> > >
> > > with
> > > Z(s) = kernel call to semop {..., 0, ...} via waitZero() [added function]
> > > P(s) = kernel call to semop {..., 1, ...} via setLock()
> > > V(s) = kernel call to semop {...,-1, ...} via setUnLock()
> > >
> > > with the new implementation the release() function looks natural.
> > >
> > > I view the lockWith{Wait,NoWait,Timeout}() as the wrapper of the
> > > Dijkstra's P() [or Z()] operation and release() as the wrapper of the V()
> > > operation. As defined, these P,V, [and Z] operations are atomic ones
> > > meaning that they are _interruptible_. With this definition, when the
> > > event is signalled, the triggering thread will run its release until
> > > completion (finishing "reset" and "cleanup") and then the listening
> > > thread(s) will get control. So when the listening thread immediately calls
> > > to register another lockWith<XYZ> again, this call will be made to the
> > > semaphore which is already reset and cleaned up and therefore it is not
> > > a recursive call.
> > >
> > > > 2. Some processes will require that they indicate an interest in the
> > > > event, but will come back later to see if it were signalled yet.
> > > >
> > >
> > > Are talking about the lockWithNoWait call?
> >
> > No, it is more like a "make a note that I am interested to know if the
> > semaphore has been released, and if so, how many times since I last
> > asked", this was a feature of OS/2 and subsequently WinNT semaphores. So
> > the listener :
> >
> > a) is not blocked when Z(s) is called even though they remain a
> > participant
> 
> The existing interface does not have this option. I think balking and
> recursion cannot be used for specifying this option. Perhaps, we should
> have a function that is called "registerEvent"
> 
> > b) has some indication (getReleaseCount()?) that the event has been
> > called n times since a reset
> >
> 
> I'll try to implement both of these features in release >= 0.4.28.

Yeah, good call. I agree.

> 
> > > --
> > > Hans Dulimarta, Ph.D.                  dul...@co...
> > > P: 517-432-7589             http://www.egr.msu.edu/~dulimart
> > > F: 760-281-7691             http://corelinux.sourceforge.net
> > > Elec. & Comp. Engg., Mich. State Univ., E. Lansing, MI 48824
> > >
> > > _______________________________________________
> > > Corelinux-develop mailing list
> > > Cor...@li...
> > > http://lists.sourceforge.net/mailman/listinfo/corelinux-develop
> >
> >
> 
> --
> Hans Dulimarta, Ph.D.                  dul...@co...
> P: 517-432-7589             http://www.egr.msu.edu/~dulimart
> F: 760-281-7691             http://corelinux.sourceforge.net
> Elec. & Comp. Engg., Mich. State Univ., E. Lansing, MI 48824
> 
> _______________________________________________
> Corelinux-develop mailing list
> Cor...@li...
> http://lists.sourceforge.net/mailman/listinfo/corelinux-develop

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

Re: [Corelinux-develop] Recursion of EventSemaphore is impossible

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

On Fri, 1 Sep 2000, Frank V. Castellucci wrote:

> Date: Fri, 01 Sep 2000 07:09:28 -0400
> From: Frank V. Castellucci <fr...@co...>
> Reply-To: cor...@li...
> To: cor...@li...
> Subject: Re: [Corelinux-develop] Recursion of EventSemaphore is impossible
> 
> Hans - Dulimarta wrote:
> > 
> > 
> > I forgot to tell you that the implementation of the EventSemaphore
> > is now different from what I proposed earlier.
> > 
> > It was like this:
> > 
> > Owner/Creator holds    --> setValue(1)   --> initialize sem to 1
> > Listener waits         --> lock<XYZ>()   --> Z(s)
> > Owner/Creator triggers --> release()     --> P(s)
> > 
> > It is now like this:
> > 
> > Owner/Creator holds    --> setValue(-1)  --> initialize sem to -1
> > Listener waits         --> lock<XYZ>()   --> Z(s)
> > Owner/Creator triggers --> release()     --> V(s)
> > 
> > with
> > Z(s) = kernel call to semop {..., 0, ...} via waitZero() [added function]
> > P(s) = kernel call to semop {..., 1, ...} via setLock()
> > V(s) = kernel call to semop {...,-1, ...} via setUnLock()
> > 
> > with the new implementation the release() function looks natural.
> > 
> > I view the lockWith{Wait,NoWait,Timeout}() as the wrapper of the
> > Dijkstra's P() [or Z()] operation and release() as the wrapper of the V()
> > operation. As defined, these P,V, [and Z] operations are atomic ones
> > meaning that they are _interruptible_. With this definition, when the
> > event is signalled, the triggering thread will run its release until
> > completion (finishing "reset" and "cleanup") and then the listening
> > thread(s) will get control. So when the listening thread immediately calls
> > to register another lockWith<XYZ> again, this call will be made to the
> > semaphore which is already reset and cleaned up and therefore it is not
> > a recursive call.
> > 
> > > 2. Some processes will require that they indicate an interest in the
> > > event, but will come back later to see if it were signalled yet.
> > >
> > 
> > Are talking about the lockWithNoWait call?
> 
> No, it is more like a "make a note that I am interested to know if the
> semaphore has been released, and if so, how many times since I last
> asked", this was a feature of OS/2 and subsequently WinNT semaphores. So
> the listener :
> 
> a) is not blocked when Z(s) is called even though they remain a
> participant 

The existing interface does not have this option. I think balking and
recursion cannot be used for specifying this option. Perhaps, we should
have a function that is called "registerEvent"

> b) has some indication (getReleaseCount()?) that the event has been
> called n times since a reset
>

I'll try to implement both of these features in release >= 0.4.28.

> > --
> > Hans Dulimarta, Ph.D.                  dul...@co...
> > P: 517-432-7589             http://www.egr.msu.edu/~dulimart
> > F: 760-281-7691             http://corelinux.sourceforge.net
> > Elec. & Comp. Engg., Mich. State Univ., E. Lansing, MI 48824
> > 
> > _______________________________________________
> > Corelinux-develop mailing list
> > Cor...@li...
> > http://lists.sourceforge.net/mailman/listinfo/corelinux-develop
> 
> 

-- 
Hans Dulimarta, Ph.D.                  dul...@co...
P: 517-432-7589             http://www.egr.msu.edu/~dulimart   
F: 760-281-7691             http://corelinux.sourceforge.net
Elec. & Comp. Engg., Mich. State Univ., E. Lansing, MI 48824

Re: [Corelinux-develop] Re: [Bug #113334] PDF and PS not bundled in corelinux-doc rpm

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

Christophe Prud'homme wrote:
> 
> > Comment:
> > Ok, the log for "make rpm" shows that the latex refman.tex is blowing up in
> > doc/latex, but it doesn't say why.
> >
> > make[1]: *** [refman.dvi] Error 1
> >
> > The results is that the ps and pdf files are not generated. Do you want the
> > zipped log? it is rather large and the only error that comes out is the one
> > I listed. -------------------------------------------------------
> well if I don't reproduce the error I will need the log file
> I will work on it tonight
> so I hope you'll be online if I need you :)
> 
> C.
> --

Yes I should be around. 

Hey, I think we may have to make the move to including a
mini-marshalling and declarative type system. I really am having a
difficult time in doing it any other way, mainly because, for reasoning,
a declarative meta-object is the right way.

This will, as you know, make describing things like
FunctionalObjectDefinitions much easier to implement and work with.

Thoughts?

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

[Corelinux-develop] Re: [Bug #113334] PDF and PS not bundled in corelinux-doc rpm

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

> Comment:
> Ok, the log for "make rpm" shows that the latex refman.tex is blowing up in
> doc/latex, but it doesn't say why.
>
> make[1]: *** [refman.dvi] Error 1
>
> The results is that the ps and pdf files are not generated. Do you want the
> zipped log? it is rather large and the only error that comes out is the one
> I listed. -------------------------------------------------------
well if I don't reproduce the error I will need the log file
I will work on it tonight
so I hope you'll be online if I need you :)

C.
-- 
  Christophe Prud'homme                  |
  MIT, 77, Mass Ave, Rm 3-243            |   If it doesn't work, force it.
  Cambridge MA 02139                     |   If it breaks, it needed
  Tel (Office) : (00 1) (617) 253 0229   |   replacing anyway.
  Fax (Office) : (00 1) (617) 258 8559   |
  http://augustine.mit.edu/~prudhomm     |
                          Following the hacker spirit

Re: [Corelinux-develop] release?

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

Christophe Prud'homme wrote:
> 
> > It seems that the doc-*.rpm is broken again. It doesn't include the PDF
> > or the PS (although the directories are there), and it now includes the
> > examples html. Did you change the cfg for doxygen or the spec file
> > somehow?
> >
> > If you do not respond I will take a look, if I can't figure I will post
> > a defect with your name on it :)
> Strange everything is fine so far with debian
> I'll check that
> 
> the huge changes you mentionned are not so huge, I just used the doxywizard
> provided by doxygen
> I just added the examples and the CORELINUX macros to the preprocessing system
> 
> C.
> --

You are right, they were not so huge, but when you first do a diff the
number, not the semantics, of change are what you are first presented
with. Sorry :)

-- 
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] release?

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

> It seems that the doc-*.rpm is broken again. It doesn't include the PDF
> or the PS (although the directories are there), and it now includes the
> examples html. Did you change the cfg for doxygen or the spec file
> somehow?
>
> If you do not respond I will take a look, if I can't figure I will post
> a defect with your name on it :)
Strange everything is fine so far with debian
I'll check that

the huge changes you mentionned are not so huge, I just used the doxywizard 
provided by doxygen
I just added the examples and the CORELINUX macros to the preprocessing system


C.
-- 
    Christophe Prud'homme                   |    So so is good, very good,
    MIT, 77, Mass Ave, Rm 3-243             |    very excellent good:
    Cambridge MA 02139                      |    and yet it is not;
    Tel (Office) : (00 1) (617) 253 0229    |    it is but so so.
    Fax (Office) : (00 1) (617) 258 8559    |    -- William Shakespeare,
    http://augustine.mit.edu/~prudhomm      |    "As You Like It"
                          Following the hacker spirit