Actually, that's not a bad idea at the expense of a little more searching. [declare] then behaves more like the lua loader which searches for both binary and script modules, which I find relatively easy to use. I don't think this would break existing patches and would also honor the relative path restrictions for self contained projects, where specifying a relative path starting with ./ or ../ only searches locally.
On Sep 11, 2018, at 12:00 PM, pd-dev-request@lists.iem.at wrote:
Date: Tue, 11 Sep 2018 11:42:00 +0200 From: Antoine Rousseau <antoine@metalu.net mailto:antoine@metalu.net> To: pd-dev <pd-dev@lists.iem.at mailto:pd-dev@lists.iem.at> Subject: Re: [PD-dev] declare (again) Message-ID: <CAOCG5Hx19cSDb5GkJ2onAtY8OU_XaQOZs28qXGn=8JZSi1ELKw@mail.gmail.com mailto:CAOCG5Hx19cSDb5GkJ2onAtY8OU_XaQOZs28qXGn=8JZSi1ELKw@mail.gmail.com> Content-Type: text/plain; charset="utf-8"
relatively easy code change
... so I propose step 2 as PR #440 !
cheers
-------- Dan Wilcox @danomatika http://twitter.com/danomatika danomatika.com http://danomatika.com/ robotcowboy.com http://robotcowboy.com/
+1 You only understand how non-intuitive current [declare] is once you've attempted to describe it simply to a roomful of learners. Not saying current situation isn't a huge improvement over where we were umpteen years ago but if there's the option to make it even simpler & more straightforward plus portable - yes please.
J.
On Tue, 11 Sep 2018 at 11:42, Dan Wilcox danomatika@gmail.com wrote:
Actually, that's not a bad idea at the expense of a little more searching. [declare] then behaves more like the lua loader which searches for both binary and script modules, which I find relatively easy to use. I don't think this would break existing patches and would also honor the relative path restrictions for self contained projects, where specifying a relative path starting with ./ or ../ only searches locally.
On Sep 11, 2018, at 12:00 PM, pd-dev-request@lists.iem.at wrote:
Date: Tue, 11 Sep 2018 11:42:00 +0200 From: Antoine Rousseau antoine@metalu.net To: pd-dev pd-dev@lists.iem.at Subject: Re: [PD-dev] declare (again) Message-ID: CAOCG5Hx19cSDb5GkJ2onAtY8OU_XaQOZs28qXGn=8JZSi1ELKw@mail.gmail.com Content-Type: text/plain; charset="utf-8"
relatively easy code change
... so I propose step 2 as PR #440 !
cheers
Dan Wilcox @danomatika http://twitter.com/danomatika danomatika.com robotcowboy.com
Pd-dev mailing list Pd-dev@lists.iem.at https://lists.puredata.info/listinfo/pd-dev
Yeah. I find "you need to tell PD where to look" make sense, but adding "and HOW it needs to look" becomes the issue.
On Sep 11, 2018, at 1:02 PM, Julian Brooks jbeezez@gmail.com wrote:
+1 You only understand how non-intuitive current [declare] is once you've attempted to describe it simply to a roomful of learners. Not saying current situation isn't a huge improvement over where we were umpteen years ago but if there's the option to make it even simpler & more straightforward plus portable - yes please.
J.
On Tue, 11 Sep 2018 at 11:42, Dan Wilcox <danomatika@gmail.com mailto:danomatika@gmail.com> wrote: Actually, that's not a bad idea at the expense of a little more searching. [declare] then behaves more like the lua loader which searches for both binary and script modules, which I find relatively easy to use. I don't think this would break existing patches and would also honor the relative path restrictions for self contained projects, where specifying a relative path starting with ./ or ../ only searches locally.
On Sep 11, 2018, at 12:00 PM, pd-dev-request@lists.iem.at mailto:pd-dev-request@lists.iem.at wrote:
Date: Tue, 11 Sep 2018 11:42:00 +0200 From: Antoine Rousseau <antoine@metalu.net mailto:antoine@metalu.net> To: pd-dev <pd-dev@lists.iem.at mailto:pd-dev@lists.iem.at> Subject: Re: [PD-dev] declare (again) Message-ID: <CAOCG5Hx19cSDb5GkJ2onAtY8OU_XaQOZs28qXGn=8JZSi1ELKw@mail.gmail.com mailto:CAOCG5Hx19cSDb5GkJ2onAtY8OU_XaQOZs28qXGn=8JZSi1ELKw@mail.gmail.com> Content-Type: text/plain; charset="utf-8"
relatively easy code change
... so I propose step 2 as PR #440 !
cheers
-------- Dan Wilcox @danomatika http://twitter.com/danomatika danomatika.com http://danomatika.com/ robotcowboy.com http://robotcowboy.com/
Also, I like that this simple, yet elegant approach does not need to remove or override the explicit -path or -lib flags at all. I'm not sure why we didn't think of it when I wrote the initial PR a year ago.
On Sep 11, 2018, at 1:04 PM, Dan Wilcox danomatika@gmail.com wrote:
Yeah. I find "you need to tell PD where to look" make sense, but adding "and HOW it needs to look" becomes the issue.
On Sep 11, 2018, at 1:02 PM, Julian Brooks <jbeezez@gmail.com mailto:jbeezez@gmail.com> wrote:
+1 You only understand how non-intuitive current [declare] is once you've attempted to describe it simply to a roomful of learners. Not saying current situation isn't a huge improvement over where we were umpteen years ago but if there's the option to make it even simpler & more straightforward plus portable - yes please.
J.
On Tue, 11 Sep 2018 at 11:42, Dan Wilcox <danomatika@gmail.com mailto:danomatika@gmail.com> wrote: Actually, that's not a bad idea at the expense of a little more searching. [declare] then behaves more like the lua loader which searches for both binary and script modules, which I find relatively easy to use. I don't think this would break existing patches and would also honor the relative path restrictions for self contained projects, where specifying a relative path starting with ./ or ../ only searches locally.
On Sep 11, 2018, at 12:00 PM, pd-dev-request@lists.iem.at mailto:pd-dev-request@lists.iem.at wrote:
Date: Tue, 11 Sep 2018 11:42:00 +0200 From: Antoine Rousseau <antoine@metalu.net mailto:antoine@metalu.net> To: pd-dev <pd-dev@lists.iem.at mailto:pd-dev@lists.iem.at> Subject: Re: [PD-dev] declare (again) Message-ID: <CAOCG5Hx19cSDb5GkJ2onAtY8OU_XaQOZs28qXGn=8JZSi1ELKw@mail.gmail.com mailto:CAOCG5Hx19cSDb5GkJ2onAtY8OU_XaQOZs28qXGn=8JZSi1ELKw@mail.gmail.com> Content-Type: text/plain; charset="utf-8"
relatively easy code change
... so I propose step 2 as PR #440 !
cheers
-------- Dan Wilcox @danomatika http://twitter.com/danomatika danomatika.com http://danomatika.com/ robotcowboy.com http://robotcowboy.com/
Thanks! I think we needed to realize fully the implications of the recent changes, before imagining that it could be even simpler...
Antoine Rousseau http://www.metalu.net http://metalu.net __ http://www.metaluachahuter.com/ http://www.metaluachahuter.com/compagnies/al1-ant1/
Le mar. 11 sept. 2018 à 13:07, Dan Wilcox danomatika@gmail.com a écrit :
Also, I like that this simple, yet elegant approach does not need to remove or override the explicit -path or -lib flags at all. I'm not sure why we didn't think of it when I wrote the initial PR a year ago.
On Sep 11, 2018, at 1:04 PM, Dan Wilcox danomatika@gmail.com wrote:
Yeah. I find "you need to tell PD where to look" make sense, but adding "and HOW it needs to look" becomes the issue.
On Sep 11, 2018, at 1:02 PM, Julian Brooks jbeezez@gmail.com wrote:
+1 You only understand how non-intuitive current [declare] is once you've attempted to describe it simply to a roomful of learners. Not saying current situation isn't a huge improvement over where we were umpteen years ago but if there's the option to make it even simpler & more straightforward plus portable - yes please.
J.
On Tue, 11 Sep 2018 at 11:42, Dan Wilcox danomatika@gmail.com wrote:
Actually, that's not a bad idea at the expense of a little more searching. [declare] then behaves more like the lua loader which searches for both binary and script modules, which I find relatively easy to use. I don't think this would break existing patches and would also honor the relative path restrictions for self contained projects, where specifying a relative path starting with ./ or ../ only searches locally.
On Sep 11, 2018, at 12:00 PM, pd-dev-request@lists.iem.at wrote:
Date: Tue, 11 Sep 2018 11:42:00 +0200 From: Antoine Rousseau antoine@metalu.net To: pd-dev pd-dev@lists.iem.at Subject: Re: [PD-dev] declare (again) Message-ID: CAOCG5Hx19cSDb5GkJ2onAtY8OU_XaQOZs28qXGn=8JZSi1ELKw@mail.gmail.com Content-Type: text/plain; charset="utf-8"
relatively easy code change
... so I propose step 2 as PR #440 !
cheers
Dan Wilcox @danomatika http://twitter.com/danomatika danomatika.com robotcowboy.com