[PD-dev] help me with my DLL snafu

[Mathieu Bouchard]

On Wed, 21 Dec 2005, Martin Peach wrote:

> Then inside pd/src would be a set of platform-specific subdirectories
> containing the code that only works on one platform, replacing the
> #ifdef system currently in use, which is difficult to maintain outside
> of m_pd.h. (s_loader.c currently has six ifdef variants and uses six
> file extensions).

I don't think it's that useful to separate the code so much. What really
helps readability is when only whole functions get #ifdef'd, instead of
having a mess of #ifdefs inside one huge function. This doesn't have to 
incur much code duplication, as new functions can be thought out to 
represent the platform-specific tasks as closely as possible.

Stuff like using separate files and separate directories is optional and
doesn't have much of an impact -- especially separate directories.

For executables, the dynamics is different, as it's not possible to easily 
merge two pd libraries. Either using different suffixes or different 
directories would be ok with me.

> Given that files with .pd suffix have the same function for all
> platforms, using .pd_ext for externs and maybe .pd_lib for libraries
> makes sense to me.

Pd doesn't think of externs and libraries as being different things. 
However, some users do.

 _ _ __ ___ _____ ________ _____________ _____________________ ...
| Mathieu Bouchard - tél:+1.514.383.3801 - http://artengine.ca/matju
| Freelance Digital Arts Engineer, Montréal QC Canada