On 31-Oct-08, at 12:28 AM, Stephen Bannasch wrote:
> But your otml still has the import for netlogo4 -- which is why this > error appears next:" It seems like its going to be pretty hard for developers to scan within layers of code and make sure they're all referencing up to date versions of everything - This may not be within the domain of unit testing, but is it possible to develop tests for a curnit that look through a table of things like this? I'm sure everyone wants to start getting away from scenarios like this one, where jennie is urgently running tomorrow, geoff up all night trying to figure out what's not working, COncord gets urgent last minutes e-mails about data not saving. .. In the next 6 -9 months, we'll have probably 12 or more classroom runs of WISE 3 projects - so I'm sure that expertise with o-trunk and everything else will build quickly amongst the team (including toronto - we'll be supporting a WISE 3 run down in purdue). SO this is just part of the learning curve, I guess. Meanwhile, thanks for your help Stephen! --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "SAIL-Dev" 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/SAIL-Dev?hl=en -~----------~----~----~----~------~----~------~--~---
