Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    singulars
    1. This table or related slice is empty.
    1. POC++ External Declaration Isolation
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USQuuxplusone
    1. USQuuxplusone
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COThanks for your answer. Actually, the idea is _not_ having `Lib3::func3()` declared at all -- not inside `Lib3` anyway, but either, _somehow_, at `Lib1`, or at some function (or class) local scope. Let me draw your attention to the C linkage case: albeit `func2()` is _declared inside_ `Lib1`, it refers to something _outside_ `Lib1` -- I wondered if it was possible to do the same with C++-linked entities. However, by looking at the progress of the question, I feel that there is no solution to the problem at the syntax level, but only at the link level, if any (some symbol renaming or the sort).
      singulars
      1. PO
      1. USalecov
    2. COIn other words, you want the effect of `using`, but then *also* you want to prevent Lib1's users from using Lib3 directly? Sometimes this effect can be achieved with `#define Lib3 __Lib3_internal_to_Lib1 ; #include <Lib3.h> ; #undef Lib3`.
      singulars
      1. PO
      1. USQuuxplusone
    3. COIn fact I want to allow `Lib1`'s users to use `Lib3` directly, however `Lib1` itself is _independent_ from any header file from `Lib3` (and does not declare anything inside the `Lib3` namespace whatsoever). This is what happens in the C case: `Lib1` accesses the C interface, and allows anyone else to include `Lib2.h` at will (because anything `Lib1` declares, which relates to `Lib2`, is inside `Lib1`). So I need to refer to `Lib3` entities with local visibility only (either at local scope or inside the `Lib1` library namespace). Also, the `#define` trick would ensue link errors, wouldn't it?
      singulars
      1. PO
      1. USalecov
 

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