Front page | perl.perl5.porters |
Postings from December 2021
Lately I'm trying to make some edits on op.c, and finding that the file has become a giant sprawling monstrosity of way too much code in one file; 630k in size and 18k lines of C source code. I intend to split it into a few smaller pieces. My plan is to create two new .c files to contain subsections of what is currently in op.c: peep.c: to contain the finalizer and peephole optimiser ck.c: to contain the opchecker functions (Perl_ck_*) This will hopefully end up with a much smaller op.c that contains mostly just the lowlevel machinery of being an optree, with the other specialised parts of it moved to their own files. I bring this to people's attention mostly as a way to point out I intend to move it, and to see if anyone has any outstanding code on that file in branches. Depending on what or where that is, it might cause a merge conflict, so I'd like to see what we can do to minimise the impact of that. -- Paul "LeoNerd" Evans leonerd@leonerd.org.uk | https://metacpan.org/author/PEVANS http://www.leonerd.org.uk/ | https://www.tindie.com/stores/leonerd/Thread Next