> I did have to copy over traps.unix, & create a user.unix.scripts -- but
> everything seems to run just fine.

mmm, there's a bug somewhere in the unix binary. If I return a 2 digit
number, it adds a '5{' to the end of the result. If I return a 3 digit
number it appends a '{'. If I call traps.unix.scpt directly it things work
as expected, and if I send an AE (from script debugger) -- it works
correctly as well.

If I coerce the the number to a string in Radio/Frontier before returning it
I get a '?' at the end.

example:

odbcli.get returns the value at the supplied address ( it's an ODB CLI )


(return as is)
]% frontier odbcli.get "PHPRU.unlucky"
135{

( return as a string)
]% frontier odbcli.get "PHPRU.unlucky"
13?

More data points (all return as numbers):
% frontier odbcli.get "PHPRU.unlucky" // set in RU as 3
3

% frontier odbcli.get "PHPRU.unlucky" // set in RU as 13
135{

% frontier odbcli.get "PHPRU.unlucky" // set in RU as 131
131{

% frontier odbcli.get "PHPRU.unlucky" // set in RU as 1312
1312

% frontier odbcli.get "PHPRU.unlucky" // set in RU as 13128
13128


Looks like I can work around it by always return a string & padding the
string with spaces before I do. ie:

return " " + string( adr^ ) + " "


James.

Enclosures

None.  

Replies

None.