gnash-commit
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Gnash-commit] gnash ChangeLog doc/C/internals.xml


From: strk
Subject: Re: [Gnash-commit] gnash ChangeLog doc/C/internals.xml
Date: Wed, 7 Mar 2007 16:55:30 +0100

On Wed, Mar 07, 2007 at 10:52:02AM +0100, ann wrote:
> On Tue, 6 Mar 2007, Rob Savoye wrote:
> 
> >strk wrote:
> >>On Tue, Mar 06, 2007 at 08:46:12AM +0100, ann wrote:
> >
> >>Ehm... can we avoid complete examples ?
> >
> > Most people are too lazy to read the code for examples, so putting
> >them in the manual seemed a good idea at the time. I guess maintaining
> >them is a pain in the neck, but in this case, hopefully how objects get
> >instantiated in the VM will stop changing. :-) I do think that if
> >examples are in manuals, they should be real code, and kept up to date.
> 
> I think that it is worth having one class which can be considered a sort
> of flagship.  This would contain the most current interface and the cleanest
> code.

I'd say the cleanest and simpest would be Boolean.cpp, except from
the static casts, to be changed into calls to ensureBoolean().

--strk;





reply via email to

[Prev in Thread] Current Thread [Next in Thread]