From edd at debian.org  Mon Oct  3 23:55:56 2016
From: edd at debian.org (Dirk Eddelbuettel)
Date: Mon, 3 Oct 2016 16:55:56 -0500
Subject: [Rd] On implementing zero-overhead code reuse
In-Reply-To: <CAFvQaj69J8SuA3uirTa_jpY6JjUZb0DsPiFe5eru=ZbZTS_uLg@mail.gmail.com>
References: <22513.41953.204280.605359@max.nulle.part>
	<CAFvQaj6=UUWafXD5asf-mtho7O1qKs9TLpWmLRdmEhGYh1exVw@mail.gmail.com>
	<CAFvQaj4SLxim=Jqi_yeOrKTRvuhWB7X-C6xXjpCw_pbmfz_=3Q@mail.gmail.com>
	<20161003141859.GV9995@ofb.net>
	<CAC2h7usFJCN1R+Fw_8oaBb37dJdQO5FRLiSgh8tZ_V30nGBmNg@mail.gmail.com>
	<CAFvQaj69J8SuA3uirTa_jpY6JjUZb0DsPiFe5eru=ZbZTS_uLg@mail.gmail.com>
Message-ID: <22514.54252.986532.619094@max.nulle.part>


Kynn,

You appear confused by the meaning of the word "optional".

All the things I listed for packages are additional features you _may_ use,
not onces that are imposed on you so that they _must_ be used.

Lastly, I forgot to mention NAMESPACE support.  Which gives pretty much
exactly what you outlined at the beginning of your post as a desiderata.

But it seems you know full well what you need, so by all means do charge full
speed ahead.  But before I close allow me to reiterate that you are somewhat
ill-informed.

Packages do not impose anything. Asking to be included in a high-quality
repository such as CRAN does.

For local and personal packages you can be precisely as ad-hoc as you are in
sourced files.  Yet you still have access to the very framework that gives
you _options_ for more structure.

Dirk

-- 
http://dirk.eddelbuettel.com | @eddelbuettel | edd at debian.org



[Rd] On implementing zero-overhead code reuse
Dirk Eddelbuettel