Lisandro Damián Nicanor Pérez Meyer:
> On miércoles, 15 de noviembre de 2017 20:35:00 -03 Ximin Luo wrote:
>> Lisandro Damián Nicanor Pérez Meyer:
>>> I was wanting to write this on a keyboard, but let me try on the phone and
>>> see if we can all agree in one point.
>>>
>>> There is one
On miércoles, 15 de noviembre de 2017 20:35:00 -03 Ximin Luo wrote:
> Lisandro Damián Nicanor Pérez Meyer:
> > I was wanting to write this on a keyboard, but let me try on the phone and
> > see if we can all agree in one point.
> >
> > There is one *excellent* method to settle this once and
El 15 nov. 2017 5:35 p.m., "Mattia Rizzolo" escribió:
On Wed, Nov 15, 2017 at 05:28:06PM -0300, Lisandro Damián Nicanor Pérez
Meyer wrote:
> There is one *excellent* method to settle this once and forever: submit
the
> __FILE__ patch to GCC devs. If it gets accepted then Qt
Lisandro Damián Nicanor Pérez Meyer:
> I was wanting to write this on a keyboard, but let me try on the phone and
> see if we can all agree in one point.
>
> There is one *excellent* method to settle this once and forever: submit the
> __FILE__ patch to GCC devs. If it gets accepted then Qt and
I was wanting to write this on a keyboard, but let me try on the phone and
see if we can all agree in one point.
There is one *excellent* method to settle this once and forever: submit the
__FILE__ patch to GCC devs. If it gets accepted then Qt and whatever
project is affected should change it.
In data mercoledì 15 novembre 2017 20:14:00 CET, Ximin Luo ha scritto:
> Pino Toscano:
> > Loose meanings do not imply neither the other way around, that you are
> > free to break because people cannot do anything with it. Also,
> > considering the very same behaviour (short of the different
In data mercoledì 15 novembre 2017 19:29:00 CET, Ximin Luo ha scritto:
> Pino Toscano:
> > [..]
> >
> >> In summary: in no document or standard, does it guarantee or imply
> >> that __FILE__ can be taken to represent a real filesystem path.
> >> Applications relying on this behaviour are broken
Pino Toscano:
> [..]
>
>> In summary: in no document or standard, does it guarantee or imply
>> that __FILE__ can be taken to represent a real filesystem path.
>> Applications relying on this behaviour are broken and should not be
>> upset when things don't work. As documented in multiple places,
In data mercoledì 15 novembre 2017 10:57:00 CET, Ximin Luo ha scritto:
> Pino Toscano:
> > In data martedì 14 novembre 2017 11:14:00 CET, Ximin Luo ha scritto:
> >> You're using __FILE__ inappropriately, none of the documentation
> >> guarantees or implies that you can access __FILE__ as a real
>
In data mercoledì 15 novembre 2017 12:09:00 CET, Ximin Luo ha scritto:
> Lisandro Damián Nicanor Pérez Meyer:
> > [..]
> >
> > Xi: you also mentioned that having to file hundreds of patchs seems
> > impossible. Well, it seems so, but it is actually not that necessary.
> > Please
> > allow me
El 15 nov. 2017 8:00 a.m., "Ximin Luo" escribió:
Pino Toscano:
> In data martedì 14 novembre 2017 11:14:00 CET, Ximin Luo ha scritto:
>> You're using __FILE__ inappropriately, none of the documentation
>> guarantees or implies that you can access __FILE__ as a real
>>
Lisandro Damián Nicanor Pérez Meyer:
> [..]
>
> Xi: you also mentioned that having to file hundreds of patchs seems
> impossible. Well, it seems so, but it is actually not that necessary. Please
> allow me to explain the idea.
>
Thanks for being less inflammatory than Pino.
I agree that
Pino Toscano:
> In data martedì 14 novembre 2017 11:14:00 CET, Ximin Luo ha scritto:
>> You're using __FILE__ inappropriately, none of the documentation
>> guarantees or implies that you can access __FILE__ as a real
>> filesystem path. "Surely for relative paths" is your justification
>> for your
13 matches
Mail list logo