7 people like it.
Like the snippet!

Ninety-Nine F# Problems - Problems 11 - 20 - List, continued]

These are F# solutions of Ninety-Nine Haskell Problems which are themselves translations of Ninety-Nine Lisp Problems and Ninety-Nine Prolog Problems. The solutions are hidden so you can try to solve them yourself.

Ninety-Nine F# Problems - Problems 95 - 99 - Miscellaneous problems

 1: 
 2: 
 3: 
 4: 
 5: 
 6: 
 7: 
 8: 
 9: 
10: 
11: 
12: 
13: 
14: 
15: 
16: 
17: 
18: 
19: 
20: 
21: 
22:

///
/// These are F# solutions of Ninety-Nine F# Problems 
/// (http://www.haskell.org/haskellwiki/H-99:_Ninety-Nine_F#_Problems), 
/// which are themselves translations of Ninety-Nine Lisp Problems
/// (http://www.ic.unicamp.br/~meidanis/courses/mc336/2006s2/funcional/L-99_Ninety-Nine_Lisp_Problems.html)
/// and Ninety-Nine Prolog Problems
/// (https://sites.google.com/site/prologsite/prolog-problems).
///
/// If you would like to contribute a solution or fix any bugs, send 
/// an email to paks at kitiara dot org with the subject "99 F# problems". 
/// I'll try to update the problem as soon as possible.
///
/// The problems have different levels of difficulty. Those marked with a single asterisk (*) 
/// are easy. If you have successfully solved the preceeding problems you should be able to 
/// solve them within a few (say 15) minutes. Problems marked with two asterisks (**) are of 
/// intermediate difficulty. If you are a skilled F# programmer it shouldn't take you more than 
/// 30-90 minutes to solve them. Problems marked with three asterisks (***) are more difficult. 
/// You may need more time (i.e. a few hours or more) to find a good solution
///
/// Though the problems number from 1 to 99, there are some gaps and some additions marked with 
/// letters. There are actually only 88 problems.
///

() Problem 95 : English number words

 1: 
 2: 
 3: 
 4: 
 5: 
 6: 
 7: 
 8: 
 9: 
10:

/// On financial documents, like cheques, numbers must sometimes be written in full words. 
/// Example: 175 must be written as one-seven-five. Write a predicate full-words/1 to print 
/// (non-negative) integer numbers in full words.
///  
/// Example in F#: 
/// 
/// > fullWords 175;;
/// val it : string = "one-seven-five"

(Solution)

() Problem 96 : Syntax checker

 1: 
 2: 
 3: 
 4: 
 5: 
 6: 
 7: 
 8: 
 9: 
10: 
11: 
12: 
13: 
14: 
15: 
16: 
17: 
18: 
19: 
20: 
21: 
22: 
23: 
24: 
25: 
26: 
27: 
28: 
29:

/// In a certain programming language (Ada) identifiers are defined by the syntax diagram below.
///  
///   ---->|letter|---+-------------------------------------+------>
///                   |                                     |
///                   +--------------+------>|letter|---+---+
///                   |             / \                 |
///                   +--->| - |---+   +---->|digit |---+
///                   |                                 |
///                   +---------------------------------+
///
/// Transform the syntax diagram into a system of syntax diagrams which do not contain loops;
/// i.e. which are purely recursive. Using these modified diagrams, write a predicate 
/// identifier/1 that can check whether or not a given string is a legal identifier.
///  
/// Example in Prolog: 
/// % identifier(Str) :- Str is a legal identifier 
///  
/// Example in F#: 
/// 
/// > identifier "this-is-a-long-identifier";;
/// val it : bool = true
/// > identifier "this-ends-in-";;
/// val it : bool = false
/// > identifier "two--hyphens";;
/// val it : bool = false

(Solution 1)

(Solution 2)

(*) Problem 97 : Sudoku

 1: 
 2: 
 3: 
 4: 
 5: 
 6: 
 7: 
 8: 
 9: 
10: 
11: 
12: 
13: 
14: 
15: 
16: 
17: 
18: 
19: 
20: 
21: 
22: 
23: 
24: 
25: 
26: 
27: 
28: 
29:

/// Sudoku puzzles go like this:
///
///       Problem statement                 Solution
///
///        .  .  4 | 8  .  . | .  1  7          9  3  4 | 8  2  5 | 6  1  7         
///                |         |                          |         |
///        6  7  . | 9  .  . | .  .  .          6  7  2 | 9  1  4 | 8  5  3
///                |         |                          |         |
///        5  .  8 | .  3  . | .  .  4          5  1  8 | 6  3  7 | 9  2  4
///        --------+---------+--------          --------+---------+--------
///        3  .  . | 7  4  . | 1  .  .          3  2  5 | 7  4  8 | 1  6  9
///                |         |                          |         |
///        .  6  9 | .  .  . | 7  8  .          4  6  9 | 1  5  3 | 7  8  2
///                |         |                          |         |
///        .  .  1 | .  6  9 | .  .  5          7  8  1 | 2  6  9 | 4  3  5
///        --------+---------+--------          --------+---------+--------
///        1  .  . | .  8  . | 3  .  6          1  9  7 | 5  8  2 | 3  4  6
///                |         |                          |         |
///        .  .  . | .  .  6 | .  9  1          8  5  3 | 4  7  6 | 2  9  1
///                |         |                          |         |
///        2  4  . | .  .  1 | 5  .  .          2  4  6 | 3  9  1 | 5  7  8
///
/// Every spot in the puzzle belongs to a (horizontal) row and a (vertical) column, as well
/// as to one single 3x3 square (which we call "square" for short). At the beginning, some 
/// of the spots carry a single-digit number between 1 and 9. The problem is to fill the 
/// missing spots with digits in such a way that every number between 1 and 9 appears exactly 
/// once in each row, in each column, and in each square.

(Solution)

(*) Problem 98 : Nonograms

 1: 
 2: 
 3: 
 4: 
 5: 
 6: 
 7: 
 8: 
 9: 
10: 
11: 
12: 
13: 
14: 
15: 
16: 
17: 
18: 
19: 
20: 
21: 
22: 
23: 
24: 
25: 
26: 
27: 
28: 
29: 
30: 
31: 
32: 
33: 
34: 
35: 
36: 
37: 
38: 
39: 
40: 
41: 
42: 
43: 
44: 
45: 
46: 
47:

/// Around 1994, a certain kind of puzzle was very popular in England. The "Sunday Telegraph" 
/// newspaper wrote: "Nonograms are puzzles from Japan and are currently published each week 
/// only in The Sunday Telegraph. Simply use your logic and skill to complete the grid and 
/// reveal a picture or diagram." As a Prolog programmer, you are in a better situation: you 
/// can have your computer do the work! Just write a little program ;-).
///
/// The puzzle goes like this: Essentially, each row and column of a rectangular bitmap is 
/// annotated with the respective lengths of its distinct strings of occupied cells. The 
/// person who solves the puzzle must complete the bitmap given only these lengths.
///
///             Problem statement:          Solution:
///             |_|_|_|_|_|_|_|_| 3         |_|X|X|X|_|_|_|_| 3           
///             |_|_|_|_|_|_|_|_| 2 1       |X|X|_|X|_|_|_|_| 2 1         
///             |_|_|_|_|_|_|_|_| 3 2       |_|X|X|X|_|_|X|X| 3 2         
///             |_|_|_|_|_|_|_|_| 2 2       |_|_|X|X|_|_|X|X| 2 2         
///             |_|_|_|_|_|_|_|_| 6         |_|_|X|X|X|X|X|X| 6           
///             |_|_|_|_|_|_|_|_| 1 5       |X|_|X|X|X|X|X|_| 1 5         
///             |_|_|_|_|_|_|_|_| 6         |X|X|X|X|X|X|_|_| 6           
///             |_|_|_|_|_|_|_|_| 1         |_|_|_|_|X|_|_|_| 1           
///             |_|_|_|_|_|_|_|_| 2         |_|_|_|X|X|_|_|_| 2           
///              1 3 1 7 5 3 4 3             1 3 1 7 5 3 4 3              
///              2 1 5 1                     2 1 5 1                      
///      
/// For the example above, the problem can be stated as the two lists [[3],[2,1],[3,2],[2,2]
/// ,[6],[1,5],[6],[1],[2]] and [[1,2],[3,1],[1,5],[7,1],[5],[3],[4],[3]] which give the 
/// "solid" lengths of the rows and columns, top-to-bottom and left-to-right, respectively. 
/// Published puzzles are larger than this example, e.g. 25 x 20, and apparently always have 
/// unique solutions.
///
/// Example in F#:
///
/// > printfn "%s" <| nonogram [[3];[2;1];[3;2];[2;2];[6];[1;5];[6];[1];[2]]
///                             [[1;2];[3;1];[1;5];[7;1];[5];[3];[4];[3]];;
/// |_|X|X|X|_|_|_|_| 3
/// |X|X|_|X|_|_|_|_| 2 1
/// |_|X|X|X|_|_|X|X| 3 2
/// |_|_|X|X|_|_|X|X| 2 2
/// |_|_|X|X|X|X|X|X| 6
/// |X|_|X|X|X|X|X|_| 1 5
/// |X|X|X|X|X|X|_|_| 6
/// |_|_|_|_|X|_|_|_| 1
/// |_|_|_|X|X|_|_|_| 2
///  1 3 1 7 5 3 4 3
///  2 1 5 1
///

(Solution needed)

(*) Problem 99 : Crossword puzzle

 1: 
 2: 
 3: 
 4: 
 5: 
 6: 
 7: 
 8: 
 9: 
10: 
11: 
12: 
13: 
14: 
15: 
16: 
17: 
18: 
19: 
20: 
21: 
22: 
23: 
24: 
25: 
26: 
27: 
28: 
29: 
30: 
31: 
32: 
33: 
34: 
35: 
36: 
37: 
38: 
39: 
40: 
41: 
42: 
43: 
44: 
45: 
46: 
47:

/// Given an empty (or almost empty) framework of a crossword puzzle and a set of words. The 
/// problem is to place the words into the framework.
/// 
/// 
/// 
/// The particular crossword puzzle is specified in a text file which first lists the words
/// (one word per line) in an arbitrary order. Then, after an empty line, the crossword 
/// framework is defined. In this framework specification, an empty character location is 
/// represented by a dot (.). In order to make the solution easier, character locations can 
/// also contain predefined character values. The puzzle above is defined in the file 
/// p99a.dat, other examples are p99b.dat and p99d.dat. There is also an example of a puzzle 
/// (p99c.dat) which does not have a solution.
/// 
/// Words are strings (character lists) of at least two characters. A horizontal or vertical 
/// sequence of character places in the crossword puzzle framework is called a site. Our 
/// problem is to find a compatible way of placing words onto sites.
/// 
/// Hints: (1) The problem is not easy. You will need some time to thoroughly understand it. 
/// So, don't give up too early! And remember that the objective is a clean solution, not 
/// just a quick-and-dirty hack!
/// 
/// (2) Reading the data file is a tricky problem for which a solution is provided in the 
/// file p99-readfile.pl. See the predicate read_lines/2.
/// 
/// (3) For efficiency reasons it is important, at least for larger puzzles, to sort the 
/// words and the sites in a particular order. For this part of the problem, the solution 
/// of P28 may be very helpful.
/// 
/// Example in F#:
/// 
/// ALPHA
/// ARES
/// POPPY
/// 
///   .
///   .
/// .....
///   . .
///   . .
///     .
/// > solve $ readCrossword "ALPHA\nARES\nPOPPY\n\n  .  \n  .  \n.....\n  . .\n  . .\n    .\n"
///  
/// [[((3,1),'A');((3,2),'L');((3,3),'P');((3,4),'H');((3,5),'A');((1,3),'P');((2,3)
/// ,'O');((3,3),'P');((4,3),'P');((5,3),'Y');((3,5),'A');((4,5),'R');((5,5),'E');((
/// 6,5),'S')]]

(Solution needed)

let fullWords (n: int) =
    let words = [| "zero"; "one"; "two"; "three"; "four"; "five"; "six"; "seven"; "eight"; "nine" |]
    let digits = n.ToString() |> Seq.map (fun c -> int c - int '0') |> Seq.map (fun c -> words.[c])|> Array.ofSeq
    System.String.Join("-", digits)

// identifier = letter((-)?(letter|digit))*
// Some people, when confronted with a problem, think "I know, I'll use regular expressions." Now they have two problems. - Jamie Zawinski
let identifier expr = System.Text.RegularExpressions.Regex.IsMatch(expr,@"^([a-z]|[A-Z])((\-)?([0-9]|[a-z]|[A-Z]))*$")

// This is the overkill solution using a parser combinator.
// For a solution using fslex and fsyacc go here: https://github.com/paks/99-FSharp-Problems/tree/master/P96
// The combinator came from here: http://v2matveev.blogspot.com/2010/05/f-parsing-simple-language.html
type 'a ParserResult = Success of 'a * char list | Failed

type 'a Parser = Parser of (char list -> 'a ParserResult)

let apply (Parser p) s = p s

let run p l = apply p (Seq.toList l)

let one v = Parser(fun cs -> Success(v,cs))
let fail() = Parser(fun _ -> Failed)

let bind p f = Parser (fun cs ->
        match apply p cs with
        | Success(r, cs2) -> apply (f r) cs2
        | Failed -> Failed)

let choose f p = Parser(fun cs ->
    match cs with
        | c::cs when f c -> Success(p c, cs)
        | _ -> Failed)

let (<|>) p1 p2 = Parser(fun cs ->
    match apply p1 cs with
        | Failed -> apply p2 cs
        | result -> result)

let (<&>) p1 p2 = Parser(fun cs ->
    match apply p1 cs with
        | Success(_, cs2) -> apply p2 cs2
        | Failed -> Failed)

let letter = choose System.Char.IsLetter id

let letterOrDigit = choose System.Char.IsLetterOrDigit id

let hiphen = choose ((=) '-') id

type ParseBuilder() =
    member parser.Return(v) = one v
    member parser.Bind(p, f) = bind p f
    member parser.ReturnFrom(p) = p
    member parser.Zero() = fail()

let parser = new ParseBuilder()

let rec zeroOrMany p f v0 =
    parser {
        return! oneOrMany p f v0 <|> one v0
    }

and oneOrMany p f v0 =
    parser {
        let! v1 = p
        return! zeroOrMany p f (f v0 v1)
    }

let hiphenLetterOrDigit = (hiphen <&> letterOrDigit) <|> letterOrDigit

let identifierP = parser {
    let! l = letter
    let sb = new System.Text.StringBuilder(l.ToString())
    let! rest = sb |> zeroOrMany hiphenLetterOrDigit (fun acc v -> acc.Append(v))
    return rest.ToString()
}

let identifier' str =
    match run identifierP str with
    | Success(_,[]) -> true //if the parser consumed all the input, then it's an identifier
    | _ -> false

let solution97 = "https://github.com/paks/ProjectEuler/blob/master/Euler2/P96/sudoku.fs"

let solution98 = "your solution here!!"

let solution99 = "your solution here!!"

Previous Version Next Version Raw view Test code New version

More information

Link:	http://fssnip.net/ao
Posted:	12 years ago
Author:	Cesar Mendoza
Tags:	ninety-nine f# problems , tutorial , f# , lists