KOS sscanf didn't understand %f

Strapping Scherzo · Post by **Strapping Scherzo** » Fri Jan 09, 2004 2:18 pm

I'm about to try the other equivilents %g and %e but it makes me wonder if the types that printf and scanf understand in KOS is limited. Any word on this?

Ian Micheal · Post by **Ian Micheal** » Fri Jan 09, 2004 3:59 pm

Yeah scanf does not work in plain kos.

doragasu · Post by **doragasu** » Fri Jan 09, 2004 6:00 pm

Ian Micheal wrote:Yeah scanf does not work in plain kos.

He isn't trying scanf, he's trying sscanf.

Strapping Scherzo · Post by **Strapping Scherzo** » Fri Jan 09, 2004 7:17 pm

doragasu wrote:
Ian Micheal wrote:Yeah scanf does not work in plain kos.
He isn't trying scanf, he's trying sscanf.

Exactly. sccanf works great in KOS for the integer format codes like %d and %i. I just get output from my dc-tool console at runtime that says %f, %d, and %e are unknown. Kinda sucks.

Ian Micheal · Post by **Ian Micheal** » Fri Jan 09, 2004 9:07 pm

Only parts work it's not complete. Better off not using it.

Ender · Post by **Ender** » Fri Jan 09, 2004 9:13 pm

Ian Micheal wrote:Only parts work it's not complete. Better off not using it.

The clock in my car doesn't work. Guess I shouldn't use my car.

nymus · Post by **nymus** » Fri Jan 09, 2004 9:36 pm

^^don't exaggerate. If the minute hand of your clock is not moving, you're better off not using the watch, unless you don't care about hourly differences in your time. Obvously scherzo wants something in particular from his sscanf and it is his place to demand it, as a user. If it doesn't exist, then he will be dissatisfied, whether or not it is a small thing.

Does your food taste different with an extra pinch of salt?

Ender · Post by **Ender** » Fri Jan 09, 2004 9:54 pm

nymus wrote:^^don't exaggerate. If the minute hand of your clock is not moving, you're better off not using the watch, unless you don't care about hourly differences in your time. Obvously scherzo wants something in particular from his sscanf and it is his place to demand it, as a user. If it doesn't exist, then he will be dissatisfied, whether or not it is a small thing.

To say that a troubleshooting/bugchecking tool should not be used at all because it does not support one particular type of variable is ridiculous (in my mind).

Does your food taste different with an extra pinch of salt?

Depends on the food

toastman · Post by **toastman** » Fri Jan 09, 2004 10:53 pm

That and some of us have the wherewithal to fix said problems or work around them.

nymus · Post by **nymus** » Sat Jan 10, 2004 1:01 am

c'mon! Avoiding it IS a valid workaround. It could take time to modify/debug a system utility.

There are others you could come up with too. Suggest them please, instead of shooting down the one put forward... especially if you can't provide an alternative.

Ian Micheal · Post by **Ian Micheal** » Sat Jan 10, 2004 1:25 pm

Bero Gave me this via email one time it's also limted

Code: Select all

int sscanf(const char *str, const char *fmt,...) 
{ 
va_list ap; 
int *pval; 

if (strcmp(fmt,"%x")) { 
exit(-1); 
} 

va_start(ap, fmt); 
pval = va_arg(ap,int*); 
va_end(ap); 

*pval = strtol(str,0,16); 
return 1; 
}

Kos has not supported it from kos1.1.9 and down. And the support for such things are not complete or even working. I have quiet a few work arounds best bet is to. Write your own string parser. Common to know most of libc is uncomplete and does not work like normal at all.

Want an example I can pm you one. But Sccanf and scanf support are limted Dan has not fix them nether have . I have A sccanf lib that uses GPL code from mini lib c which can not be included into kos.

Other then that You do have to write it one's self.

I can provide work arounds and help if you need it.