> On 14 Mar 2018, at 16:40, Denis Kudriashov <[email protected]> wrote:
>
> Hi.
>
> I look at hierarchy of PackageManifest and I was wondering that all these
> classes are commented but most of packages which they describe are not.
>
> Also interesting that most of manifest comments are same.
>
> Then I found that package comment is managed as special class side method
> #description which is generated when you call "aPackage packageComment:
> 'test'".
>
> Now the idea: will not it be better to manage package comment as manifest
> class comment?
>
> Manifest is already responsible to describe the package. So it looks logical
> to have "manifest comment = package comment".
> Also it will simplify code and remove duplication of texts.
> In addition it will add extra place indicating that package needs to be
> commented because uncommented classes are marked in the browser.
>
> What you think?
>
I would say yes… this would save actually space: lots of methods removed, and
the string would be stored on disk instead
of inside the image.
Marcus
