I use more or less always the f option to generate Flex command files.
Then these files are xmodem transferred to a real flex system with Minicom and Mike Douglas PCGET program.
Sometime loss of data occur due to the size of the Linux (or Windows) file of the Flex binary...
Is it possible to get a compilation option so that the output file is always a strict multiple of 252 bytes like it should be on a Flex file system ?
I think the filling char could be what we want.
Another point that can be improved on the command line is the inclusion of a space char between the option and the option value.
This can give for example "-f outfile.cmd "instead of "-foutfile.cmd" and thus leave the auto completion do his job...
Hello,
I use more or less always the f option to generate Flex command files. Then these files are xmodem transferred to a real flex system with Minicom and Mike Douglas PCGET program. Sometime loss of data occur due to the size of the Linux (or Windows) file of the Flex binary... Is it possible to get a compilation option so that the output file is always a strict multiple of 252 bytes like it should be on a Flex file system ? I think the filling char could be what we want.
Another point that can be improved on the command line is the inclusion of a space char between the option and the option value. This can give for example "-f outfile.cmd "instead of "-foutfile.cmd" and thus leave the auto completion do his job...
Anyway continue the good job !
Thanks and regards. Philippe