> Anyway, this has always been the case on the Sam and other sensible systems. > I often call bits of code "*.bin" even though I don't have to.
But the SAM is stil insensible enough to differ between the filetypes BASIC, CODE, SCREEN, OPENTYPE, etc. > What the filetype bit of the name is actually for is to give a hint as to > what's in the file. If it's called abc.jpg then it's likely to be a JPEG > picture, although it would still work if it were called zyx.bas. Some > filetypes contain more hints than others. For example, if you want to > compile a C program you should call it foo.c or else the compiler won't > know it is a C program. Anyway that's enough random waffle... But you can call a BASIC-program "foo.c" if you want to - the ".c" does not have anything to do with the filetype. The filetype is determined from the first byte of the directory-entry. The postfix should not be important for the operating system - an excelent example of the oposite is MessDos.... -Frode
