[#4076] Ruby/DL — Jamis Buck <jamis_buck@...>

I recently used Ruby/DL to create bindings to the SQLite3 embedded

40 messages 2005/01/03
[#4096] Re: Ruby/DL — Paul Brannan <pbrannan@...> 2005/01/04

On Tue, Jan 04, 2005 at 02:53:49AM +0900, Jamis Buck wrote:

[#4099] Re: Ruby/DL — ts <decoux@...> 2005/01/04

>>>>> "P" == Paul Brannan <pbrannan@atdesk.com> writes:

[#4119] Re: Ruby/DL — Paul Brannan <pbrannan@...> 2005/01/05

On Wed, Jan 05, 2005 at 03:05:48AM +0900, ts wrote:

[#4120] Re: Ruby/DL — ts <decoux@...> 2005/01/05

>>>>> "P" == Paul Brannan <pbrannan@atdesk.com> writes:

[#4125] Re: Ruby/DL — Paul Brannan <pbrannan@...> 2005/01/05

On Thu, Jan 06, 2005 at 01:10:34AM +0900, ts wrote:

[#4116] Test::Unit::Collector::Dir won't work with code that modifies $LOAD_PATH — Eric Hodel <drbrain@...7.net>

Any test code that depends upon modifications of $: fails when used

10 messages 2005/01/05

[#4146] The face of Unicode support in the future — Charles O Nutter <headius@...>

Hello Rubyists!

47 messages 2005/01/06
[#4152] Re: The face of Unicode support in the future — Yukihiro Matsumoto <matz@...> 2005/01/07

Hi,

[#4167] Re: The face of Unicode support in the future — Christian Neukirchen <chneukirchen@...> 2005/01/09

Yukihiro Matsumoto <matz@ruby-lang.org> writes:

[#4175] Re: The face of Unicode support in the future — Yukihiro Matsumoto <matz@...> 2005/01/10

Hi,

[#4186] Re: The face of Unicode support in the future — Paul Brannan <pbrannan@...> 2005/01/11

On Mon, Jan 10, 2005 at 11:53:48PM +0900, Yukihiro Matsumoto wrote:

[#4192] Re: The face of Unicode support in the future — Yukihiro Matsumoto <matz@...> 2005/01/12

Hi,

[#4269] Re: The face of Unicode support in the future — Wes Nakamura <wknaka@...>

19 messages 2005/01/18
[#4270] Re: The face of Unicode support in the future — Yukihiro Matsumoto <matz@...> 2005/01/18

Hi,

[#4275] Re: The face of Unicode support in the future — Wes Nakamura <wknaka@...> 2005/01/19

[#4323] test/unit doesn't rescue a Exception — Tanaka Akira <akr@...17n.org>

test/unit doesn't rescue a Exception in a test method, as follows.

14 messages 2005/01/27
[#8773] Re: test/unit doesn't rescue a Exception — Tanaka Akira <akr@...> 2006/09/02

In article <87is5jb46q.fsf@serein.a02.aist.go.jp>,

[#8776] Re: test/unit doesn't rescue a Exception — "Nathaniel Talbott" <ntalbott@...> 2006/09/03

On 9/1/06, Tanaka Akira <akr@fsij.org> wrote:

[#8777] Re: test/unit doesn't rescue a Exception — Eric Hodel <drbrain@...7.net> 2006/09/03

On Sep 2, 2006, at 6:34 PM, Nathaniel Talbott wrote:

Re: The face of Unicode support in the future

From: Florian Gro<florgro@...>
Date: 2005-01-19 19:47:39 UTC
List: ruby-core #4281
Yukihiro Matsumoto wrote:

> Hi,

Moin.

> |(And I think it would somehow need to work for all possible script 
> |encodings, but I'm not sure if this is possible when all string literals 
> |automatically use the script encoding. This might be a problem.)
> 
> We might need something to denote raw strings (r"" for example).

Hm, I thought about that, but I'm not so sure. E.g. what about %{} style 
literals and so on? While this might be a special case of string 
suffixes, there still could be another and simpler way of doing it. Hm.

I wonder, what format would external Strings be in? (E.g. ones that get 
read via IO or Sockets.) They can not be in the script's encoding in all 
cases because the encodings might not be compatible. If they would 
always use the raw encoding we might be able to get away with not having 
raw strings. I'm not sure if non-script-encoding String literals would 
ever be needed outside of encoding libraries. And those could use 
number.chr(encoding) anyway.

> |Does this mean that #size and #length would do different things or am I 
> |just misunderstanding?
> 
> In the current prototype, it work differently (length gives number of
> code points in the string; size give the length of the byte sequence).
> But I now think they should behave same.

Ah, I agree. I think it would be odd to have things that were synonyms 
so long do different things. Plus getting the byte sequence length could 
still be done with .raw_length or something similar.

> |Hm, what about international method and variable names? (These are 
> |possible with -Ku right now.)
> 
> In this case, we give up those.

In case they're not given up: Would Ruby know about upper and lower case 
in international characters? (E.g. could I have a class named 
底testeKlasse?) And I wonder if it would make sense to provide ways for 
distinguishing class and variable names in cases where there is no case 
differences. (So Japanese names might for example be prefixed with 
special symbols / particles.)

Sorry if this last area is not so important, but I think it is an 
interesting area of thought.

And thanks again for answering in so much detail.


In This Thread