Talk:ProposalLibraryDependencies

Revision as of 13:38, 14 November 2006 by Patrickr (Talk | contribs)

--Paulb 21:23, 14 November 2006 (CET)

I don't know if the Examples are going to turn into anything concrete. I don't like a useless "com." prefix. "eiffel." is useless also because it's an Eiffel library. I'm assuming you meant "eiffelsoftware."

My suggestions for naming conventions should be:

<company>.<type>.<name>

  • For EiffelBase: eiffelsoftware.library.base
  • For a utiltiy framework: eiffelsoftware.framework.utilities
  • For the Eiffel parser: eiffelsoftware.eiffel.parser
  • For the Eiffel compiler: eiffelsoftware.eiffel.compiler

--Patrickr 22:37, 14 November 2006 (CET)

My idea was to use the url of the "company" producing the library to be sure that the name is unique, from most general to more specific. So for base from eiffel.com the idea was com.eiffel.base, gobo could then for example be net.sourceforge.gobo.base (basically the same schema that is used in the java world).