using String.charAt() for semicolons

Hi all

Been a while since I posted here.

I haven't tested it yet, but thought I should try asking nonetheless. When using the charAt(int) method from the String class what would it return if the character at that index were a semicolon?

For example if I had the String hell;o

and used

Code:

---

if (stringName.charAt(stringName.length-2) == ';')

---

would that work or would I need to use the unicode number (UTF 59 as my research has told me) for a semicolon instead?

If both work then what are the pros/cons of each approach?

Perhaps relatively simple for you guys but it something I have been thinking about.

Thanks in advance for your help everyone.

Quote:

---

Originally Posted by porchrat

I haven't tested it yet, ...

---

You know what the correct answer here is: For gosh sake, test it!.

Come on now. There is no substitute for this.

Quote:

---

Originally Posted by Fubarable

You know what the correct answer here is: For gosh sake, test it!.

Come on now. There is no substitute for this.

---

Hey, that code could make his toaster explode. Better yours than his :p

Quote:

---

Originally Posted by Fubarable

You know what the correct answer here is: For gosh sake, test it!.

Come on now. There is no substitute for this.

---

lol fair enough I need to test it, it is just a large batch run that takes hours to run to completion so that answer is going to take time.

It isn't so much whether or not it will work as I don't see why it won't work I just wanted to know what the pros and cons were of the two approaches. :p

You can create a test case that take small fractions of a second to run.

Quote:

---

Originally Posted by r035198x

You can create a test case that take small fractions of a second to run.

---

have ended up doing that, looks good. So it does work (when referring to the semicolon as ';').

I would still like some insight as to why someone would use the UTF-16/UTF-32 value of 59 instead as I have seen code in which coders do that instead.

Personally doesn't make sense to me as if at some point the encoding changes the number would no longer correspond to a semicolon or am I wrong?

Is it perhaps faster that way?