On Wed, 15 Jul 2009 04:40:07 +0200, Alan Grimes <agri...@speakeasy.net>
wrote:
> aah! You catch on! =)
>
A few other ideas I forgot to write down:
As implementation, the matrix.h header could be reused, and only the
private part must be changed in it, as the implementation can be placed in
other .cpp file as matrix.cpp. To do this, all the inline implementations
should be removed from the header's public section. It's not a big
problem, still, that famous "g" method is undocumented for the moment...
/Me wrote:
> Yet another question: what is supposed the Matrix::g(CUI, CUI) method
> to
> do? By looking at the code, it's not obvious to me.
Another note: the second definition,
double g(CUI i, CUI j) const { return m_mat->at(m_inMap[i], j); }
is not used at all in the project, so something stange is going on
(again).
Bonus: the example 555 circuit ( hepl -> examples -> 555s -> internals )
makes ktechlab to write tons of "invalid matrix!!!" messages. What's
broken?
------------------------------------------------------------------------------
Enter the BlackBerry Developer Challenge
This is your chance to win up to $100,000 in prizes! For a limited time,
vendors submitting new applications to BlackBerry App World(TM) will have
the opportunity to enter the BlackBerry Developer Challenge. See full prize
details at: http://p.sf.net/sfu/Challenge
_______________________________________________
Ktechlab-devel mailing list
Ktechlab-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ktechlab-devel
