HI

I need that WRITELN make the same end of line in Linux and Win32,

I found sLineBreak, but for some OS it is var, for some const,

There is second identifier LineEnding (mostly const)

I think, tha one should be const, and second var, and when somebody need changes behavour of WRITELN that he can do it.

Darek

The purpose of this constant is not to be able to set the lineending, it gives the lineending which is the default on the current platform.

If you need to have the same lineending on all platforms, you must do your writes yourself. I would suggest using TStreams then.

Michael.

changes

> behavour of WRITELN that he can do it. The purpose of this constant is not to be able to set the lineending, it gives the lineending which is the default on the current platform.

I know, but why are two identifiers

If you need to have the same lineending on all platforms, you must do your writes yourself. I would suggest using TStreams then.

I can do it, but I have to change many lines of code (many thousand lines), thats trouble

One of the two is for Delphi compatibility.

If I remember correctly, LineEnding is the FPC constant. sLineBreak comes from Delphi/Kylix

I think that if your code expects the same linefeed on both platforms, you should rethink your strategy. You should always use the 'local' default. Opening a unix LF file in Windows gives strange results, and vice versa too...

Michael.

I dont agree:
I don't know on which OS file will be write or read, I have several places to generate and several to read files. And no user need to open this files myself without application.

And second I don't understand why You don't want change it. I don't see any true reason to left it unchanged. Everybody, who want to control output must avoid WRITELN (I don't test READLN, but I use it very rare). I want do decide, how function work, not OS.

Of course I can do it by hand, but I think that somebody help me (I must change more than 1000 places in my program)

Darek

On Wed, 15 Sep 2004 23:59:57 +0200, Darek Mazur wrote

If it's only your application working with these files, you are already on the safe side, because FPC supports all line endings on all supported platforms.

We will discuss this internally and let you know the result.

Tomas

I know.

Thx, that sounds good.

From: Darek Mazur
To:
Subject: Re: [fpc-devel]const sLineBreak
Send reply to:

Date sent: Thu, 16 Sep 2004 16:52:54 +0200

.
.

A new procedure SetTextLineEnding (var T: text; S: string) was added to System unit in CVS. This allows you to change line ending for individual text files. After call to Assign the line ending for that file is set to the default line ending on your platform, then you can change the default value using the newly provided procedure - since that time all WriteLn calls will use your new value. Changing the default value system-wide would be dangerous because of output to console, redirection, libraries possibly expecting particular behaviour etc.

Tomas

This is not really necessary. If you rewrite or append the file it has the System.LineEnding as line ending. You are the one who changes it with SetTextLineEnding and if you have done it, you know what you changed it to. If you haven't called SetTextLineEnding, it is still the default: System.LineEnding.

Regards,
Vincent.

On Wed, 22 Sep 2004 11:51:06 +0200, Darek Mazur wrote

Użytkownik Tomas Hajny napisał: > From: Darek Mazur > Date sent: Thu, 16 Sep 2004 16:52:54 +0200

.
.

Such a function can be added, of course, but keep in mind that it will only return the value you assigned to it yourself (as already mentioned by Vincent). Don't expect that it would be able to determine the used line ending type in existing files while reading them - this is not possible (among other reasons, you are never guaranteed to have uniform line endings throughout the whole existing file).

Tomas

Darek Mazur wrote

Is SetTextLineEnding applied to readln (I can test it)

readln has always supported all possible line break formats (Dos/Windows, Unix and Mac).

Jonas

That is better solution, than I think .

But is function like
GetTextLineEnding(vat T: text): string

I don check CVS yet

Darek

On Wed, 22 Sep 2004 13:32:27 +0200, Darek Mazur wrote

.
.

>>But is function like >> GetTextLineEnding(vat T: text): string

.
.

Why do you think this function is needed (sample scenario)?

Tomas

Of course, I don't expect test of format of file. I think, this function is need when pass T:text to other function

My ask:
Is SetTextLineEnding applied to readln (I can test it)

Darek

Darek Mazur wrote

I can't now give an exact program, but this kind of function don't make any disorder or other bad things.

The main problem is that people may expect it to return the line-endings of the text file, instead of just what you set it to be. As such, it can cause confusion. Just like some properties of an object can be read-only, some can be write-only as well. I also can't think of any situation where you would want to write something different to the file based on the set line endings.

Jonas

I only imagine (sorry for my english), when I set something that sometimes I must read what I set. For me T: text is like object, which I pass to function, this function maybe need to know, how Lineending is set (I think about special or internal function). Its not correct pass to this function LineEnding separately. I think that every kind of information about T:text should be set and get through function/procedures not direct from fields of record.

I can't now give an exact program, but this kind of function don't make any disorder or other bad things.

Darek

Uz.ytkownik Jonas Maebe napisa?:

This is for developer, not for users ?
When I found new function, I test it and read manual. In whole FPC is many similar names of different function and nobody should think about function only from its name. Of course better is, when names are full of knowledge (I don't know how it say), but it can't be a barrier of development.

My idea: change name (settextlineending too) or make second function GetFileLineEnding to return line-endings of file.

As such, it can