[Gambas-user] Class to Read/Write INI files

Ron Onstenk ronstk at ...239...
Mon Jan 17 23:54:09 CET 2005


On Wednesday 12 January 2005 10:48, Benoit Minisini wrote:
| On Wednesday 12 January 2005 10:22, Frank Berg wrote:

--8<-----

| LINE INPUT reads the file until finding a newline character '\n' or the end of 
| file. The '\n' character is not returned.
| 
| On Unix systems, lines are delimited with '\n', not '\r\n' like on Windows 
| (what a stupid idea).
| 
| > and
| >
| > call_from = -
--8<-----
 Regards,
| 

That is not stupid at all.

It is historical, \n as _newline_ did go to a new line and the
character position was keep the same.
The \r as _return_ was the carriage return to be able to bold printing
by do it twice.

Printer options in the past, for example the FX80 from epson, 
has a option switch to add a _return_ after receiving a _linefeed_
because it was logical to have it in normal _1 go_ printing.

See a page as an pre printed order form with two columns
1 description field and cost and 1 price field per row.
Go to the second column, print the count and the price, send backspaces 
to go to the start of the 2' column and do linefeed for net price.

This way was more quick on the (very old now) printers in history
to get nice tabular pre printed order forms. :)
Now you must print spaces till you are at the 2' column 
what cost more characters than the backspaces.
Printing to file results also in smaller files.

It is more stupid the way _unix/linux_ does.
Maybe more user friendly now a days with some mistake behavior.

It is not the fault from printer manufacture, windows/linux/ user does 
print the whole form with the expensive inkjet and ink printers.
Pre printer sheets are still cheaper than printing your self :).

Back from tennerife with some salt :)

Ron

ps. job done but in april again for 4/6 weeks.






More information about the User mailing list