Hello David! > This fork will eventually see lots of testing via the CPAN Testers when I > include it in a Perl > module. That's planned to happen this summer. Please inform us.
>> I pushed to the mob your changes to the win32/inlcude/winapi > Those changes were the minimum necessary so that tcc could compile perl.h on > Windows. Is that a sensible criterion for including them in tcc's source code? I think yes. All what extends usage case of the tcc on Windows is a sensible criterion. Btw, a nimrod developers consider a tcc as backed for REPL on Windows. > I do not believe that the exsymtab fork, in its current state, should be > brought into the mob > branch. I am more than happy to have help, but let's wait a few more months > until most of > these issues have been ironed out and we all have had a chance to discuss the > merits > and drawbacks of extended symbol table support. All changes are protected by a CONFIG_TCC_EXSYMTAB. This is done to keep tcc clean when "./configure --enable-exsymtab" is not used. I will test this behaviour more. Keeping somewhere this patch will allow not to introduce a changes which make porting much harder. I will try to follow your work and keep a patch in sync with the current mob. > We need to have a wider discussion about the merits of the extension before > we include it in mob Yes, I agree. PS: there are some error messages in exsymtab tests output which I don't see in the original branch (as some function defined twice) _______________________________________________ Tinycc-devel mailing list [email protected] https://lists.nongnu.org/mailman/listinfo/tinycc-devel
