Re^4: CGI problem: USING THE FUNCTION-ORIENTED INTERFACE (patches)

Patches welcome.

Already submitted a patch to CGI.pm. Already had it rejected.

The suggestion is spelled out quite clearly above and is nearly trivial to implement. If the maintainers like the idea, then they can implement it about as easily as they can review a patch request (and implement exactly to their taste rather than look at a patch that doesn't quite fit their taste). If they don't like the idea, then a patch request would just be a waste of my time and theirs.

- tye

Comment on Re^4: CGI problem: USING THE FUNCTION-ORIENTED INTERFACE (patches)

Replies are listed 'Best First'.
Re^5: CGI problem: USING THE FUNCTION-ORIENTED INTERFACE (patches) by leej (Monk) on Nov 19, 2015 at 12:04 UTC
Already submitted a patch to CGI.pm. Already had it rejected. Can you point this out to me please and i shall look at it (possibly again if it was i who rejected it originally).	[reply]
Re^6: CGI problem: USING THE FUNCTION-ORIENTED INTERFACE (patches) by choroba (Cardinal) on Nov 19, 2015 at 13:16 UTC
RT-61396 or #76 on GitHub, maybe? ($q=q:Sq=~/;[c](.)(.)/;chr(-\|\|-\|5+lengthSq)`"S\|oS2"`map{chr \|+ord }map{substrSq`S_+\|`\|}3E\|-\|`7**2-3:)=~y+S\|`+$1,++print+eval$q,q,a, [download]	[reply] [d/l]
Re^7: CGI problem: USING THE FUNCTION-ORIENTED INTERFACE (patches) by leej (Monk) on Nov 19, 2015 at 13:24 UTC
Is this the same as we are discussing here, list context behaviour in the param functionality, because looking at those tickets they are related to HTML generation functionality and i'm afraid any changes to those are not being accepted (I also don't see a patch file attached to the RT ticket or in the body of the requests, so...)	[reply]