From: Ilias Lazaridis <ilias@...>
Date: 2011-06-18T00:45:26+09:00
Subject: Re: RFC - One word alias for require_relative

On 11 Ιούν, 20:35, Ilias Lazaridis <il...@lazaridis.com> wrote:
> This is a simple Request for Comments.
>
> Scenario:
>
> require_relative 'lib/alter'
> require 'alibrary'
>
> Some project manager complains about "require_relative", and asks you
> to find a one-word alias.
>
> Which name would you select and for what reasons?
>
> Requirements
> must:
> * one word
>
> optional:
> * ideally a 7 letter word

My own suggestions didn't pass the requirements.

I order the list

involve 'lib/alter' # 2011-06-16 by Sam Duncan
locally 'lib/alter' # 2011-06-11 by Rob Biedenharn
uniload 'lib/alter' # my
request 'lib/alter' # my
include 'lib/alter' # my
relative 'lib/alter' # my

-

Original situation of headers

require_relative "lib/baselib"
require "sinatra"

Use of "involve" results in very clean headers:

involve "lib/baselib"
require "sinatra"

-

Applying the change:

module Kernel
  alias involve require_relative
end

-

Btw: I am the project-manager (on my own project), and as I'm alone
for now, I had to fulfil the role of the executing project-member as
well (posting this RFC here).

This thread gives additionally some valuable insights subjecting the
topic "trolling" and "trolls", uncovering some "trouble-makers" of
comp.lang.ruby (or ruby-talk).

Many thanks to the very few people which managed to stay in-topic and
in-context.

Time to close this thread.

.

--
http://lazaridis.com