[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Documentation of Architecture / Design?

From: Douglas A Linhardt
Subject: Re: Documentation of Architecture / Design?
Date: Fri, 19 Mar 2004 15:55:14 -0600
User-agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.0.1) Gecko/20020823 Netscape/7.0 (CK-LucentTPES)


It wouldn't hurt.  But that's not really what I'm approaching.  My point wasn't
so much that the code needs to be cleaned up, but that there should be a web
page / document / something that a developer can refer to to know where to look.

In this example, I couldn't immendiately find VIRTUAL_COPY_CONSTRUCTOR().  It
took me a couple of minutes to remember that there is a /flower directory, and I
found it there.  I'm not suggesting that /flower be removed.  This is just a
minor annoyance that a newbie (I) will learn from.  But it shows that more
direction can be made available to developers.

When you start getting into the macros like (lily-guile.hh):

                static SCM NAME ARGS; \
                static SCM NAME ## _proc

that things really start getting confusing.  When I see the following snippet of
        == Percent_repeat_iterator::constructor_proc

I have a function that hasn't declared (sort of).  And when I see the following
snippet of Scheme code:

        (iterator-ctor . ,Percent_repeat_iterator::constructor)

I'm really confused.  When macro arguments are concatenated to form new tokens,
there should be, at minimum, some comments describing what's being created.  And
having an outside reference that talks about it would give a developer a hint of
what lies ahead.

I like the freedom of coding without worrying about comments, too.  But with a
project this size with multiple volunteer developers in multiple time zones,
some sort of umbrella design document would not be a bad idea.


On 3/19/2004 3:09 PM, Han-Wen Nienhuys wrote:
> address@hidden writes:
>>Probably the biggest things that threw me are the C++ member functions that 
>>declared/defined through macros.  It's really annoying when a member function 
> would it help if we changed VIRTUAL_COPY_CONSTRUCTOR() , ie going from 
> to
>    Base *clone () const { return new Name (*this); }
> ?

reply via email to

[Prev in Thread] Current Thread [Next in Thread]