Tested the above and agree your example works but when applied to a TextField situation i.e. a stray “ or text enclosed in quotes “example text” the quotes are removed. let removeCommasFirstCardFirstWordClue = cards.firstCardFirstWordClue.replacingOccurrences(of: ",", with: "") works in the TextField but, let removeCommasFirstCardFirstWordClue = cards.firstCardFirstWordClue.replacingOccurrences(of: """, with: "") does not work. Maybe I need to find a way to prevent quotes from being entered?

I don’t understand why the answers are about structs versus enums versus……. when my question was about reformatting the code into chunks and in line?

So sorry if you thought my comment was directed to you (it wasn’t). Again sorry I didn’t answer the extension question of yours as I was so confused I didn’t realise it was for me. My question is, is it bad practice to take a piece of code and break it up into chunks and format it down one line and also a supplementary question, if code was presented like that, would it compile okay and be acceptable to the App Store for example. Apologies again.

Found this which should open up a whole new world of learning! https://google.github.io/swift/

Noted thank you. I missed that one! (hopefully the only one!)

Sorry I thought you had in your mind it was being reviewed. I would still check your submission because it will most likely be something you need to fix or attend to. Take it from me they don’t make it easy or obvious.

Thank you for your reply. Although your suggestion does not address what I am trying to achieve I am always grateful to learn something new. Your suggestion removes a type error which is good but it changes the accuracy of the location and depending on where the error is in the Coordinate variable the location could be way off.

I have global error trap that catches “000.000000” which is why I chose “000.000000” as the result of this error trap. I have also taken onboard your suggestion of checking “-“ is not anywhere except at the first position. Regarding which line the error occurs? unfortunately Playgrounds shows the alert at the top of an enclosure (Section { ) (for example).

Thank you for your reply. Your suggestion clears the error and I now see my syntax mistake. Unfortunately it does not work (no change if a type error is included in the Text Field). I will study the Code and hopefully the answer will come. Regarding which line the error occurs? unfortunately Playgrounds shows the alert at the top of an enclosure (Section { ) (for example).

No Errors but does not do anything.

No Errors but does not do anything (typo remains)

Sorry it was not my intention to comment twice but it was my intention to comment that this does not work!