Re:V Language Review
by vlang1dot0 on Monday June 20, 2022 @06:33PM
(#31817058)
Did you even bother to read what he pasted? Tcc is used in the first set of commands that do not terminate.
Re:V Language Review
by ylluminate on Monday June 20, 2022 @08:01PM
(#31817925)
He is in fact reading it, please look again at what he pasted. It really seems somehow you're getting your wires crossed.
Re:V Language Review
by lifthrasiir on Monday June 20, 2022 @08:17PM
(#31818062)
No he didn't understand at all. Both the OP and I'm saying that while `make` claims that tcc was not used, the compiler does seem to use tcc even in that case. I have demonstrated that this is a plausible explanation by moving the tcc binary and showing the stark performance difference.
(This is my final response on this matter. I have already given enough information and an inability to interpret it is not my business.)
Re:V Language Review
by amedvednikov on Monday June 20, 2022 @08:55PM
(#31818390)
I admit I misread, and you do indeed use TCC.
I've just tested it, and turns out all C compilers are terrible at hundreds of thousands of print calls (for me Clang was stuck for minutes with 100% cpu usage).
The claim was made about actual code, like the V compiler itself, which is about 220k loc and compiles in 0.3 seconds, not some unrealistic test with a million of prints.
I'll make it clear on the home page with a link to the benchmark.
Re:V Language Review
by ylluminate on Monday June 20, 2022 @09:08PM
(#31818509)
Understandable to misread - I, funnily, did as well as I was quickly going down through the original comment + replies.
[dead]
Re:V Language Review
by ylluminate on Wednesday June 22, 2022 @06:44PM
(#31842836)
Human decency is a foreign concept to a lot of folks, eh?
I think it's pretty clear.
Anyway, now that we are clear on the compilation speed claim, can you please list a couple of those extraordinary claims?