Re: [PD] [oscparse] parsing address patterns with integers differently

Hi Miller, On 29/10/14 12:51, Chris McCormick wrote: > One alternative would be to make the [f] object accept a subset of > symbols that look like floats so that a user can do an explicit > typecast, printing an error in the event a symbol does not convert > cleanly. Would you hypothetically accep

Re: [PD] [oscparse] parsing address patterns with integers differently

On 29/10/14 12:51, Chris McCormick wrote: > Incidentally, my eyes might be deceiving me but it seems like > pdfloat_float() is defined twice in x_connective.c(.) Ridiculous. I am my own gremlin. Sorry for the noise! Cheers, Chris. -- http://mccormick.cx/ __

Re: [PD] [oscparse] parsing address patterns with integers differently

Hi Miller, On 29/10/14 12:34, Miller Puckette wrote: > Oops, you're right, that acomplished nothing but deeper confusion. > > There should be a way to convert strings <-> floats in vanilla without > making a monstrous ascii-parsing patch. Seems like this shouldn't happen > automatcally (99% of t

Re: [PD] [oscparse] parsing address patterns with integers differently

Oops, you're right, that acomplished nothing but deeper confusion. There should be a way to convert strings <-> floats in vanilla without making a monstrous ascii-parsing patch. Seems like this shouldn't happen automatcally (99% of teh time it's probably a mistake) but there should be a way to do

Re: [PD] [oscparse] parsing address patterns with integers differently

Hi Miller, Yeah but try replacing the 'print' with a float box. Cheers, Chris. On October 29, 2014 12:22:47 PM GMT+08:00, Miller Puckette wrote: >Sorry if this patch gives you nightmares: > >[bang( >| >[oscformat 0] >| >[oscparse] >| >[set $1, bang( >| >[ ( >| >[print] > >Hit the bang, and t

Re: [PD] [oscparse] parsing address patterns with integers differently

Sorry if this patch gives you nightmares: [bang( | [oscformat 0] | [oscparse] | [set $1, bang( | [ ( | [print] Hit the bang, and the empty message box gets a "0", and the print says, "0". cheers Miller On Sun, Oct 26, 2014 at 10:02:17PM +0800, Chris McCormick wrote: > Hi Frank, > > On 13/10/1

Re: [PD] [oscparse] parsing address patterns with integers differently

Hi, On 28/10/14 16:21, Frank Barknecht wrote: > I think, for the way back some external based on atoi(3) or atof(3) is needed. I made the attached monstrosity as an abstraction. Agree this probably needs a native implementation and I think it probably belongs inside Pd like Jonathan said. Cheer

Re: [PD] [PD-announce] Pd 0.46-2 released

I'm sure it's mostly skill on your part. I believe Iohannes got the autotools working, but it probably has contributions from Hans and others. Anyhow, it clearly works when it's in the right context since all the Debian based builds rely on the autotools structure. cheers Miller On Tue, Oct 28

Re: [PD] [oscparse] parsing address patterns with integers differently

On Die, 2014-10-28 at 08:55 -0700, Jonathan Wilkes wrote: > In pd_typedmess of m_class.c, the float handler will currently throw > an error if the arg isn't a float atom. However, this could be > changed so that if the arg is a symbol-atom Pd sends it through a > binbuf "carwash" to check if it co

Re: [PD] [PD-announce] Pd 0.46-2 released

On Die, 2014-10-28 at 09:06 -0700, Miller Puckette wrote: > But my advice is not to use the autotools unless you have to. I'll try to > keep them working but have no idea what I'm doing with them and personally > use the simple makefiles. Funny. I never had a single problem with using autotools

Re: [PD] [PD-announce] Pd 0.46-2 released

Sure, no problem. Sometimes there’s an easy fix and sometimes there isn’t. Luckily this was an easy one :D Hopefully the src.tar.gz package get’s updated ... Dan Wilcox @danomatika danomatika.com robotcowboy.com

Re: [PD] [PD-announce] Pd 0.46-2 released

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 OK, done. It builds just fine now. Thanx. ++ Jack Le 28/10/2014 17:16, Dan Wilcox a écrit : > That commit does a very simple thing which you can do on your own > to get it building. > > Change Makefile.am line 346 from > > doc/5.reference/metro.p

Re: [PD] [PD-announce] Pd 0.46-2 released

That commit does a very simple thing which you can do on your own to get it building. Change Makefile.am line 346 from doc/5.reference/metro.pd \ to doc/5.reference/metro-help.pd \ Then rerun ./configure make Dan Wilcox @danomatika danomatika.com <

Re: [PD] [PD-announce] Pd 0.46-2 released

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Le 28/10/2014 17:06, Miller Puckette a écrit : > This is fixed in git, I hope, > > But my advice is not to use the autotools unless you have to. I'll > try to keep them working but have no idea what I'm doing with them > and personally use the simple

Re: [PD] [PD-announce] Pd 0.46-2 released

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Le 28/10/2014 16:57, Dan Wilcox a écrit : > Err, I spoke too soon. I see a commit that fixed this exact issue. > I bet you just need to clean all the automake stuff and rebuild the > makefiles, assuming you built 0.46.1 and then updated and didn’t > re

Re: [PD] [PD-announce] Pd 0.46-2 released

This is fixed in git, I hope, But my advice is not to use the autotools unless you have to. I'll try to keep them working but have no idea what I'm doing with them and personally use the simple makefiles. cheers Miller On Tue, Oct 28, 2014 at 11:53:01AM -0400, Dan Wilcox wrote: > From reading t

Re: [PD] [PD-announce] Pd 0.46-2 released

Err, I spoke too soon. I see a commit that fixed this exact issue. I bet you just need to clean all the automake stuff and rebuild the makefiles, assuming you built 0.46.1 and then updated and didn’t regenerate the makefiles when building 0.46.2. Try: make dist clean ./autogen ./configure make

Re: [PD] [oscparse] parsing address patterns with integers differently

In pd_typedmess of m_class.c, the float handler will currently throw an error if the arg isn't a float atom. However, this could be changed so that if the arg is a symbol-atom Pd sends it through a binbuf "carwash" to check if it comes out as a float. If so, it could send it on its way. If no

Re: [PD] [PD-announce] Pd 0.46-2 released

From reading the error, it’s obvious the Makefile.am was broken when “metro.pd" was renamed to "metro-help.pd”. Automake goes through and generates Makefiles based on the Makefile.am files found through out the project. You probably only need to find the Makefile.am for puredata/extra and change

[PD] svn and git question

Hi list, I am trying to understand the relation between different ways of getting the Pd sources via svn and git.

Re: [PD] [PD-announce] Pd 0.46-2 released

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Here, on Ubuntu 14.10 : $ apt-cache show puredata ... Version: 0.45.5-1 ... ++ Jack Le 28/10/2014 14:22, IOhannes zmölnig a écrit : > > > Am 28. Oktober 2014 11:06:03 MEZ, schrieb Jack : >> -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 >> >> It

Re: [PD] [PD-announce] Pd 0.46-2 released

Am 28. Oktober 2014 11:06:03 MEZ, schrieb Jack : >-BEGIN PGP SIGNED MESSAGE- >Hash: SHA1 > >It is OK with : >$ cd src/ >$ make -f makefile.gnu > >But is there a reason why it does not work with ? : >$ ./autogen.sh >$ ./configure >$ make > Because there is a bug. It has been fixed in git b

Re: [PD] [oscparse] parsing address patterns with integers differently

On Tue, 2014-10-28 at 09:21 +0100, Frank Barknecht wrote: > Hi Chris, > > I think, for the way back some external based on atoi(3) or atof(3) is needed. > I'm pretty sure someone has made one already. The "0" in the printed "symbol > 0" > is a real symbol atom itself, just like the word "zero" wo

Re: [PD] [PD-announce] Pd 0.46-2 released

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 It is OK with : $ cd src/ $ make -f makefile.gnu But is there a reason why it does not work with ? : $ ./autogen.sh $ ./configure $ make ++ Jack Le 28/10/2014 10:52, Jack a écrit : > Hello, > > I used to use : $ ./autogen.sh $ ./configure $ make

Re: [PD] [PD-announce] Pd 0.46-2 released

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello, I used to use : $ ./autogen.sh $ ./configure $ make to compile Pd. But I have a problem with the pd 0.46-2 : make[3]: Leaving directory '/home/jack/Téléchargements/pd-0.46-2/extra/stdout' make[3]: Entering directory '/home/jack/Téléchargements

Re: [PD] [oscparse] parsing address patterns with integers differently

Hi Chris, I think, for the way back some external based on atoi(3) or atof(3) is needed. I'm pretty sure someone has made one already. The "0" in the printed "symbol 0" is a real symbol atom itself, just like the word "zero" would. One could [select] it, but if you don't know what symbol-number yo