-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Thursday, January 17, 2002, at 11:37 AM, El JoPe Magnifico wrote: > (*) As a perl devotee, I understand your revulsion to forced use of > indentation, Randall. I'm of the same mind... but only with respect > to soruce code. This is not source code though, but rather essentially > a config file, and use of whitespace to indicate nesting makes far more > sense in that circumstance, IMHO. I can't seem to access <http://www.yaml.org/>, so I may be entirely off-base here, but... I rather dislike any sensitivity to the type or amount of white space (with the exception of newlines -- sometimes) simply because it tends to cause problems. Look at syslog.conf! If you accidently use spaces instead of tabs, you'll get weird errors. If I accidently put an extra space in, or a tab, or anything like that, what happens? I would prefer to move to a format that ignores variations in whitespace, including newlines. I want to be able to write something like <DescriptionDetail>Blah blah blah</DescriptionDetail> (or whatever, those tags are rather long) and not have to worry about wrapping my lines to <78 characters or whatever the limit is. Furthermore, I can then format the file however I want without worry about unintended consequences. Again, I can't access <http://www.yaml.org/>, but it really doesn't sound that attractive to me. Daniel - -- PGP public key: http://mwdesign.dyndns.org/~daniel/publickey.txt ACA4 FA04 4033 0569 C626 AA1A C489 25A5 5F67 C125 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (Darwin) Comment: For info see http://www.gnupg.org iD8DBQE8R7i0xIklpV9nwSURAnGvAJ9HLQdV0oo7fq/gE8j+lV/tS1Sa2gCg1H/R Iv6IW6qf2nrHPOClJAPwXHY= =LUg9 -----END PGP SIGNATURE----- _______________________________________________ Fink-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/fink-devel
