Question

The basic usage of a library is by defining its name like:

#library('Name');

In my case, I’d like to define “nested” or “deeper” library hierarchies. So if I had a framework called Foo and let’s say I build library Messenger:

#library('Messenger');

I’m afraid that would conflict with something else. What I’m looking for is something like:

#import('Foo.Messenger');

So that it’s clear the messenger library is part of a Foo set of libraries.

What’s the recommended way to approach this? As I understand, people would refer to your library like:

#import('package:Foo.Messenger')

Answer 1

Librarires will change soon, see http://news.dartlang.org/2012/07/draft-spec-changes-to-library-and.html. Note that your question is answered in this document, as it says: Names of libraries intended for widespread use should follow the well known reverse internet domain name convention.