Rostislav Svoboda <rostislav.svob...@gmail.com> writes: Hi Rostislav,
>> You want do diffs > > I think you need to concentrate on a way how a diff is made and > defined if you want to improve the way how a VCS works. I.e. current > VCSs use something like this: > > @ some line numbers @ > - replacing that old line... > + ... with this new line > > which works well for a machine, but it's (almost always) meaningless > for a human mainly because a VCS knows nothing about the language your > file is written in. I don't think so. After some practice you can read patches as if they were finest prose. ;-) > This has some huge implications. Even with a good GUI editor, when you > compare files, you see just some blocks of text being > deleted/inserted/changed or shifted. So the meaning of the diff is > quite often pretty hard to understand. > > IMO the next generation of VCSs must be content-aware working with > content-aware diffs There are already special-purpose, format-dependent diff/patch tools, e.g., XMLdiff, various binary diff/patch tools, and some more. Bye, Tassilo -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en
