Well it is convenient to use Nero to drag files to a CD (provided they don't fill the CD - which means you have quite a lot of code). I have already actually fallen foul of the length restriction (several documentation files are the worst culprits) and you have to delete these files before you can copy the rest. A nuisance. I can imagine that portable 'embedded' systems may enforce length limits too. And you may not be able to email zips. I feel we are creating unnecessary problems for a few users by using 'unlimited' filename lengths. Paul Paul A Bristow Prizet Farmhouse, Kendal, Cumbria UK LA8 8AB +44 1539 561830 +44 7714 330204 mailto: pbristow@hetp.u-net.com | -----Original Message----- | From: boost-bounces@lists.boost.org | [mailto:boost-bounces@lists.boost.org] On Behalf Of John Torjo | Sent: 18 August 2004 19:45 | To: boost@lists.boost.org | Subject: Re: [boost] 31 character limit for filenames | | | > Okay, it's time to ask again: do we still need to enforce the | > 31-character limit on filenames? AFAIK, we have this for | MacOS 9, only. | > Is that platform still significant for Boost users? | > | | After reading the other posts, I sort of agree with 31 char limit. | But, when archiving/backing up to CD, I always use a .zip or | .tarball - | so this wouldn't affect me at all. | | Do people back up boost "raw" files? | | Best, | John