Sha256: d5015f0ec260392f6997d96bd19a7565ab7769d6a39ef6e58fda91f892cf5f5f
Contents?: true
Size: 1.51 KB
Versions: 75
Compression:
Stored size: 1.51 KB
Contents
# Robot Name Manage robot factory settings. When robots come off the factory floor, they have no name. The first time you boot them up, a random name is generated in the format of two uppercase letters followed by three digits, such as RX837 or BC811. Every once in a while we need to reset a robot to its factory settings, which means that their name gets wiped. The next time you ask, it will respond with a new random name. The names must be random: they should not follow a predictable sequence. Random names means a risk of collisions. Your solution must ensure that every existing robot has a unique name. ## Setup There are two different methods of getting set up to run the tests with Objective-C: - Create an Xcode project with a test target which will run the tests. - Use the ruby gem `objc` as a test runner utility. Both are described in more detail here: http://exercism.io/languages/objective-c ### Submitting Exercises When submitting an exercise, make sure your solution file is in the same directory as the test code. The submit command will look something like: ```shell exercism submit <path-to-exercism-workspace>/objective-c/robot-name/RobotName.m ``` You can find the Exercism workspace by running `exercism debug` and looking for the line beginning with Workspace. ## Source A debugging session with Paul Blackwell at gSchool. [http://gschool.it](http://gschool.it) ## Submitting Incomplete Solutions It's possible to submit an incomplete solution so you can see how others have completed the exercise.
Version data entries
75 entries across 75 versions & 1 rubygems