AW: Delphi´s .DFM files, store as ASCII or binary?

[Schell Walter]

Hi Stephan,
I don't know, if you can tell cvs, not to merge certain files (sure you
don't want to mark them as binary <g>).
But for me a merge always has some extra work: if I commit a 2nd change, I
get an error and have to do an update first. This update will merge the
changes and before I commit the resulting file, I check the foreign changes,
look at the form, compile the program etc. 

Another possibility is to use locks, but the users have to have
cvsadmin-permission and any user can break the locks  or  put watches on the
dfm-files and use "cvs edit" before start editing files.

Walter

-----Ursprüngliche Nachricht-----
Von: Stephan Petersen [mailto:address@hidden
Gesendet: Dienstag, 12. Juni 2001 09:05
An: address@hidden
Betreff: Delphi´s .DFM files, store as ASCII or binary?



Hi there,

I searched the archives for an answer to this question, but
couldn´t find a matching one...

Delphi offers you the choice of storing .DFM files (where the layout
of forms is stored) as ASCII or binary files.

While ASCII files are better for cvs, I´m wondering about the 
potential side effects in a multi-developer environment, 
i.e. what happens if two developers change the form and 
cvs is able to perform a non-conflicting merge.

Is there a chance that the .DFM file can be rendered unusable
by something like this?

Thanks in advance for any pointers!

Stephan


--
Stephan Petersen                           address@hidden

>-=-=-=- Visit GTT's Technical Thermochemistry Web Page at =-=-=-=-<
>-=-=-=-      http://gttserv.lth.rwth-aachen.de/gtt/       =-=-=-=-<

_______________________________________________
Info-cvs mailing list
address@hidden
http://mail.gnu.org/mailman/listinfo/info-cvs