8 messages in at.iem.pd-devRe: [PD-dev] CVS addition: -helppath| From | Sent On | Attachments |
|---|---|---|
| Adam Lindsay | Feb 19, 2003 5:21 pm | |
| Adam Lindsay | Feb 20, 2003 5:41 am | |
| Frank Barknecht | Feb 20, 2003 6:16 am | |
| guenter geiger | Feb 20, 2003 8:39 am | |
| Adam Lindsay | Feb 20, 2003 9:35 am | |
| Frank Barknecht | Feb 20, 2003 9:58 am | |
| Adam Lindsay | Feb 20, 2003 10:15 am | |
| guenter geiger | Feb 21, 2003 1:48 am |
| Subject: | Re: [PD-dev] CVS addition: -helppath | |
|---|---|---|
| From: | guenter geiger (gei...@xdv.org) | |
| Date: | Feb 21, 2003 1:48:41 am | |
| List: | at.iem.pd-dev | |
On Thu, 20 Feb 2003, Adam Lindsay wrote:
1) Put it in m_imp.h 2) Put a declaration on top of the file where you use the function.
Thanks. That's an important coding guideline.
If you take it as a coding guideline, forget about option 2. Its a hack.
The way I use the helppath namelist is to initialise it with the pd path + /doc/5.reference (so it works as normal).
If I want to, for example, add pddp help patches without overwriting the original pd help patches, I can put them in another directory, and then add that directory as another line in my .pdrc. I personally would use these -path and -helppath directives to keep the pd installation "clean" and then point to other directories for externals and their help patches.
I might be wrong, have to check before complaining actually ...
I'm not sure I understood your question. I hope I approached a little of the "why", though.
Yes, the "why" answers my question perfectly. Keeping the pd installation clean, makes a lot of sense, definitely. Especially on architecture where this issue is not handled by the installer.
Guenter