Re: [Simulavr-devel] Settings for stackpointer

[Klaus Rudolph]

Can we please stop having meta discussions here!

If we have a design problem in simulavr which makes it hard to implement 
variants of features, we should fix this. But overwriting features with other 
features is not longer acceptable. There are enough features which are lost in 
the last time without any need.

So if someone have a problem with adding new things or want to adapt the 
software for own needs, so do it in a way which not break the needs of other 
users. Again: If there is a general problem in adding new things without 
breaking old ones, we should clean up the interfaces BEFORE we simply break 
again existing code.

Open Source did not mean that the last committer has the best ideas.

Regards
 Klaus


> Gesendet: Dienstag, 23. Februar 2016 um 01:32 Uhr
> Von: "Markus Hitter" <address@hidden>
> An: address@hidden
> Betreff: Re: [Simulavr-devel] Settings for stackpointer
>
> Am 23.02.2016 um 01:16 schrieb Petr Hluzín:
> > IMO the reason of algorithm testing and examples for learning are fantasy.
> 
> D'oh. So we're doing fantasy:
> 
> http://reprap.org/wiki/Teacup_Firmware#Teacup_in_SimulAVR
> 
> It's also used to run semi-automated regression tests for the firmware:
> 
> https://github.com/Traumflug/Teacup_Firmware/blob/master/testcases/run-in-simulavr.sh
> https://github.com/Traumflug/Teacup_Firmware/commit/808f5dcfca7b71b44ac35f3baa4d7c81c4673020
> 
> 
> Markus
> 
> -- 
> - - - - - - - - - - - - - - - - - - -
> Dipl. Ing. (FH) Markus Hitter
> http://www.jump-ing.de/
> 
> _______________________________________________
> Simulavr-devel mailing list
> address@hidden
> https://lists.nongnu.org/mailman/listinfo/simulavr-devel
>