What to submit and when:

- All submissions are electronic: by e-mail to elenam at morris.umn.edu and CC to all lab partners. Please do not delete your e-mail from "Sent mail" or your mailbox until the end of the semester.
- When working on the lab, please comment your work so that it is clear what contributions of each person are.
- At the end of the lab each group should send me the results of their in-class work. Please indicate if this is your final submission.
- If your submission at the end of the lab time was not final, please send me(CC to the lab partner(s)) a final copy before the due time. Please use the subject "3501 Lab N", where N is the lab number.

Work in pairs

The goal of the lab is to practice with JFLAP (a tool for experimenting with finite automata and other computability topics) and to explore the pumping lemma for regular languages.

- Please save your automata files as .jff files and your data as
.txt files.
**Files names must be as follows**: names of those in the group followed by question name, e.g.`SmithAdams3.jff`

(where 3 refers to the question number). This will help me in running test data - Consult the JFLAP tutorial as needed.

Use the tutorial Regular Expressions and Converting to an NFA to convert the regular expressions given below to NFAs. Note that JFLAP uses + as a symbol for union and * for the star operation. Also make sure to set parentheses correctly in your expression.

JFLAP gives you hints on the steps and provides a button "(De)-expressionify Transition" to break down regular expressions into smaller subexpressions. You need to add the empty transitions to complete each step.

As you are converting a regular expression to an NFA, write down the
intermediate expressions as a note on the JFLAP screen: use the
selection tool (the one that you use to mark initial and final
states), right-click anywhere on the JFLAP screen, and choose "add
note". For instance, if you are breaking down an expression
`00+11`

into `00`

and `11`

, write
`00+11 -> 00, 11`

.

Below are two regular expressions to convert:

- ((0+1)0)*
- (00)*+(10)*

Please export and submit your NFAs.

JFLAP guides you through the process of converting a DFA to a regular expression via a generalized NFA (GNFA), as described in the tutorial Converting a FA to a Regular Expression. JFLAP uses a slightly different version of a GNFA: it allows self-loops in the starting and the final state. The empty set transitions are added just like in the book, and the number of states is reduced by the procedure described in the book. The resulting regular expression then is combined as R1*R2R3*, where R1 is the self-loop expression in the start state, R2 is the expression on the transition from the start state to the final state, and R3 is the loop in the final state.

As you are transforming your DFA to a 2-state GNFA, write down (in a plain-text file) all transition changes that result in non-empty-set expressions.

Below is the DFA to convert:- The language of all strings that have 00
- The language of all strings that either start with 0 and don't have any more 0s, or start with 1 and don't have any more 1s. Note that as the first step you would need to create a single final state and connect the old final states to it by empty-string transitions.

Please export and submit your resulting expression.

The pumping lemma in JFLAP is implemented as a two-player "game" when one player is trying to prove that a language is regular by representing strings as required by the pumping lemma, and the other player is trying to disprove it, as described in the tutorial Regular Pumping Lemmas.

Go to "Regular Pumping Lemma" in the JFLAP start menu (careful: you
don't want Context-Free Pumping Lemma). There is a list of languages,
some are regular, some aren't. The alphabet is a,b. The pumping length is
denoted as m. JFLAP allows you to save the file with the log of all
your attempts. Please submit these files for the two cases below and
**additionally** write down your conclusions in a
plain-text file or an e-mail message.

Your conclusions should include:

- whether the language satisfies the pumping lemma. This is a bit tricky since you are testing a pumping length, but your conclusions should be general. For a language that satisfies the pumping lemma show its pumping length and explain how you would always be able to break down a string that in a way that satisfies the pumping lemma. If the language does not satisfy the pumping lemma, show how to construct a string that breaks the pumping lemma. Show it for at least two values of candidates for the pumping length.
- whether it is regular (note that some languages that satisfy the pumping lemma may still be non-regular). Justify your answer, either by explaining why the language is regular, or by giving your intuition for why it is not regular. You don't need to do a proof.

The languages to try:

- The 6th example (the language a^n b^j a^k, where n > 5, j > 3, and k ≤ j). Choose the "computer goes first" option so that you are trying to prove that the language is non-regular.
- The 8th example (the language a^n b^k, n is odd or k is even). Choose the "you go first" option so that you are trying to prove that the language satisfies the pumping lemma.

Please refer to the corresponding sections of
the JFLAP tutorial,
namely Entering
grammars (just pressing "enter" on the right hand side enters an empty
string),
Brute
Force Parser for constructing parse trees,
and Constructing
a push-down automaton. If Brute Force Parser doesn't work on your grammar,
contsruct your parse tree manually using **User Control Parser**.

Your tasks are as follows:

- A context free grammar for the language of strings a^n b^m, where n >= m
- A context free grammar for the language of strings a^k followed by any number of b followed by c^k
- A context-free grammar for odd-length strings of alternating zeros and ones. It can start with either zero or one.
- A context-free grammar for a language of 0, 1, true, false,
operations
`<, >, ==`

, a ternary conditional operator`?:`

, and parentheses. The order of**precedence**is as follows: parentheses have the highest precedence, then the comparison operations, and then the conditional operator.The conditional operator is defined as following:

evalautes e1, and if it is true then it evaluates and returns e2, otherwise it evaluates and returns e3. For example:`e1? e2 : e3`

would be interpreted as`0 < 1? 0 : 1`

which becomes`(0 < 1) ? 0 : 1`

after the condition is evaluated, which would in turn result in 0.`true ? 0 : 1`

The comparison operators

`<, >, ==`

are left-associative, i.e.

should be interpreted as`0 == 1 == false`

which evaluates to`(0 == 1) == false`

which is true.`false == false`

The conditional is right-associative:

is interpreted as`0 > 1 ? 0 : 0 == 0 ? 1 : 0`

then evaluated as`(0 > 1) ? 0 : ((0 == 0) ? 1 : 0)`

then as`false ? 0 : ((0 == 0) ? 1 : 0)`

then as`false ? 0 : (true ? 1 : 0)`

which will return 1.`false ? 0 : 1`

Test your grammar on all of the test cases above and two more cases that check for precedence, associativity, and parentheses. Submit jpg files for the parse trees.

Note that language designers don't always get the associativity right.

**Important:**your grammar must enforce correct precedence and associativity for all operations. Your write-up for this problem should briefly explain how this is done. - A pushdown automaton for the language of strings a^k followed by any number of b followed by c^k (do not convert your grammar from the previous question into an automaton or vice versa)
- A pushdown automaton for the language of strings a^n b^m where n <= m.

Use the option Convert CFG to PDA (LL) for this problem. In a plain-text file explain what rules were added to the PDA and why.

- Convert the grammar for the language of palindromes to a PDA. The alphabet is 0,1. Submit the resulting PDA.