Looks good. And you are right. The distinction between text and binary
isn't properly maintained in OWFS -- and probably shouldn't be. The 1-wire
slaves really only use binary strings.
I'll add the patch.
Paul
On Wed, Jun 26, 2013 at 9:05 AM, Jan Kandziora <[email protected]> wrote:
> Am 23.06.2013 22:52, schrieb Jan Kandziora:
> > Hello,
> >
> > I found another bug in owtcl.
> >
> > Tcl does UTF mangling on the result of Tcl_GetStringFromObj. This is
> > very disturbing for the value of a "put" operation as there is no way to
> > output binary data to owfs as it is possible with owfs/fuse itself (and
> > the other language bindings, I guess).
> >
> > As far as I see there is no use case for such a mangling. The onewire
> > devices expect mostly numbers or binary data, the only device expecting
> > text is the LCD, and this is *not* UTF but another encoding.
> >
> > Comments welcome.
> >
> No comments on this? Serg? Paul? Or is it just the holiday season?
>
>
> Kind regards
>
> Jan
>
>
>
>
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by Windows:
>
> Build for Windows Store.
>
> http://p.sf.net/sfu/windows-dev2dev
> _______________________________________________
> Owfs-developers mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/owfs-developers
>
------------------------------------------------------------------------------
This SF.net email is sponsored by Windows:
Build for Windows Store.
http://p.sf.net/sfu/windows-dev2dev
_______________________________________________
Owfs-developers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/owfs-developers
