Martin Rubey wrote:
> 
> Waldek Hebisch <[EMAIL PROTECTED]> writes:
> 
> > It also makes harder to track changes to categories.
> 
> Don't understand this one.
>

svn tells us the last revision in which given file changed and
keeps log of changes.  If we have non-code changes or
changes which do not affect functionality then trying to find
out which patch caused some change in functionality requires
"filtering out noise".
 
> > 3) In practice we test domains and packages: while some functions
> > are implemented in categories we can test them only via domains.
> > Also, good test _should_ depend on implementation: we should test
> > for known/suspected weak spots of implementation, we should aim
> > for full coverage...  Putting tests in categories moves
> > implemention information into wrong place.
> 
> I'm quite sure that this is not true.  Tests should *not* know
> about implementation, because otherwise I'll possibly
> unconsciously test only things that work anyway.  (Happened to me
> once...)
> 

Googling for "Test coverage" should explain the issue.  There
are dangers of using _only_ tests based on implementation, but
using only black-box tests is even more dangerous.

> > Concerning trigcat, some parts of change looks undesirable (as
> > explained above), other are positive.  If change is limited to
> > trigcat, then probably this is not worth long discussion --
> > just go on.
> 
> 
> > OTOH, if you plan more changes of this sort I would ask you to
> > reconsider.
> 
> Hm, yes, I plan more changes of this sort.  I see two possible
> compromises:  
> 
> 1) we have a branch, where I structure files as I currently
>    envision.  trunk contains the input file already extracted in
>    src/input.
> 
> 2) I commit this change, and we rediscuss before the next change
>    (which will possibly be power series, and will probably *not*
>    happen in near future.)
> 
> In case of (1), please set up a branch.
> 

Since we were taking about branch a few times I have set up one
for you.  For the record the command to do this was:

svn copy https://fricas.svn.sourceforge.net/svnroot/fricas/trunk 
https://fricas.svn.sourceforge.net/svnroot/fricas/branches/martin-sandbox

However, I leave it up to you choice between 1 and 2.

-- 
                              Waldek Hebisch
[EMAIL PROTECTED] 

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"FriCAS - computer algebra system" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/fricas-devel?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to