* stephane eranian <eran...@googlemail.com> wrote:
> > Spreading them all out into architecture code is the far worse
> > solution, it creates a fragile distributed monster with repeating
> > patterns - instead we want a manageable central monster ;-) [We are
> > also quite good at controlling and shrinking monsters in the core
> > kernel.]
>
> I don't understand this either.
> Why would architecture specific code be more fragile ?
Because similar code spread out and partly duplicated in 22
architectures is an order of magnitude less maintainable than
a core library.
Ingo
------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
perfmon2-devel mailing list
perfmon2-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/perfmon2-devel
