From 64fdb009695828b788fce074135b20a5e52c5fc4 Mon Sep 17 00:00:00 2001 From: Thomas Grill Date: Tue, 23 Sep 2003 00:21:28 +0000 Subject: imported version 0.37-0 svn path=/trunk/; revision=1016 --- pd/doc/1.manual/x4.htm | 34 ++++++++++++++++++---------------- 1 file changed, 18 insertions(+), 16 deletions(-) (limited to 'pd/doc/1.manual/x4.htm') diff --git a/pd/doc/1.manual/x4.htm b/pd/doc/1.manual/x4.htm index 5fe5d25d..faaf2f48 100644 --- a/pd/doc/1.manual/x4.htm +++ b/pd/doc/1.manual/x4.htm @@ -1,20 +1,23 @@ + + - -Pd Documentation - - - -
- -
-Pd Documentation chapter 4: writing Pd objects in C -
-
-
back to table of contents
-

+ + Pd Documentation 4 + + + + + + + +

Pd Documentation chapter 4: writing Pd objects in C

+

+ back to table of contents +

+

-You can write your own objects that you and others can use in their Pd +

You can write your own objects that you and others can use in their Pd applications. You can write them in C or (if you're smart and brave) in C++ or FORTRAN. @@ -27,7 +30,7 @@ first in the directory containing the patch, then in directories in its "path." Pd will then add whatever object is defined there to its "class list," which is the set of all Pd classes you can use. If all this works, Pd then attempts again to create the object you asked for, this time perhaps -sucessfully. There is no difference between an object defined this way and an +successfully. There is no difference between an object defined this way and an object built into Pd.

Once you load a new object into Pd, it's there for the duration of your Pd @@ -54,6 +57,5 @@ or bad DLL." Simply recompile Pd under 5.x and the problem goes away. Externs compiled under 5.x and 6.x are binary compatible; it's just the compilation that's sensitive. - -- cgit v1.2.1