On Thu, Feb 24, 2011 at 11:51:30AM -0500, DJ Delorie wrote:
>
> > I'd not constrain ourselves to one action per file, but certainly
> > breaking things down by topic would be a good idea.
>
> Perhaps one file per action for stand-alone actions, and one file per
> group named after the group's common action prefix for groups. I.e:
>
> teardrops.c for Teardrops()
>
> but
>
> element.c for ElementList() and ElementSetAttr()
>
> I want some correlation between file name and action name, to prevent
> future conflicts.
That is reasonable. One file for "group" of commands which can be simply
described by one filename.
Martin Kupec
_______________________________________________
geda-user mailing list
geda-user@moria.seul.org
http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
