"Junyu Zhang" <24*6*1*2@s*u*e*t*u*a*e*u*a*> wrote: There's no need to do all this work yourself, as we have standard functions such atof and even strtof to help us.

Could we make this more clear or simplified? If we accept any representations, the situation may be a little bit complicated: 1. "1.5e4F" -> Some characters like ".eF" must be grabbed when tokenizing a real number. 2. "- 4" -> A space-separated minus may not be an operator, but the sign of a real number. 3. ".123" -> Not all real numbers start with or end with digits. Although APIs like atof or strtof can check and parse potential real number tokens very well, knowing characters in real number token is necessary when splitting words. Another solution may be simply the syntax of real number, that will make life easier. For example, all real numbers will be like '[+-]([0-9]*)[.]([0-9]*)'.

Adding to this, should we accept a number formatted as 1. or should we only accept 1 (no decimal if it is a whole number) or 1.0, 1.00, etc

ANONYMOUS wrote: Hey guys, ml accepts whole numbers, there is no example in the ml file where there is a decimal point after a whole number, e.g. 2.0 would just appear as 2 in the ml file. I'm assuming as more decimal places are required they will be added e.g. 2.546. I wouldn't worry about how exactly numbers appear as you are guaranteed that expressions are valid, there won't be invalid decimal numbers. So you should be able to directly copy the numbers into the C file and let C do the work for you.