You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The reason for keeping it all in one file is consistency, i.e. it generally prevents running a version of the script and then using another version of the header file. The only reason I could think of for not keeping it in one file is probably header file size.
Header size is the main reason, avoiding the craziness is another one. The ironic thing is that the script already supports editing itself to cut out the script and documentation portions (ppport.h --strip), only leaving the header portions. However, this is only part of the script, not of the module that creates the script/header/documentation. This means you can't easily use it for dzil purposes for example.
Is there any reason to keep ppport.h as both a Perl script and a C header file?
Is there any reason not to?
leont has requested that we separate them.
The text was updated successfully, but these errors were encountered: