[#18121] [Ruby 1.8.7 - Bug #405] (Open) ssl.rb:31: [BUG] Bus Error — Anonymous <redmine@...>

Issue #405 has been reported by Anonymous.

14 messages 2008/08/04

[#18130] Re: New array methods cycle, choice, shuffle (plus bug in cycle) — Brian Candler <B.Candler@...>

> Seriously though... Array.first is a noun.

10 messages 2008/08/05

[#18319] NEW Command: absolute_path() -- — "C.E. Thornton" <admin@...>

Core,

14 messages 2008/08/16
[#18321] Re: NEW Command: absolute_path() -- — Yukihiro Matsumoto <matz@...> 2008/08/18

Hi,

[#18381] [Bug #496] DRb.start_service(nil) is very slow — Hongli Lai <redmine@...>

Bug #496: DRb.start_service(nil) is very slow

11 messages 2008/08/25

[ruby-core:18345] Re: NEW Command: absolute_path() --

From: Matthew Boeh <mboeh@...>
Date: 2008-08-19 19:56:25 UTC
List: ruby-core #18345
On Wed, Aug 20, 2008 at 04:39:45AM +0900, Pit Capitain wrote:
> 2008/8/19 Trans <transfire@gmail.com>:
> > Is this common practice? I mean it seems like a sucky edge case to
> > have to fuss with. Why not just have a separate method for that, say
> >
> >  File.home_path('thornton')
>=20
> +1
>=20
> Though it might be common unix practice, Ruby could/should have a more
> explicit way to get at the home path of a user. I think there's no
> need to encode this in a file naming scheme. Can anyone show me a use
> case where it would be more appropriate to have the existing behaviour
> instead of a separate method?

User input:

  config =3D YAML.load(File.read(config_file_path))
  destination_path =3D File.expand_path(config["destination_path"])

I've always understood File.expand_path to be intended for this kind of use=
,=20
where a user might plausibly expect to be able to use the kind of expansion=
s=20
they can in the Bourne shell.=20

--
Matthew Boeh

Attachments (1)

signature.asc (189 Bytes, application/pgp-signature)

In This Thread