On Feb 18, 2013, at 23:27, Lawrence Velázquez wrote:
> On Feb 18, 2013, at 8:02 PM, Lawrence Velázquez wrote:
>
>> I don't think return is behaving like you (or I) expect.
>
> The following is somewhat academic, but some might find it instructive. And
> it will almost certainly make Jeremy h
On Feb 18, 2013, at 8:02 PM, Lawrence Velázquez wrote:
> I don't think return is behaving like you (or I) expect.
The following is somewhat academic, but some might find it instructive. And it
will almost certainly make Jeremy hate Tcl more than he already does.
The Tcl "return" command[1] tak
On Feb 18, 2013, at 7:28 PM, Jeremy Huddleston Sequoia
wrote:
> You'll get:
>
> ~/src/macports/dports/x11/xwininfo $ port lint
> Can't map the URL 'file://.' to a port description file ("can't use empty
> string as operand of "!"").
> Please verify that the directory and portfile syntax are co
On Feb 18, 2013, at 16:19, Jeremy Huddleston Sequoia
wrote:
>
> On Feb 15, 2013, at 14:11, Ryan Schmidt wrote:
>
>> I haven't actually tested this code but I'm sure a language like Tcl must
>> support such a construct. But if you want to commit it as you sent it (but
>> with Rainer's chang
On Feb 15, 2013, at 14:11, Ryan Schmidt wrote:
> I haven't actually tested this code but I'm sure a language like Tcl must
> support such a construct. But if you want to commit it as you sent it (but
> with Rainer's change) we can always refine it later.
I beat my head against the keyboard tr
On Feb 15, 2013, at 3:10 AM, Jeremy Huddleston Sequoia
wrote:
> I'd like to update base trunk such that future versions of clang, dragonegg,
> and gcc "just work", so we don't need to wait for newer versions of base to
> depend on newer compilers.
>
> I've taken a first pass at portconfigure.
On Feb 15, 2013, at 16:30, Lawrence Velázquez wrote:
> On Feb 15, 2013, at 5:11 PM, Ryan Schmidt wrote:
>
>>> +if {[string first "macports-gcc" $compiler] == 0 ||
>>> +[string first "dragonegg-" $compiler] == 0} {
>>> +return no
>>> +} else {
>>> +return yes
>>>
On Feb 15, 2013, at 5:11 PM, Ryan Schmidt wrote:
>> +if {[string first "macports-gcc" $compiler] == 0 ||
>> +[string first "dragonegg-" $compiler] == 0} {
>> +return no
>> +} else {
>> +return yes
>> }
>
> Can't this be:
>
>return [string first "macports-
On Feb 15, 2013, at 02:10, Jeremy Huddleston Sequoia wrote:
> I'd like to update base trunk such that future versions of clang, dragonegg,
> and gcc "just work", so we don't need to wait for newer versions of base to
> depend on newer compilers.
That's a great idea! Thanks.
> I've taken a fi
On Feb 15, 2013, at 1:06 PM, Sean Farley wrote:
>
> Jeremy Huddleston Sequoia writes:
>
>> On Feb 15, 2013, at 12:18 PM, Sean Farley wrote:
>>
>>>
>>> Rainer Müller writes:
>>>
On 2013-02-15 09:10, Jeremy Huddleston Sequoia wrote:
> I'd like to update base trunk such that future v
On Feb 15, 2013, at 4:10 AM, Jeremy Huddleston Sequoia
wrote:
> That is the entire point of this patch. macports-gcc-3.14 is perfectly valid
> and should result in a dependency on gcc314. Of course the developer would
> then see a lint error about an unknown port just like they would see if
Jeremy Huddleston Sequoia writes:
> On Feb 15, 2013, at 12:18 PM, Sean Farley wrote:
>
>>
>> Rainer Müller writes:
>>
>>> On 2013-02-15 09:10, Jeremy Huddleston Sequoia wrote:
I'd like to update base trunk such that future versions of clang,
dragonegg, and gcc "just work", so we don
On 2013-02-15 21:18, Sean Farley wrote:
>
> Rainer Müller writes:
>> This change makes sense as the features supported by the gcc and clang
>> compilers shipped in ports are almost homogenous at the moment; in the
>> past there were differences as not all gcc4* shipped gfortran or gcj.
>> However,
On Feb 15, 2013, at 12:18 PM, Sean Farley wrote:
>
> Rainer Müller writes:
>
>> On 2013-02-15 09:10, Jeremy Huddleston Sequoia wrote:
>>> I'd like to update base trunk such that future versions of clang,
>>> dragonegg, and gcc "just work", so we don't need to wait for newer versions
>>> of b
Rainer Müller writes:
> On 2013-02-15 09:10, Jeremy Huddleston Sequoia wrote:
>> I'd like to update base trunk such that future versions of clang, dragonegg,
>> and gcc "just work", so we don't need to wait for newer versions of base to
>> depend on newer compilers.
>>
>> I've taken a first pa
On 2013-02-15 09:10, Jeremy Huddleston Sequoia wrote:
> I'd like to update base trunk such that future versions of clang, dragonegg,
> and gcc "just work", so we don't need to wait for newer versions of base to
> depend on newer compilers.
>
> I've taken a first pass at portconfigure.tcl and her
On Feb 15, 2013, at 12:51 AM, Lawrence Velázquez wrote:
> On Feb 15, 2013, at 3:10 AM, Jeremy Huddleston Sequoia
> wrote:
>
>> I'd like to update base trunk such that future versions of clang, dragonegg,
>> and gcc "just work", so we don't need to wait for newer versions of base to
>> depen
On Feb 15, 2013, at 3:10 AM, Jeremy Huddleston Sequoia
wrote:
> I'd like to update base trunk such that future versions of clang, dragonegg,
> and gcc "just work", so we don't need to wait for newer versions of base to
> depend on newer compilers.
>
> I've taken a first pass at portconfigure.
I'd like to update base trunk such that future versions of clang, dragonegg,
and gcc "just work", so we don't need to wait for newer versions of base to
depend on newer compilers.
I've taken a first pass at portconfigure.tcl and here is a patch. Comments?
Concerns?
future-compilers.patch
D
19 matches
Mail list logo
