• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: OCUnit vs OBJCUnit
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: OCUnit vs OBJCUnit


  • Subject: Re: OCUnit vs OBJCUnit
  • From: Chris Ridd <email@hidden>
  • Date: Thu, 26 Jun 2003 13:53:17 +0100

On 26/6/03 8:24 am, Malte Tancred <email@hidden> wrote:
> Jiva DeVoe wrote:
>> Specifically however I was referring to how I always disliked that
>> OCUnit required an external script to run the test application. Or a
>> least it did when I used it. There are some good reasons to do this,
>> in particular when writing test frameworks for things like C++, which
>> doesn't have reflection capabilities.
>
> There's another reason to have an external runner. Objective C, just
> like C or C++, is a language where you can mess up badly. Think
> free(0x0).

In ISO C, calling free(NULL) is OK. But your point's still valid :-)

Cheers,

Chris
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.

  • Follow-Ups:
    • Re: OCUnit vs OBJCUnit
      • From: Malte Tancred <email@hidden>
References: 
 >Re: OCUnit vs OBJCUnit (From: Malte Tancred <email@hidden>)

  • Prev by Date: Re: OCUnit vs OBJCUnit
  • Next by Date: No window again
  • Previous by thread: Re: OCUnit vs OBJCUnit
  • Next by thread: Re: OCUnit vs OBJCUnit
  • Index(es):
    • Date
    • Thread