2009/4/2 Stéphane Bisinger <stephane.bisin...@gmail.com> > 2009/4/2 Youness Alaoui <kakar...@kakaroto.homelinux.net>: > > [Solution to every mistery on earth] > > You pwnd me :O
lol :) > > > >> > >> Workarounds like yours are fine, but a full understanding of the issue > >> would be advisable: it leads to better solutions. > > > > Actually, I disagree.. workarounds are fine for TESTING, but I would > REALLY > > like aMSN2 to be as clean as possible, no hacks anywhere! And I know that > > Ali Sabil (original pymsn author) wrote the whole pymsn library with > exactly > > this idea in mind, he did a lot of engineering to make sure there would > be > > no hacks anywhere in the code, so trying to fix the thing correctly is > the > > best solution... I think my tips above should help you enough in fixing > > this! > > My bad, I didn't express clearly enough what I meant: workarounds are > fine to the single user who has an issue, but to solve a problem > permanently you have to fully understand the issue. I didn't mean > "Workarounds are fine for inclusion in the main branch", the only > reason they could be there is if there is a really severe issue which > for some reason cannot be fixed in short time and it affects many > users: in that case a workaround can be a way to earn time to resolve > the issue. I think we basically agree ;) Yeah, we both agree! :) Sorry about that ;) > > > -- > Stéphane > > > ------------------------------------------------------------------------------ > _______________________________________________ > Amsn-devel mailing list > Amsn-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/amsn-devel >
------------------------------------------------------------------------------
_______________________________________________ Amsn-devel mailing list Amsn-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amsn-devel
