Path: csiph.com!eternal-september.org!feeder.eternal-september.org!mx02.eternal-september.org!.POSTED!not-for-mail From: Paul Rubin Newsgroups: comp.lang.forth Subject: Re: File extensions and Gforth on Openhub Date: Tue, 29 Mar 2016 00:15:06 -0700 Organization: A noiseless patient Spider Lines: 9 Message-ID: <87zith4ux1.fsf@nightsong.com> References: <2016Mar26.091504@mips.complang.tuwien.ac.at> <2016Mar27.100129@mips.complang.tuwien.ac.at> <2016Mar27.161527@mips.complang.tuwien.ac.at> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: mx02.eternal-september.org; posting-host="ac130717aa033f117b1251f50cb4c61b"; logging-data="21925"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX18G5kybxNqpVCWdc+vfJ3OZ" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3 (gnu/linux) Cancel-Lock: sha1:fQUzFXIZKyGBQzPKs7hWCfQ5jI0= sha1:Xp8lP+Isn/7s2xsIwcSpJPKwRM8= Xref: csiph.com comp.lang.forth:46278 Gerry Jackson writes: > In my ignorance I don't understand this. Can you give an example of a > scenario in which Microsoft would sue someone for using .forth as an > extension. The issue is that traditional FAT filenames are limited to 3 character extensions. The workaround is VFAT, an overlay on FAT that is patented by Microsoft. FAT is used in many embedded systems. Using .forth would require people to also use VFAT and potentially get hassled over patents.