Databases
StackOverflow2013
Postsdbo
PONamespaces without packages
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PONamespaces without packages
    primarykey
    data
    text
    <p>In reorganising my code base I’d like to clean up my code sharing mechanism. So far I’m using <code>source</code> for lots of small, largely self-contained modules of functionality.</p> <p>However, this approach suffers from a number of problems, among them</p> <ul> <li>the lack of tests for circularity (accidental circular <code>source</code> chains),</li> <li>complex syntax required to properly specify include paths (<code>chdir=TRUE</code> argument, hard-coded paths),</li> <li>potential of name clashes (when redefining objects).</li> </ul> <p>Ideally I’d like to get something alike to the Python module mechanism. The R package mechanism would be overkill here: <strong>I do <em>not</em> want to generate nested path hierarchies, multiple files with tons of metadata and manually build the package</strong> just to get a small, self-contained, reusable code module.</p> <p>For now I’m using a code snippet which allows me to solve the first two problems mentioned above. The syntax for inclusion is like this:</p> <pre><code>import(functional) import(io) import(strings) </code></pre> <p>… and a module is defined as a simple source file which resides in the local path. <a href="https://gist.github.com/klmr/5301304" rel="noreferrer">The definition of <code>import</code> is straightforward</a> but I cannot solve the third point: I want to import the module into a separate namespace but from what I see the namespace lookup mechanism is pretty hard-wired to packages. True, I could override <code>`::`</code> or <code>getExportedValue</code> and maybe <code>asNamespace</code> and <code>isNamespace</code> but that feels very dirty and has the potential of breaking other packages.</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. This table or related slice is empty.
    1. USKonrad Rudolph
    plurals
    1. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. PONamespaces without packages
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PONamespaces without packages
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PONamespaces without packages
      1. This table or related slice is empty.
      1. VTUpMod
    1. COCan you expand on why adding each file's contents to a separate environment on the search path (as shown in the examples of `?sys.source`) is insufficient?
      singulars
      1. PONamespaces without packages
      1. USJoshua Ulrich
    2. CO@Joshua That’s actually what I’m doing at the moment (my example was simplified) – I thought that having a way of explicitly qualifying the namespace was nice though. Of course I can do the same with `get` and `assign` but the syntax of `::` is quite a bit nicer.
      singulars
      1. PONamespaces without packages
      1. USKonrad Rudolph
    3. COI was confused because your `import` function doesn't do that. If you put each file's content in a separate environment on the search path, you can access a specific environment with the `$` operator (e.g. `strings$concatenate()`).
      singulars
      1. PONamespaces without packages
      1. USJoshua Ulrich
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload