git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Support for old Perl versions

From
Johannes Schindelin <johannes.schindelin@gmx.de>
Date
May 31, 2008, 12:32 UTC
Message-ID
<alpine.DEB.1.00.0805311328040.13507@racer.site.net>
In-Reply-To
<20080531121755.GL593@machine.or.cz>
Hi,
On Sat, 31 May 2008, Petr Baudis wrote:
Show 17 quoted lines
> On Sat, May 31, 2008 at 12:50:14PM +0100, Johannes Schindelin wrote:
> > On Fri, 30 May 2008, Lea Wiemann wrote:
> > 
> > > I'm honestly not too keen on sacrificing time (or code prettiness) 
> > > on 5.6 compatibility, so if there are no reasons besides the memory 
> > > leak to move away from throw/catch, perhaps we can just keep using 
> > > it?
> > 
> > I think your opinion would change dramatically if you were stuck on a 
> > platform with Perl 5.6.  In general, I deem it not nice to sacrifice 
> > backwards compatibility just because _you_ do not need it.
> 
>   let's get some perspective here: 5.6.1 was released on 2001-Apr-08. 
> 5.8.0 followed on 2002-Jul-18.  Is there anyone on the list who _is_ 
> stuck on a platform with Perl 5.6 _and_ uses Git on it? Heck, we are 
> even approaching GNU Interactive Tools 4.3.20 release here, walking that 
> much back.

I think this is not an interesting question. Those stuck with Perl 5.6 are most likely not those who lurk on this list.

Sure, we could just require users to upgrade to Linux, newest glibc and everything and be done. We could also require our users to stick their fingers where the sun don't shine.

The really interesting question is: is the time of a single developer (who gets all the upsides of requiring a certain setup) worth the hassle and pain of possibly more than one person getting all the _downsides_?

In the case that started this thread, I would not hesitate a single microsecond to answer "No, hell no".

Hth, Dscho

Previous: Petr BaudisNext: Petr Baudis
Message 21 of 32 in “perl/Git.pm: add rev_parse method”
  1. perl/Git.pm: add rev_parse methodLea Wiemann, May 30, 2008
  2. Lea WiemannMay 30, 2008
  3. Petr BaudisMay 30, 2008
  4. Merging strategy for extending Git.pm (was: [PATCH] perl/Git.pm: add rev_parse method)Lea Wiemann, May 30, 2008
  5. Junio C HamanoMay 30, 2008
  6. Johannes SchindelinMay 31, 2008
  7. Lea WiemannMay 31, 2008
  8. Johannes SchindelinMay 31, 2008
  9. Junio C HamanoMay 30, 2008
  10. Petr BaudisMay 30, 2008
  11. perl/Git.pm: add parse_rev methodLea Wiemann, May 30, 2008
  12. Petr BaudisMay 30, 2008
  13. Junio C HamanoMay 30, 2008
  14. Randal L. SchwartzMay 30, 2008
  15. Lea WiemannMay 30, 2008
  16. Randal L. SchwartzMay 30, 2008
  17. Lea WiemannMay 30, 2008
  18. Junio C HamanoMay 30, 2008
  19. Johannes SchindelinMay 31, 2008
  20. Support for old Perl versionsPetr Baudis, May 31, 2008
  21. Johannes SchindelinMay 31, 2008
  22. Petr BaudisMay 30, 2008
  23. perl/Git.pm: add parse_rev methodLea Wiemann, May 31, 2008
  24. perl/Git.pm: add parse_rev methodLea Wiemann, Jun 1, 2008
  25. perl/Git.pm: add parse_rev methodLea Wiemann, Jun 1, 2008
  26. Lea WiemannJun 1, 2008
  27. Miklos VajnaJun 1, 2008
  28. Lea WiemannJun 1, 2008
  29. Junio C HamanoJun 2, 2008
  30. Lea WiemannJun 2, 2008
  31. perl/Git.pm: add get_hash methodLea Wiemann, Jun 1, 2008
  32. perl/Git.pm: add get_hash methodLea Wiemann, Jun 1, 2008

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.