From: Eric E. A. <eri...@ma...> - 2002-08-12 19:18:07
|
> However, this does pose an interesting dilemma still for testing. We > would > still need to have both versions of JSR14 available if we were to write > testcases to handle each situation, no? (Eric?) What do we presently > do to > ensure that platform specific bugs don't propogate? My understanding is that we would then have two implementations of IFoo (one for each version of JSR14), and each implementation would be a simple adapter, right? In that case, the methods in the adapters would be simple forwarding methods, and they should never change, so I think it's okay if we don't include unit tests for them (we should be able to verify when they're written that they can't possibly break). Then we can test the rest of the code with just one of the two adapters, or even a mock object adapter if we want to test some of the client code in isolation. Of course, the mock object would not help to test the logic for reflectively instantiating an adapter... -- Eric > > Just some thoughts before bed... > > theo:) > > p.s. I had sent that previous message because it's evil how close > Ctrl-X and > Ctrl-C are on the keyboard (Pine shortcuts). I had originally meant to > cancel > the message and draft one later... but you guys saw what happenned :-D > > On Sun, 11 Aug 2002, Charles Reis wrote: > >> Date: Sun, 11 Aug 2002 22:49:33 -0500 >> From: Charles Reis <cr...@ri...> >> To: Brian Stoler <bs...@bs...> >> Cc: drj...@li... >> Subject: Re: [DrJava] ack re jsr14 1.2 >> >> Rather than compiling against the JSR-14 v1.0/v1.2 compilers directly, >> couldn't we just invoke their compile, etc, methods using reflection? >> Then we don't have to worry about this if the compiler interface >> changes >> yet again-- we just "invoke" a different method... >> >> I'm not entirely against the other method (some classes only compile in >> some environments), but I'd like to allow everyone to be able to >> compile >> everything as long as we can, if possible... >> >> Of course, if reflection isn't an option, I think we'd have to do that >> anyway-- JSR-14 v1.0 isn't available anymore, so only people who have >> an >> old copy could compile DrJava if we went the route of requiring both. >> (And we've already gotten complaints from people outside Rice who want >> to compile. Rightfully so...) >> >> Charlie >> >> >> >> ------------------------------------------------------- >> This sf.net email is sponsored by:ThinkGeek >> Welcome to geek heaven. >> http://thinkgeek.com/sf >> _______________________________________________ >> drjava-hackers mailing list >> drj...@li... >> https://lists.sourceforge.net/lists/listinfo/drjava-hackers >> > > > > ------------------------------------------------------- > This sf.net email is sponsored by:ThinkGeek > Welcome to geek heaven. > http://thinkgeek.com/sf > _______________________________________________ > drjava-hackers mailing list > drj...@li... > https://lists.sourceforge.net/lists/listinfo/drjava-hackers |