In article <66605182$1@news.ausics.net>, dxf wrote:
>On 5/06/2024 8:17 pm, Anton Ertl wrote:
>> dxf writes:
>>> On 5/06/2024 2:11 am, Anton Ertl wrote:
>>>> albert@spenarnc.xs4all.nl writes:
>>>>> For Forth we've seen: .f .F .frt .FRT .fth .4th .fs
>>>>> Are there more?
>>>>>
>>>>> I'd like to see an official extension.
>>>>
>>>> At the 2015 Forth200x meeting we decided on ".4th", and that has been
>>>> added to the extensions that VFX knows about
>>>
>>> The question surely is whether VFX uses it. AFAICS it continues
>>> to use .fth for all its source files.
>>
>> [/usr/local/src/VfxForth64Lin-5.43:149811] find . -name \*.4th|wc -l
>> 4
>> [/usr/local/src/VfxForth64Lin-5.43:149812] find . -name \*.fth|wc -l
>> 275
>>
>> But no, that was not the question. The question was about an
>> "official" extension, and as far as the Forth200x committee is
>> concerned, .4th is the official extension. Of course that does not
>> mean that other extensions are forbidden. And actually the standard
>> document does not mention extensions at all.
>
>Well that makes it ok then. The Forth200x committee has nominated
>an "official extension" that's little more than a flag users can
>wave about when they feel like it.
It could be much more. If lina is the official Forth compiler installed
and you have hello.4th
you could say
make hello
That would be similar as having hello.c and saying
make hello
Delivering syntax coloring to editors could be the next step.
Groetjes Albert
>
--
Don't praise the day before the evening. One swallow doesn't make spring.
You must not say "hey" before you have crossed the bridge. Don't sell the
hide of the bear until you shot it. Better one bird in the hand than ten in
the air. First gain is a cat purring. - the Wise from Antrim -
--- SoupGate-Win32 v1.05
* Origin: you cannot sedate... all the things you hate (1:229/2)
|
