X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?a=blobdiff_plain;f=pod%2Fperltodo.pod;h=30f17b04cbc8ad30d90482654ac035b0deed2e84;hb=98af1e142028dcf116f32636ea54f4c3e9494651;hp=f99c4ae5657e2f363bdfb816752ed7691e3a0001;hpb=162f8c6795b94ac69ddd84e3f510dab96b20003f;p=p5sagit%2Fp5-mst-13.2.git diff --git a/pod/perltodo.pod b/pod/perltodo.pod index f99c4ae..30f17b0 100644 --- a/pod/perltodo.pod +++ b/pod/perltodo.pod @@ -36,9 +36,11 @@ Since then the Perl 6 target moved, but the Perl 5 implementation did not. So it would be useful for someone to compare the Perl 6 smartmatch table as of February 2006 L and the current table L -and tabulate the differences in Perl 6. The diff is +and tabulate the differences in Perl 6. The annotated view of changes is +L and the diff is C --- search for C<=head1 Smart matching> +-- search for C<=head1 Smart matching>. (In theory F can generate that, +but in practice when I tried it hung forever, I assume "thinking") With that done and published, someone (else) can then map any changed Perl 6 semantics back to Perl 5, based on how the existing semantics map to Perl 5: @@ -398,29 +400,31 @@ the hint file setting. =back -There is an implicit historical assumption, probably from Perl 1, that C<$cc> -is also the correct command for linking object files together to make an -executable. This may be true on Unix, but it's not true on other platforms, -and there are a maze of work arounds in other places (such as F) -to cope with this. +There is an implicit historical assumption from around Perl5.000alpha +something, that C<$cc> is also the correct command for linking object files +together to make an executable. This may be true on Unix, but it's not true +on other platforms, and there are a maze of work arounds in other places (such +as F) to cope with this. Ideally, we should create a new variable to hold the name of the executable linker program, probe for it in F, and centralise all the special case logic there or in hints files. A small bikeshed issue remains - what to call it, given that C<$ld> is already -taken (arguably for the wrong thing) and C<$link> could be confused with the -Unix command line executable of the same name, which does something completely -different. Andy Dougherty makes the counter argument "In parrot, I tried to -call the command used to link object files and libraries into an executable -F, since that's what my vaguely-remembered DOS and VMS experience -suggested. I don't think any real confusion has ensued, so it's probably a -reasonable name for perl5 to use." +taken (arguably for the wrong thing now, but on SunOS 4.1 it is the command +for creating dynamically-loadable modules) and C<$link> could be confused with +the Unix command line executable of the same name, which does something +completely different. Andy Dougherty makes the counter argument "In parrot, I +tried to call the command used to link object files and libraries into an +executable F, since that's what my vaguely-remembered DOS and VMS +experience suggested. I don't think any real confusion has ensued, so it's +probably a reasonable name for perl5 to use." "Alas, I've always worried that introducing it would make things worse, since now the module building utilities would have to look for C<$Config{link}> and institute a fall-back plan if it weren't found." - +Although I can see that as confusing, given that C<$Config{d_link}> is true +when (hard) links are available. =head1 Tasks that need a little C knowledge