does it work to just use binary and then do ``>string``?
On Wed, Oct 26, 2016 at 2:55 PM, Alexander Ilin wrote:
> Hello!
>
> I'd like to parse some log-files created by an old-style DOS program.
> They contain pseudographics characters for drawing frames and tables.
>
Are you talking about the characters that used to be used in character
based windows apps? LIke on this page from 179-218 or so?
https://en.wikipedia.org/wiki/Code_page_437
On Wed, Oct 26, 2016 at 3:52 PM, John Benediktsson wrote:
> does it work to just use binary and then
Imho, choose based on what makes the implementation better. If the
parser can be written in a simpler (and probably faster) way by
dropping support for ratios in uncommon bases, then let's do it. Tbh,
I don't think any ratios other than those on the format int1/int2
needs to be supported.
I think there is value in having such in important word (string>number)
have a documented behavior. Right now it's hard to document all the things
that are correctly parsed by this word...
Jon
On Wed, Oct 26, 2016 at 9:40 AM, Björn Lindqvist wrote:
> Imho, choose based on
A Factor version of the C function Beached is posting would be a nice
addition to the windows.privileges vocab.
2016-10-25 23:05 GMT+02:00 Doug Coleman :
> Take a look at basis/windows/privileges/privileges.factor and
>
Hello! I'd like to parse some log-files created by an old-style DOS program.They contain pseudographics characters for drawing frames and tables.Technically, that's not ASCII, but a superset with all 8 bits used.Do we have an 8-bit encoding that would support that? I took a look at the