Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <blockquote> <p>However, most of the material that I have found about the FBC problem dates back to the late 90s, early 00s, so it makes me wonder if the 'problem' is no longer a major issue.</p> </blockquote> <p>I think it's more that the issue is now well-understood. Similarly, you won't find too many recent papers discussing problems with <code>GOTO</code> and how to address them, not because these problems no longer exist, but because people now know how to avoid them.</p> <blockquote> <p>Is [the proposed class sealing mechanism] not basically the same thing as making classes default/package-private?</p> </blockquote> <p>No. Package-private classes and "sealed" classes are similar in that both cannot be extended by classes outside the package, but they differ in that the former also cannot be <em>used</em> by classes outside the package. That is &mdash; if a class <code>X</code> is package-private, then a class outside its package can't even refer to <code>X</code>: no <code>extends X</code>, no <code>X x = new X()</code>, no <code>Class&lt;X&gt; clazz = X.class</code>. But if it's merely sealed, then a class in a different package cannot write <code>extends X</code>, but can still write <code>X x = new X()</code> and <code>Class&lt;X&gt; clazz = X.class</code> and so on. (Just as important, it can still write <code>X x = new Y()</code>, if <code>Y</code> is a subclass. So it can still take advantage of <code>X</code>'s type hierarchy, even though it itself can't extend <code>X</code>.)</p>
    singulars
    1. This table or related slice is empty.
    1. POHow to avoid the fragile base class in Java
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USruakh
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POHow to avoid the fragile base class in Java
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COThank you ever so much for a great answer!
      singulars
      1. PO
      1. This table or related slice is empty.
    2. CO@talt: You're welcome!
      singulars
      1. PO
      1. USruakh
    3. COOne thing though: the goto statement was omitted when programming languages turned more structured; inheritance is still all over the place. I can't help but wonder if this still non-present sealing mechanism could prove useful in Java after all.
      singulars
      1. PO
      1. This table or related slice is empty.
 

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