Re: [PD-dev] corelibs, build system
On Oct 9, 2006, at 12:21 PM, IOhannes m zmoelnig wrote: Hans-Christoph Steiner wrote: what i did (try to) do, was to modify your build system in a way, that it could handle both cases. (and the build system has serious problems with this) Is this urgent? well no, but pd-0.40.1 is out now... How about waiting until we get the 0.39.2 Pd-extended release out, then we can switch externals/corelibs to work with 0.40 with no need for kludges to support 0.39.2. i see. i was interested in making both work at the same time, while you were interested in making a release asap. i think both standpoints are valid. (i don't try to prove that "i was right", i just try to explain why i did what i did) I don't think we should waste time on backwards compatibility for the build environment for things like that. Maybe in the future there will be a reason to do that, but for now we have better things to do. If someone wants to build an old version, they can always checked out the sources from CVS. Miller and I have been talking about how to make Pd-extended and his build systems more in sync. Right now, there are patches to pd/src that are required to make things build. If its possible to build Pd- extended against pd/src without patches, then everything becomes much easier to work with, and issues like these should be easier to deal with. So that I think it the most pressing issue in this regard. .hc "[W]e have invented the technology to eliminate scarcity, but we are deliberately throwing it away to benefit those who profit from scarcity."-John Gilmore ___ PD-dev mailing list PD-dev@iem.at http://lists.puredata.info/listinfo/pd-dev
[PD-dev] [ pure-data-Bugs-1573656 ] $arg-expansion gives error with old patches
Bugs item #1573656, was opened at 2006-10-09 07:06
Message generated for change (Comment added) made by matju
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=478070&aid=1573656&group_id=55736
Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: puredata
Group: v0.40.1
Status: Open
Resolution: None
Priority: 5
Submitted By: IOhannes m zm�lnig (zmoelnig)
Assigned to: Miller Puckette (millerpuckette)
Summary: $arg-expansion gives error with old patches
Initial Comment:
with the advent of the new and better $arg-expansion
(namely: expansion of $args _within_ an argument, like
bla-$2-blu), old patches (<0.40) that used dollars
within symbols are somewhat broken.
example1: iemlib provides an object [parentdollarnull]
with an alias [parent$0]; the latter gets expanded
(e.g. to [parent1003]) and cannot be created.
THIS IS NO BUG (imho)
however, $0 is not only expanded on a logic level, but
also on a visible level (i really see [parent1003]);
this i believe IS a bug.
example2 (more important!): in the olde times, if a
symbol contained dollars within, it was saved (in the
.pd file) like "bla-$2-blu".
in pd=0.40.0, the same symbol gets saved as
"bla-\$2-blu" (note the backslash).
loading an old abstraction yields an error ("argument
out of range"), even if enough arguments (in this case:
2) are supplied.
the expansion works correctly though!
imho, either the warning should be supressed or the old
behaviour (no expansion) should be preserved.
(it would be good if the pd-version at the time of
saving would be stored in the .pd-fileformat in order
to allow such things)
this little script should replace all "$" with a
missing backslash at the beginning with "\$"
find . -name "*.pd" | while read f
do
sed -i -e 's|\([^\\]\)\$|\1\\$|g' $f
done
note on the script: i haven't done excessive testing,
but it seems to work; make backups before you apply it,
since it will change all affected files without asking)
note: it seems like old versions (tested with
pd-0.39-2) seem to be able to correctly read files
saved with pd-0.40-0
--
Comment By: Mathieu Bouchard (matju)
Date: 2006-10-09 12:45
Message:
Logged In: YES
user_id=801174
PureUnity uses dollar-expansion in class names, so an
exception cannot be made for class names, especially because
PureUnity has no other way to implement its feature set.
I call this feature "abstraction templates" or "class
templates": [f.swap], [~.swap], [#.swap] are like
swap, swap, swap would be in C++.
--
Comment By: IOhannes m zm�lnig (zmoelnig)
Date: 2006-10-09 07:11
Message:
Logged In: YES
user_id=564396
also confirmed with 0.40.1
--
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=478070&aid=1573656&group_id=55736
___
PD-dev mailing list
PD-dev@iem.at
http://lists.puredata.info/listinfo/pd-dev
Re: [PD-dev] corelibs, build system
Hans-Christoph Steiner wrote: what i did (try to) do, was to modify your build system in a way, that it could handle both cases. (and the build system has serious problems with this) Is this urgent? well no, but pd-0.40.1 is out now... How about waiting until we get the 0.39.2 Pd-extended release out, then we can switch externals/corelibs to work with 0.40 with no need for kludges to support 0.39.2. i see. i was interested in making both work at the same time, while you were interested in making a release asap. i think both standpoints are valid. (i don't try to prove that "i was right", i just try to explain why i did what i did) mfga.dsr IOhannes ___ PD-dev mailing list PD-dev@iem.at http://lists.puredata.info/listinfo/pd-dev
Re: [PD-dev] corelibs, build system
On Oct 4, 2006, at 4:30 AM, IOhannes m zmoelnig wrote: Hans-Christoph Steiner wrote: did not ask at all. d_mayer_fft.c is the name of the file in 0.39.2. You have broken compilation for Pd-extended. because corelibs IS broken, even without my changes (which tried to fix what was going on) Check the build logs from the auto-build farm for the past 2 months. I had been building fine on every platform. This is really, really i do not doubt that pd-0.39-2 has built fine. however, times are a-changing, like the pd source code, and d_mayer_fft.c is nowadays called d_fft_mayer.c what i did (try to) do, was to modify your build system in a way, that it could handle both cases. (and the build system has serious problems with this) Is this urgent? How about waiting until we get the 0.39.2 Pd- extended release out, then we can switch externals/corelibs to work with 0.40 with no need for kludges to support 0.39.2. .hc The arc of history bends towards justice. - Dr. Martin Luther King, Jr. ___ PD-dev mailing list PD-dev@iem.at http://lists.puredata.info/listinfo/pd-dev
[PD-dev] [ pure-data-Patches-1564800 ] a few old MACOSX macros have crept back in
Patches item #1564800, was opened at 2006-09-25 03:57 Message generated for change (Comment added) made by zmoelnig You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=478072&aid=1564800&group_id=55736 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: puredata Group: bugfix >Status: Closed >Resolution: Accepted Priority: 5 Submitted By: Hans-Christoph Steiner (eighthave) Assigned to: Miller Puckette (millerpuckette) Summary: a few old MACOSX macros have crept back in Initial Comment: A few of the old MACOSX manually defined macros have crept back into the source. Everywhere else, its __APPLE__ which is the preferred macro to use, plus it automatically defined. The attached patch replaces the offending macros. -- >Comment By: IOhannes m zm�lnig (zmoelnig) Date: 2006-10-09 13:15 Message: Logged In: YES user_id=564396 seems to be fixed in 0.40.1 -- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=478072&aid=1564800&group_id=55736 ___ PD-dev mailing list PD-dev@iem.at http://lists.puredata.info/listinfo/pd-dev
[PD-dev] [ pure-data-Bugs-1573656 ] $arg-expansion gives error with old patches
Bugs item #1573656, was opened at 2006-10-09 13:06
Message generated for change (Comment added) made by zmoelnig
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=478070&aid=1573656&group_id=55736
Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: puredata
>Group: v0.40.1
Status: Open
Resolution: None
Priority: 5
Submitted By: IOhannes m zm�lnig (zmoelnig)
Assigned to: Miller Puckette (millerpuckette)
Summary: $arg-expansion gives error with old patches
Initial Comment:
with the advent of the new and better $arg-expansion
(namely: expansion of $args _within_ an argument, like
bla-$2-blu), old patches (<0.40) that used dollars
within symbols are somewhat broken.
example1: iemlib provides an object [parentdollarnull]
with an alias [parent$0]; the latter gets expanded
(e.g. to [parent1003]) and cannot be created.
THIS IS NO BUG (imho)
however, $0 is not only expanded on a logic level, but
also on a visible level (i really see [parent1003]);
this i believe IS a bug.
example2 (more important!): in the olde times, if a
symbol contained dollars within, it was saved (in the
.pd file) like "bla-$2-blu".
in pd=0.40.0, the same symbol gets saved as
"bla-\$2-blu" (note the backslash).
loading an old abstraction yields an error ("argument
out of range"), even if enough arguments (in this case:
2) are supplied.
the expansion works correctly though!
imho, either the warning should be supressed or the old
behaviour (no expansion) should be preserved.
(it would be good if the pd-version at the time of
saving would be stored in the .pd-fileformat in order
to allow such things)
this little script should replace all "$" with a
missing backslash at the beginning with "\$"
find . -name "*.pd" | while read f
do
sed -i -e 's|\([^\\]\)\$|\1\\$|g' $f
done
note on the script: i haven't done excessive testing,
but it seems to work; make backups before you apply it,
since it will change all affected files without asking)
note: it seems like old versions (tested with
pd-0.39-2) seem to be able to correctly read files
saved with pd-0.40-0
--
>Comment By: IOhannes m zm�lnig (zmoelnig)
Date: 2006-10-09 13:11
Message:
Logged In: YES
user_id=564396
also confirmed with 0.40.1
--
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=478070&aid=1573656&group_id=55736
___
PD-dev mailing list
PD-dev@iem.at
http://lists.puredata.info/listinfo/pd-dev
[PD-dev] [ pure-data-Bugs-1573656 ] $arg-expansion gives error with old patches
Bugs item #1573656, was opened at 2006-10-09 13:06
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=478070&aid=1573656&group_id=55736
Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: puredata
Group: v0.40.0
Status: Open
Resolution: None
Priority: 5
Submitted By: IOhannes m zm�lnig (zmoelnig)
Assigned to: Miller Puckette (millerpuckette)
Summary: $arg-expansion gives error with old patches
Initial Comment:
with the advent of the new and better $arg-expansion
(namely: expansion of $args _within_ an argument, like
bla-$2-blu), old patches (<0.40) that used dollars
within symbols are somewhat broken.
example1: iemlib provides an object [parentdollarnull]
with an alias [parent$0]; the latter gets expanded
(e.g. to [parent1003]) and cannot be created.
THIS IS NO BUG (imho)
however, $0 is not only expanded on a logic level, but
also on a visible level (i really see [parent1003]);
this i believe IS a bug.
example2 (more important!): in the olde times, if a
symbol contained dollars within, it was saved (in the
.pd file) like "bla-$2-blu".
in pd=0.40.0, the same symbol gets saved as
"bla-\$2-blu" (note the backslash).
loading an old abstraction yields an error ("argument
out of range"), even if enough arguments (in this case:
2) are supplied.
the expansion works correctly though!
imho, either the warning should be supressed or the old
behaviour (no expansion) should be preserved.
(it would be good if the pd-version at the time of
saving would be stored in the .pd-fileformat in order
to allow such things)
this little script should replace all "$" with a
missing backslash at the beginning with "\$"
find . -name "*.pd" | while read f
do
sed -i -e 's|\([^\\]\)\$|\1\\$|g' $f
done
note on the script: i haven't done excessive testing,
but it seems to work; make backups before you apply it,
since it will change all affected files without asking)
note: it seems like old versions (tested with
pd-0.39-2) seem to be able to correctly read files
saved with pd-0.40-0
--
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=478070&aid=1573656&group_id=55736
___
PD-dev mailing list
PD-dev@iem.at
http://lists.puredata.info/listinfo/pd-dev
