I'm not sure if I understood your question correctly, but compiling a version
of tcc that hasn't replaced '--' with '-run' seems to be a bit of a nuisance -
it does not support the x86_64 architecture.
I don't think that there are very many people stuck on i386 nowadays, plus I
can't see how a c
On 18.04.2023 07:41, certanan via Tinycc-devel wrote:
I couldn't find any specific reasons as to why '--' was replaced by '-run'
(other than '-run' being implicitly more coherent than '--'). Since there is a
possibility that older scripts still depend on '--', would it be a bad idea to
re-impl
I couldn't find any specific reasons as to why '--' was replaced by '-run'
(other than '-run' being implicitly more coherent than '--'). Since there is a
possibility that older scripts still depend on '--', would it be a bad idea to
re-implement it for the sake of backward compatibility, and sta
Hi all.
Honestly ? When I read "-- option to tcc", I laughed at lot !
I consider this particularly irrelevant, and Grishka's comment is right
("For example, not to support compilation of files such as -c.c is not a
problem as long as we assume that such files do not exist.")
Considering other
On 17.04.2023 07:59, avih via Tinycc-devel wrote:
What some random script tries or doesn't try to do is irrelevant.
In a case however where the script and the tcc to be used with it
were written by the same author at the same time, we probably better
assume that it actually did work.
As it se
What some random script tries or doesn't try to do is irrelevant.
tcc should follow the spec and common practices.
Generally speaking, applications which respect the POSIX syntax
guidelines should treat non-option-argument "--" as an indication
that all further arguments are operands:
- https://
I understand. But then what role does the flag fulfil in this script?
https://github.com/qemacs/qemacs/blob/master/qe.tcc
- certanan
> I tried: gcc -- a.c
> and got:
> gcc: error: unrecognized command-line option '--'
>
> This is with prerelease of gcc 13.
> So gcc does not support this. Why wou
On 4/16/23 20:10, certanan wrote:
>From experience, when a program invoked by a shell sees the '--' flag, it
stops looking for options.
$ grep -V// print grep version
grep (GNU grep) 3.8
...
$ grep -- -V // match for '-V'
[waiting for stdin where matching for '-V' will occu
From experience, when a program invoked by a shell sees the '--' flag, it stops
looking for options.
$ grep -V// print grep version
grep (GNU grep) 3.8
...
$ grep -- -V // match for '-V'
[waiting for stdin where matching for '-V' will occur]
If I'm not mistaken, tcc expects
On 15.04.2023 22:38, certanan via Tinycc-devel wrote:
From what it seems to me, even Bellard's QEmacs seems to be relying on this,
rather, standard feature since at least 19 years ago, as referenced in its
official GitHub repository.
Am I missing something cardinal, or is there, indeed, no val
From what it seems to me, even Bellard's QEmacs seems to be relying on this,
rather, standard feature since at least 19 years ago, as referenced in its
official GitHub repository.
Am I missing something cardinal, or is there, indeed, no valid reason for this
seemingly not being implemented in tc
11 matches
Mail list logo
