Talk About Network

Google


Register and Login
Nick
Password
Register create new account Sign up is FREE and you can post replies, new topics, bookmark posts and more!
Recover lost password


Programming > Modula 3 > Re: Packaging p...
Latest [ Topics | Posts ] Archive Post A New Topic Post a Reply
<< Topic < Post Post 5 of 5 Topic 76 of 149
Post > Topic >>

Re: Packaging problems with CM3

by Olaf Wagner <wagner@[EMAIL PROTECTED] > Jan 10, 2004 at 01:35 PM

Thomas Tensi <t.tensi@[EMAIL PROTECTED]
> wrote:
> Dear all,


> first of all thanks to Henning and Olaf for their answers.

> Let me summarize what I think I have understood about CM3
> packaging from the discussion with some additional comments:
[...]
> Is this correct?
An excellent summary.

> Additional questions:

>    - Shall the ****pped sources be used for rebuilding the
>      system or are they for do***entation purposes only?  If
>      the latter, why do we ****p all modules and why any
>      program sources at all (html-files would suffice)?
The builder only needs the derived files and some timestamp
information, the ****pped sources are for do***entation only.
Source is shorter than HTML, and there is the m3browser
program, which produces HTML pages frm the ****pped code
and its dependencies (down to type level).

>    - Do we need a generally agreed hierarchical package
>      structure for Modula3? A good example would be Java
>      where e.g. "java.awt" signifies some package for user
>      interfaces with subpackages for its specific aspects.
>      This package structure to be defined can only be found
>      in quake files; I do not propose any change in the
>      programming language.  Modules should still remain the
>      top level structure in Modula-3.
Not necessarily, but it would help to maintain the CM3 and PM3
code distributions. An attempt at a new hierarchy should IMO
start with providing the necessary infrastructure (quake code,
scripts etc.) for PM3 and CM3 to build packages within the
new hierarchy without much hassle, and then continue with
incrementally moving packages from the old code sets into
the new repository, while eliminating differences.

BTW, I have always found the complex PM3 hierarchy and its
internal dependencies a bit confusing, but that does not
mean that the CM3 package structure is necessarily better,
it's just simpler.

> Or is everything okay the way it is now?
Well, everything can be improved, and `better' is the enemy
of `good'. If you intend to work on a new hierarchy structure,
that will be appreciated by many people, I think. But you
should post a detailed plan of your work here and/or to the
m3devel mailing list, so other users can comment on it and
(perhaps) improve it.

Olaf
-- 
/\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
|| Olaf Wagner           | wagner(at)luthien.in-berlin.de (priv.)|
|| Cranachstrasse 7      | wagner(at)elego.de (business)         |
|| D-12157 Berlin        | phone: +49 30  85 60 26 70            | 
|| Germany / Deutschland | fax:   +49 30  85 58 01 88            | 
\/////////////////////////////////////////////////////////////////
 




 5 Posts in Topic:
Packaging problems with CM3
Thomas Tensi <t.tensi@  2004-01-05 14:42:17 
Re: Packaging problems with CM3
Henning Thielemann <ia  2004-01-07 12:57:55 
Re: Packaging problems with CM3
Olaf Wagner <wagner@[E  2004-01-08 22:02:32 
Re: Packaging problems with CM3
Thomas Tensi <t.tensi@  2004-01-09 12:40:44 
Re: Packaging problems with CM3
Olaf Wagner <wagner@[E  2004-01-10 13:35:36 

Post A Reply:
  Go here to Signup

AddThis Feed Button


About - Advertising - Contact - Frequently Asked Questions - Privacy Policy - Terms of Use - Signup

Contact
tan12V112 Fri Jul 25 0:19:16 CDT 2008.