StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PODo Scala libraries follow the same inverted domain convention for naming packages as Java?
primarykey
Id
774979
data
AcceptedAnswerId
774981
AnswerCount
2
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2009-04-21T22:40:18.537
FavoriteCount
1
LastActivityDate
2009-04-21T23:44:50.113
LastEditDate
LastEditorUserId
0
OwnerUserId
48837
ParentId
0
PostTypeId
1
Score
6
ViewCount
689
LastEditorDisplayName
text
Body
I'm looking to write a small Scala library to get a feel for its Actor programming model. In the example code I've come across, some libraries use inverted domain (e.g. org.foo.bar) for packages and some do not (maybe just for brevity). Is it advisable for Scala libraries to use the same package naming conventions as Java? More generally, are there any good Scala coding style suggestions like Python has with <a href="http://www.python.org/dev/peps/pep-0008/" rel="nofollow noreferrer">PEP 8</a>? Yes, probably putting cart before horse, but I find I can get a decent feel for a language by also seeing some of the conventions that have shaken out. Thanks
Tags
<scala><coding-style><naming-conventions><packages>
Title
Do Scala libraries follow the same inverted domain convention for naming packages as Java?
singulars
PostAcceptedAnswerId
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
PostParentId
1. This table or related slice is empty.
PostTypePostTypeId
1. PTQuestion
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USJoe Holloway
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
2. PO
 singulars
 PostTypePostTypeId
 PTAnswer
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PODo Scala libraries follow the same inverted domain convention for naming packages as Java?
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
2. VO
 singulars
 PostPostId
 PODo Scala libraries follow the same inverted domain convention for naming packages as Java?
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
3. VO
 singulars
 PostPostId
 PODo Scala libraries follow the same inverted domain convention for naming packages as Java?
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId
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.