trackler 2.0.6.19 → 2.0.6.20

data/tracks/php/exercises/book-store/example.php

@@ -0,0 +1,38 @@
+<?php
+
+function total($items)
+{
+    return calculate($items, 0);
+}
+
+function calculate($items, $total)
+{
+    if (empty($items)) {
+        return $total;
+    }
+
+    $group = array_unique($items);
+    $totalMin = INF;
+
+    for ($i = count($group); $i > 0; $i--) {
+        $itemsToRemove = array_flip(array_slice($group, 0, $i));
+        $itemsRemaining = array_filter($items, function ($x) use (&$itemsToRemove) {
+            if (array_key_exists($x, $itemsToRemove)) {
+                unset($itemsToRemove[$x]);
+                return false;
+            }
+            return true;
+        });
+        $totalCurrent = calculate($itemsRemaining, $total + totalForGroup($i));
+        $totalMin = min([$totalMin, $totalCurrent]);
+    }
+
+    return $totalMin;
+}
+
+function totalForGroup($count)
+{
+    $discount = [0, 0, 0.05, 0.1, 0.2, 0.25];
+    $price = 8;
+    return $price * $count * (1 - $discount[$count]);
+}

data/tracks/swift/docs/TESTS.md

@@ -1,88 +1,93 @@
 ## Testing Tutorial
 
-This guide explains how to run unit tests for the Exercism Swift exercises using either macOS or Linux.
+This guide explains how to run unit tests for the Exercism Swift exercises using either macOS or Linux. It assumes you have already successfully installed the Exercism client and fetched the first exercise. If not, [do that now](http://exercism.io/languages/swift).
+
+#### For experienced users:
 
-### For experienced users:
 	1. `swift test` runs tests
 	2. `swift package generate-xcodeproj` creates an Xcode project
 	
-To run the tests from the command line, first `cd` to the directory for an exercise (for example, ~/exercism/swift/exercises/hello-world/), then execute `swift test`. This will compile the files in the Sources directory and execute the tests in the Tests directory. Alternatively, open the Xcode project and press Command-U.
+To run the tests from the command line, first `cd` to the exercise directory (for example, ~/exercism/swift/exercises/hello-world/), then execute `swift test`. This will compile the files in the Sources directory and execute the tests in the Tests directory. Alternatively, open the Xcode project and press Command-U.
 
 ### Overview
 
 The following instructions are written with the expectation that some readers will be very new to test driven development, Exercism, or Xcode. Each step is described in detail.
 
-**macOS users are encouraged to use Xcode.** The Xcode environment provides detailed error messages compared to those available from the command line.
+**macOS users are encouraged to use Xcode.** The Xcode environment provides very detailed error messages compared to those available from the command line.
 
-Exercism uses the [Swift Package Manager](https://github.com/apple/swift-package-manager/tree/master/Documentation) to package files and tests for Swift. Packages provide a complete set of source files that can be compiled and executed from the command line.
+Exercism uses the [Swift Package Manager](https://github.com/apple/swift-package-manager/tree/master/Documentation) to package files and tests for Swift. Packages provide a complete set of source files that can be compiled and executed from the command line (or from Xcode).
 
 To complete an Exercism exercise, you will work primarily with two files:
 
-* **Swift Source** (hello-world/Sources/HelloWorld.swift). This is the code file you will submit to Exercism.
-* **Test Source** (hello-world/Tests/HelloWorldTests/HelloWorldTest.swift). This file is provided by Exercism which contains the XCTestCase subclass that defines the solution to the exercise. You never edit this file, but you will have to understand it in order to fulfill its expectations.
+* **Swift Source** (hello-world/Sources/HelloWorld.swift). This is the code file you will submit to Exercism. Typically each exercise contains a Swift Source file with the same name as the project.
+* **Test Source** (hello-world/Tests/HelloWorldTests/HelloWorldTest.swift). This file is provided by Exercism. It contains the XCTestCase subclass that defines the solution to the exercise. You never edit this file, but you will have to understand it in order to fulfill its expectations.
 
 Optionally, Xcode can create a third file for experimentation:
 
-* **Playground** (MyPlayground.playground) is a scratchpad for drafting code snippets and playing with ideas. The code executes as you type, providing instant feedback.
+* **Playground** (MyPlayground.playground) is a scratchpad for drafting code and playing with ideas. The code executes as you type, providing instant feedback. It is not possible to call Exercism tests in a playground directly, so code must be copied to the Swift Source file before invoking the unit tests.
 
 
 ### Configuring Xcode
-1. `cd` to the directory for an exercise (for example, ~/exercism/swift/exercises/hello-world/), then execute `swift package generate-xcodeproj` in the Terminal. This creates an Xcode project in the current directory with the same name as the package. (The generated project file is ideal for unit tests, as it does not include overhead such as launching the iOS simulator or a target application.)
+1. In the Terminal `cd` to the directory for an exercise (for example, ~/exercism/swift/exercises/hello-world/), then execute `swift package generate-xcodeproj`. This creates an Xcode project in the current directory with the same name as the package. (The generated project is ideal for unit tests. It does not include the overhead of launching the iOS simulator or a target application.)
 2. Open the newly generated project file.
-3. At this point the project's file inspector should look similar to the following image. If the `HelloWorldTests` folder is closed, click on the disclosure triangle to reveal its contents.
-4. The items Package.swift, Configs, and Products are boilerplate that do not need modification.
+3. At this point the project's file inspector should look similar to the image below. If the `HelloWorldTests` folder is closed, click on the disclosure triangle to reveal its contents.
+4. When Xcode opens a project, typically it will build automatically. If there is an initial build error, press Shift-Command-K to clean the project followed by Command-B to build again. (Cleaning is a useful Xcode troubleshooting technique for all sorts of error conditions.)
+5. The items Package.swift, Configs, and Products are boilerplate that do not need modification.
+6. Congratulations! If the project builds successfully, configuration is complete.
 
 ![file inspector](/docs/img/file-inspector.png)
 
-### Running Tests with Xcode
+### Xcode Playgrounds
 
-Select the test file from the file inspector. You can trigger tests by clicking on one of the diamonds in the gutter of the Tests Source file. The diamond next to the class definition will run all the tests, whereas the diamond next to each individual test will run only that test.
+Playgrounds can be useful for brainstorming solutions to the problem. The playground continuously evaluates code as you type, displaying variable states and results almost immediately.
 
-![tests](/docs/img/tests.png)
+If you generated an Xcode project, follow these steps:
 
-Tests can also be invoked with Command-U, from the Test Inspector (Command-5), or from the sub-menu under the play button in the top bar. Red errors are normal at this stage.
+1. First, make sure to select the topmost item in the File Inspector, the item marked with a blue icon that represents the project file.
+2. Press Command-N and choose Playground from the template chooser. Click Next, and click Create.
 
-![failing tests](/docs/img/tests-fail.png)
+Keep in mind that while playgrounds are useful for drafting code snippets and ideas, code must be moved to the Swift Source file for testing and submission.
 
-Once all the tests are marked with a green icon, congratulations, you have successfully completed the exercise! Now submit it to the Exercism website for review. If you are impossibly stuck, submit the exercise before it is complete to view how other users solved the exercise.
+### Running Tests with Xcode
 
-![passing tests](/docs/img/tests-pass.png)
+Select the Tests Source file from the file inspector. You can trigger tests by clicking on one of the diamonds in the gutter of the file. The diamond next to the class definition will run all the tests, whereas the diamond next to each individual test will run only that test.
 
-*The Hello-World exercise is a very simple coding problem, but the complexity of Xcode can make even simple exercises complex. We can ignore most of this complexity, because we only need to edit one file. You can always regenerate the Xcode project if something goes wrong.*
+![tests](/docs/img/tests.png)
 
-### Xcode Playgrounds
+Tests can also be invoked with Command-U, from the Test Inspector (Command-5), or from the sub-menu under the play button in the top bar. Red errors alongside all the tests are normal, since you have not witten any code yet!
 
-Playgrounds can be useful for brainstorming solutions to the problem. The playground continuously evaluates code as you type, displaying variable states and results as you type.
+![failing tests](/docs/img/tests-fail.png)
 
-If you generated an Xcode project, follow these steps:
+Test driven development is a very iterative process. The first step is to successfully run the tests and have them fail. Next try "sliming a test" by creating a method that returns a correct hard coded value for the first test. Sliming will confirm the project can compile and pass one test.
 
-1. First, make sure to select the topmost item in the File Inspector, the item marked with a blue icon that represents the project file.
-2. Press Command-N and choose Playground from the template chooser. Click Next, and click Create.
+Next, replace the hard coded value with code that generates the expected return value and test again. Keep repeating this cycle until all the tests pass.
 
-Keep in mind that while playgrounds are useful for drafting code snippets and ideas, code must be moved to the Swift Source file for testing and submission.
+Remember that the exercise is solved with code in the application source file alone. As you enter your solution into the Swift Source file, Xcode will continuously update the display with errors that highlight code that will not compile.
 
-### How Tests Are Used
+Once all the tests are marked with a green icon, congratulations, you have successfully completed the exercise! Now submit it to the Exercism website for review. If you are impossibly stuck, submit the exercise before it is complete to view how other users solved the exercise.
 
-Test driven development is a very iterative process. The first step is to successfully run the tests and have them fail. Remember that the exercise can be solved with code in the application source file alone. Enter your solution into the Swift Source file. Xcode will continuously update the display with errors that highlight code that will not compile.
+![passing tests](/docs/img/tests-pass.png)
 
-One approach begins with "sliming a test" by creating a method that returns a correct hard coded value. Sliming will confirm the project can compile and pass one test. Next, replace the hard coded value with code that generates the expected return value and test again. Keep repeating this cycle until all the tests pass.
+*The Hello-World exercise is a very simple coding problem, but the complexity of Xcode can make even simple exercises complex. We can ignore most of this complexity, because we only need to edit one file. You can always regenerate the Xcode project if something goes wrong.*
 
 ## Submission
 
-1. In the Terminal, navigate to the folder that contains the application source file. In this example, the path would be `~/exercism/swift/hello-world/HelloWorld/HelloWorld/`
-2. To submit, type `exercism submit HelloWorld.swift` (_Alternatively, you can submit by using the file name with the full path from any directory. A second alternative is to locate the file you need to submit in the Finder. Open the Terminal, type exercism submit followed by a space, then drag the file from the Finder into the Terminal and press return._)
-3. Once uploaded, a URL will appear that reveals your solution on the Exercism web site.
-4. The Exercism CLI allows files to be submitted more than once, and each successive iteration will be added alongside the original.
-
 To review:
 
 * **HelloWorld.swift** is the Swift Source code file where you code the solution and later submit it to Exercism.
 * **HelloWorldTest.swift** is the Test Source code file provided by Exercism. It contains the tests that define the exercise.
 * **MyPlayground.playground** is for drafting code snippets and playing with ideas.
 
-### Participate in Code Reviews
+To submit:
+
+1. In the Terminal, navigate to the folder that contains the application source file. In this example, the path would be `~/exercism/swift/hello-world/HelloWorld/HelloWorld/`
+2. To submit, type `exercism submit HelloWorld.swift` (_Alternatively, you can submit by using the file name with the full path from any directory. A second alternative is to locate the file you need to submit in the Finder. Open the Terminal, type exercism submit followed by a space, then drag the file from the Finder into the Terminal and press return._)
+3. Once uploaded, a URL will appear that reveals your solution on the Exercism web site.
+4. The Exercism CLI allows files to be submitted more than once, and each successive iteration will be added alongside the original.
+
+To participate in code reviews:
 
-After you submit a file, follow the URL presented to show the submission on the web. Bookmark it for future reference. From your submission page you can view how others solved the same problem.
+* After you submit a file, follow the URL presented to show the submission on the web. Bookmark it for future reference. From your submission page you can view how others solved the same problem.
 
 ### More Information
 

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: trackler
 version: !ruby/object:Gem::Version
-  version: 2.0.6.19
+  version: 2.0.6.20
 platform: ruby
 authors:
 - Katrina Owen
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2017-01-24 00:00:00.000000000 Z
+date: 2017-01-25 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: rubyzip
@@ -1382,6 +1382,8 @@ files:
 - tracks/csharp/exercises/flatten-array/FlattenArrayTest.cs
 - tracks/csharp/exercises/food-chain/Example.cs
 - tracks/csharp/exercises/food-chain/FoodChainTest.cs
+- tracks/csharp/exercises/forth/Example.cs
+- tracks/csharp/exercises/forth/ForthTest.cs
 - tracks/csharp/exercises/gigasecond/Example.cs
 - tracks/csharp/exercises/gigasecond/GigasecondTest.cs
 - tracks/csharp/exercises/go-counting/Example.cs
@@ -2566,6 +2568,10 @@ files:
 - tracks/fsharp/exercises/ledger/Example.fs
 - tracks/fsharp/exercises/ledger/Ledger.fs
 - tracks/fsharp/exercises/ledger/LedgerTest.fs
+- tracks/fsharp/exercises/lens-person/Example.fs
+- tracks/fsharp/exercises/lens-person/HINTS.md
+- tracks/fsharp/exercises/lens-person/LensPerson.fs
+- tracks/fsharp/exercises/lens-person/LensPersonTest.fs
 - tracks/fsharp/exercises/linked-list/Example.fs
 - tracks/fsharp/exercises/linked-list/HINTS.md
 - tracks/fsharp/exercises/linked-list/LinkedListTest.fs
@@ -3876,7 +3882,6 @@ files:
 - tracks/javascript/exercises/binary-search/example.js
 - tracks/javascript/exercises/binary/binary.spec.js
 - tracks/javascript/exercises/binary/example.js
-- tracks/javascript/exercises/bob/bob.js
 - tracks/javascript/exercises/bob/bob.spec.js
 - tracks/javascript/exercises/bob/example.js
 - tracks/javascript/exercises/bowling/bowling.spec.js
@@ -3925,6 +3930,7 @@ files:
 - tracks/javascript/exercises/largest-series-product/example.js
 - tracks/javascript/exercises/largest-series-product/largest-series-product.spec.js
 - tracks/javascript/exercises/leap/example.js
+- tracks/javascript/exercises/leap/leap.js
 - tracks/javascript/exercises/leap/leap.spec.js
 - tracks/javascript/exercises/linked-list/example.js
 - tracks/javascript/exercises/linked-list/linked-list.spec.js
@@ -4840,6 +4846,9 @@ files:
 - tracks/objective-c/exercises/bob/BobExample.h
 - tracks/objective-c/exercises/bob/BobExample.m
 - tracks/objective-c/exercises/bob/BobTest.m
+- tracks/objective-c/exercises/bracket-push/BracketPushExample.h
+- tracks/objective-c/exercises/bracket-push/BracketPushExample.m
+- tracks/objective-c/exercises/bracket-push/BracketPushTest.m
 - tracks/objective-c/exercises/clock/ClockExample.h
 - tracks/objective-c/exercises/clock/ClockExample.m
 - tracks/objective-c/exercises/clock/ClockTest.m
@@ -4906,6 +4915,9 @@ files:
 - tracks/objective-c/exercises/space-age/SpaceAgeExample.h
 - tracks/objective-c/exercises/space-age/SpaceAgeExample.m
 - tracks/objective-c/exercises/space-age/SpaceAgeTest.m
+- tracks/objective-c/exercises/sublist/SublistExample.h
+- tracks/objective-c/exercises/sublist/SublistExample.m
+- tracks/objective-c/exercises/sublist/SublistTest.m
 - tracks/objective-c/exercises/sum-of-multiples/SumOfMultiplesExample.h
 - tracks/objective-c/exercises/sum-of-multiples/SumOfMultiplesExample.m
 - tracks/objective-c/exercises/sum-of-multiples/SumOfMultiplesTest.m
@@ -5170,6 +5182,17 @@ files:
 - tracks/pascal/docs/LEARNING.md
 - tracks/pascal/docs/RESOURCES.md
 - tracks/pascal/docs/TESTS.md
+- tracks/pascal/docs/img/00delphiwelcomepage.png
+- tracks/pascal/docs/img/01delphiclicktools.png
+- tracks/pascal/docs/img/02delphiclickoptions.png
+- tracks/pascal/docs/img/03delphioptionsenvironmentvariables.png
+- tracks/pascal/docs/img/04delphioptionsenvironmentvariablesclicknew.png
+- tracks/pascal/docs/img/05delphinewuservariable.png
+- tracks/pascal/docs/img/06delphioptionslibrary.png
+- tracks/pascal/docs/img/07delphiclicklibrarypathbutton.png
+- tracks/pascal/docs/img/08delphidirectoriesinputvarnameclickadd.png
+- tracks/pascal/docs/img/09delphidirectoriesclickok.png
+- tracks/pascal/docs/img/10delphioptonsclickok.png
 - tracks/pascal/exercises/.keep
 - tracks/pascal/exercises/allergies/AllergyTests.dpr
 - tracks/pascal/exercises/allergies/uAllergiesExample.pas
@@ -5472,6 +5495,8 @@ files:
 - tracks/php/exercises/bob/HINTS.md
 - tracks/php/exercises/bob/bob_test.php
 - tracks/php/exercises/bob/example.php
+- tracks/php/exercises/book-store/book-store_test.php
+- tracks/php/exercises/book-store/example.php
 - tracks/php/exercises/bowling/bowling_test.php
 - tracks/php/exercises/bowling/example.php
 - tracks/php/exercises/bracket-push/bracket-push_test.php