Databases
StackOverflow2013
Postsdbo
POWhy are classes inside Scala package objects dispreferred?
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POWhy are classes inside Scala package objects dispreferred?
    primarykey
    data
    text
    <p>Starting with 2.10, <code>-Xlint</code> complains about classes defined inside of package objects. But why? Defining a class inside a package object should be exactly equivalent to defining the classes inside of a separate package with the same name, except a lot more convenient.</p> <p>In my opinion, one of the serious design flaws in Scala is the inability to put anything other than a class-like entity (e.g. variable declarations, function definitions) at top level of a file. Instead, you're forced to put them into a separate ''package object'' (often in <code>package.scala</code>), separate from the rest of the code that they belong with and violating a basic programming rule which is that conceptually related code should be physically related as well. I don't see any reason why Scala can't conceptually allow anything at top level that it allows at lower levels, and anything non-class-like automatically gets placed into the package object, so that users never have to worry about it.</p> <p>For example, in my case I have a <code>util</code> package, and under it I have a number of subpackages (<code>util.io</code>, <code>util.text</code>, <code>util.time</code>, <code>util.os</code>, <code>util.math</code>, <code>util.distances</code>, etc.) that group heterogeneous collections of functions, classes and sometimes variables that are semantically related. I currently store all the various functions, classes, etc. in a <code>package object</code> sitting in a file called <code>io.scala</code> or <code>text.scala</code> or whatever, in the <code>util</code> directory. This works great and it's very convenient because of the way functions and classes can be mixed, e.g. I can do something like:</p> <pre><code>package object math { // Coordinates on a sphere case class SphereCoord(lat: Double, long: Double) { ... } // great-circle distance between two points def spheredist(a: SphereCoord, b: SphereCoord) = ... // Area of rectangle running along latitude/longitude lines def rectArea(topleft: SphereCoord, botright: SphereCoord) = ... // ... // ... // Exact-decimal functions class DecimalInexactError extends Exception // Format floating point value in decimal, error if can't do exactly formatDecimalExactly(val num: Double) = ... // ... // ... } </code></pre> <p>Without this, I would have to split the code up inconveniently according to fun vs. class rather than by semantics. The alternative, I suppose, is to put them in a normal object -- kind of defeating the purpose of having package objects in the first place.</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USChris Martin
    1. USUrban Vagabond
    plurals
    1. This table or related slice is empty.
    1. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POWhy are classes inside Scala package objects dispreferred?
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POWhy are classes inside Scala package objects dispreferred?
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POWhy are classes inside Scala package objects dispreferred?
      1. This table or related slice is empty.
      1. VTUpMod
    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