# FUP vs. fileio

Brack (slayer@kaiwan.com)
Sat, 22 Feb 1997 11:28:45 PST

- Messages sorted by:[ date ][ thread ][ subject ][ author ]

    At 05:52 AM 2/22/97 PST, cecil@mail.iaw.on.ca wrote:
    >Okay, comments from the newbie here, but oh well. I just thought I'd=20
    >say that I much prefer FUP's ability to input binary characters in=20
    >normal strings.=20
    >   I don't use it a great deal, but when I do, I generally make sure I=20
    >know what I'm doing, so as to not corrupt the database as=20
    >mentioned before. (this is fairly hard to do accidentally, isn't it?=20
    >seems like it)
    >   It's also fairly useful for when you /need/ binary characters, for=20
    >example, when installing ANSI. (It refers to a chr() patch that you=20
    >can get, as an alternative... anyone know where this can be=20
    >obtained?)

    Well ANSI 2.2 didn't need any of that anymore, but Dark Owl's development
    copy got trashed (or so he said) and he's not planning on working on it=
     soon.=20
    You can get chr() at
    ftp://ftp.crl.com/users/ro/riche/MOO/patches/MOO-1.7.8/moo-1.7.8-chrasc.patc=
    h

    however this was a patch made for 1.7.8, although you can just copy the
    code and put it in your extensions.c. I converted it to 1.8 extension
    format to put in my patch archive but it isn't up yet.

    >    I dunno about the rest of you, but the MOO's form of binary=20
    >strings just don't cut it for me. :) Now, if only binary strings=20
    >could be displayed as binary without having to set the whole=20
    >connection binary. (ick)
    >
    well the reason this wasn't done was because people would put binary
    characters all over the place, and some people can't even see those
    characters, and they don't look the same in different fonts, etc. Also some
    people will take great delight in ANSI-bombing raw telneters...
    For example, not everyone sees these characters the same way: =A9 =E3 =F6
    In the windows font I'm using that comes out as a copyright symbol, an a
    with a tilde over it, and a o with an umlaut over it. but it's not the same
    on other systems, so using high-bit characters isn't a good idea.

    >Anyway, that's just my comment on the matter. :)
    >=20
    Well, these are just my comments. Have a nice day (insert annoying smiley
    here)