[#29911] [Bug #3231] Digest Does Not Build — Charlie Savage <redmine@...>

Bug #3231: Digest Does Not Build

19 messages 2010/05/01

[#29920] [Feature #3232] Loops (while/until) should return last statement value if any, like if/unless — Benoit Daloze <redmine@...>

Feature #3232: Loops (while/until) should return last statement value if any, like if/unless

9 messages 2010/05/01

[#29997] years in Time.utc — Xavier Noria <fxn@...>

Does anyone have a precise statement about the years supported by

13 messages 2010/05/04

[#30010] [Bug #3248] extension 'tk' is finding tclConfig.sh and tkConfig.sh incorrectly — Luis Lavena <redmine@...>

Bug #3248: extension 'tk' is finding tclConfig.sh and tkConfig.sh incorrectly

9 messages 2010/05/05

[#30226] [Bug #3288] Segmentation fault - activesupport-3.0.0.beta3/lib/active_support/callbacks.rb:88 — Szymon Jeż <redmine@...>

Bug #3288: Segmentation fault - activesupport-3.0.0.beta3/lib/active_support/callbacks.rb:88

10 messages 2010/05/13

[#30358] tk doesn't startup well in doze — Roger Pack <rogerdpack2@...>

Currently with 1.9.x and tk 8.5,the following occurs

12 messages 2010/05/22

[ruby-core:30357] Re: suggestion: switch default name for BINARY encoding

From: Roger Pack <rogerdpack2@...>
Date: 2010-05-22 00:13:49 UTC
List: ruby-core #30357
>> Currently the encoding ASCII-8BIT "means" ascii and binary.
>
> No. ASCII-8BIT means ASCII compatible 8bit string; it has 256 characters.

I believe it actually means two things, depending on context, no?


> No. ASCII-8BIT is not a default in Ruby.
> You may confused by the fact that rb_str_new returns ASCII-8BIT string
> and old extension library returns such strings.

BINARY is the default, when you pass an encoding of nil...seems like
it's the default..
Apparently BINARY means "unencoded bytes" which happens to be the same
encoding as ASCII-8BIT

>> Beginners have no idea what ASCII-8BIT means. ut they do understand
>> BINARY.
>
> ASCII-8BIT is different from the thing people will imagine by the name
> "BINARY",
> even if it aliased as BINARY.

Good point, actually.  I take back my suggestion.

However it is a bit confusing to have binary data (File.binread 'x')
and have it come back to you as ASCII-8BIT.  A jpeg image, for
example, is *not really* ASCII-8BIT.  It happens to have the same
encoding, however.

...
> The name "BINARY" can't express it is ASCII-compatible.

I think that the ambiguity is that "ASCII-8BIT" typically means "just
some data--it might be a string, it might be binary" so it's hard to
have a good name for its encoding.

Maybe we can call it ASCII-8BIT-BINARY? Or maybe UNKNOWN or
UNSPECIFIED or something...

I'd be ok with that.  We could alias the others...

Thoughts?
-rp

In This Thread