CAD Development : 8139


CAD / Development / 8139	8138 \| 8140

Subject:	Re: What's up with box3#8.dat? (was: BFC parts with BFC-less primitives)
Newsgroups:	lugnet.cad.dev
Date:	Fri, 10 Jan 2003 02:36:23 GMT
Viewed:	797 times

On Thu, Jan 09, 2003 at 10:42:07PM +0000, Jacob Sparre Andersen wrote: > The next level of problems is that the parts tracker is > implemented in Perl and running on a Unix system. Formally > any byte but zero can be used in a Unix file name (which > means that a line-break is an acceptable file name in Unix > ;-), but the Perl implementation might have some additional > limitations I'd have to look at the code again, but there's no reason why it couldn't deal with anything :) -- Dan Boger dan@peeron.com

Message has 2 Replies:

		Re: What's up with box3#8.dat? (was: BFC parts with BFC-less primitives)
(...) True, but it'd probably be better to restrict ourselves to a limited set of characters that are well-supported in file and path names on different OS's and protocols. But you already knew that, right? ;) Steve (22 years ago, 11-Jan-03, to lugnet.cad.dev)

		Re: What's up with box3#8.dat? (was: BFC parts with BFC-less primitives)
(...) In another branch of this thread it was my understanding that we had agreement on renaming box3#8p.dat to box3u8p.dat. Chris (22 years ago, 11-Jan-03, to lugnet.cad.dev)

Message is in Reply To:

		Re: What's up with box3#8.dat? (was: BFC parts with BFC-less primitives)
(...) HTML can handle anything. So can HTTP, but of the characters listed above, I think it is only '-' and '_' which don't need special treatment. The next level of problems is that the parts tracker is implemented in Perl and running on a Unix (...) (22 years ago, 9-Jan-03, to lugnet.cad.dev)

27 Messages in This Thread:

Entire Thread on One Page:: Nested: All | Brief | Compact | Dots
Linear: All | Brief | Compact
This Message and its Replies on One Page:: Nested: All | Brief | Compact | Dots
Linear: All | Brief | Compact

Custom Search