macports_version

2018-05-20 Thread Ryan Schmidt
Why is macports_version a proc and not an option?

Re: macports_version

2018-05-20 Thread Andrew Moore
On May 20, 2018, at 8:23 AM, Ryan Schmidt wrote: > > Why is macports_version a proc and not an option? To make it read-only? It seems procs and trace are Tcl’s way of defining constants <http://wiki.tcl.tk/1734>. -AM

Re: macports_version

2018-05-20 Thread Ryan Schmidt
On May 20, 2018, at 17:04, Andrew Moore wrote: > On May 20, 2018, at 8:23 AM, Ryan Schmidt wrote: > >> Why is macports_version a proc and not an option? > > To make it read-only? It seems procs and trace are Tcl’s way of defining > constants. Variables can be easi

Re: macports_version

2018-05-21 Thread Andrew Moore
> On May 20, 2018, at 9:45 PM, Ryan Schmidt wrote: > > > On May 20, 2018, at 17:04, Andrew Moore wrote: > >> On May 20, 2018, at 8:23 AM, Ryan Schmidt wrote: >> >>> Why is macports_version a proc and not an option? >> >> To make it read-

Re: macports_version

2018-05-21 Thread Ryan Schmidt
On May 21, 2018, at 04:28, Andrew Moore wrote: > On May 20, 2018, at 9:45 PM, Ryan Schmidt wrote: > >> On May 20, 2018, at 17:04, Andrew Moore wrote: >> >>> On May 20, 2018, at 8:23 AM, Ryan Schmidt wrote: >>> >>>> Why is macports_version a proc

Re: macports_version

2018-05-21 Thread Andrew Moore
On May 21, 2018, at 5:32 AM, Ryan Schmidt wrote: > > Yes I'm talking about $xcodeversion, and I'm wondering why we don't have a > corresponding $macports_version. Why do we have to call a procedure to get > the MacPorts version, when we don't have to c

Re: macports_version

2018-05-22 Thread Ryan Schmidt
On May 22, 2018, at 00:45, Andrew Moore wrote: > On May 21, 2018, at 5:32 AM, Ryan Schmidt wrote: > >> Yes I'm talking about $xcodeversion, and I'm wondering why we don't have a >> corresponding $macports_version. Why do we have to call a procedure to get

Re: macports_version

2018-05-22 Thread Clemens Lang
Hi, - On 22 May, 2018, at 09:04, Ryan Schmidt ryandes...@macports.org wrote: >> The cleanest way of defining a global const variable that I’ve come across is >> with trace, tying the variable to a write command with an explicit error >> message. >> >> But the Tcl wiki page that I linked to p

Re: macports_version

2018-05-22 Thread Ryan Schmidt
proc > doesn't. It's about runtime vs. compile time failure if you're trying to do > something > unsupported. > > IMHO, using a proc for read-only variables is much cleaner than using a write > trace, > which feels like a hack to me. > > Why would you need it to be a variable? Could you not just call the proc > instead? I'm confused by the inconsistency between variables like macosx_version and xcodeversion, and the macports_version proc.

Re: macports_version

2018-05-22 Thread Clemens Lang
Hi, - On 22 May, 2018, at 13:12, Ryan Schmidt ryandes...@macports.org wrote: > I'm confused by the inconsistency between variables like macosx_version and > xcodeversion, and the macports_version proc. xcodeversion and macosx_version are handled very different in the code. x

Re: macports_version

2018-05-22 Thread Ryan Schmidt
On May 22, 2018, at 06:22, Clemens Lang wrote: > On 22 May, 2018, at 13:12, Ryan Schmidt wrote: > >> I'm confused by the inconsistency between variables like macosx_version and >> xcodeversion, and the macports_version proc. > > xcodeversion and macosx_version are