Why should I use XML instead of HTML?

本文探讨了XML相较于HTML的优势,包括自定义文档类型的能力、更丰富的内容表现形式、更好的浏览器呈现性能、简化了的复杂性以及提高了信息的可访问性和重用性。
<script type="text/javascript" src="http://pagead2.googlesyndication.com/pagead/show_ads.js"> </script> Authors and providers can design their own document types using XML, instead of being stuck with HTML. Document types can be explicitly tailored to an audience, so the cumbersome fudging that has to take place with HTML can become a thing of the past: authors and designers are free to invent their own markup elements; Information content can be richer and easier to use, because the descriptive and hypertext linking abilities of XML are much greater than those of HTML. XML can provide more and better facilities for browser presentation and performance, using CSS and XSL stylesheets; It removes many of the underlying complexities of SGML in favor of a more flexible model, so writing programs to handle XML is much easier than doing the same for full SGML. Information will be more accessible and reusable, because the more flexible markup of XML can be used by any XML software instead of being restricted to specific manufacturers as has become the case with HTML. Valid XML files are kosher SGML, so they can be used outside the Web as well, in existing SGML environments.
If so, just execute both commands and retry the installation as mentioned above. You can now use valgrind as normal. Note: in case of failures during the build, make sure you have the latest Xcode/CLI tools installed. Update Any brew upgrade will now correctly rebuild the latest LouisBrunner/valgrind instead of the upstream one (which doesn't support the latest macOS versions). brew upgrade --fetch-HEAD LouisBrunner/valgrind/valgrind Tests Linux (Ubuntu 24.04) These errors seem to come from the CI environment itself (as they show with or without my changes). == 857 tests, 20 stderr failures, 1 stdout failure, 0 stderrB failures, 0 stdoutB failures, 0 post failures == none/tests/fdleak_cmsg (stderr) none/tests/fdleak_cmsg_supp (stderr) none/tests/fdleak_cmsg_xml (stderr) none/tests/fdleak_creat (stderr) none/tests/fdleak_creat_sup (stderr) none/tests/fdleak_creat_xml (stderr) none/tests/fdleak_dup (stderr) none/tests/fdleak_dup2 (stderr) none/tests/fdleak_dup2_xml (stderr) none/tests/fdleak_dup_xml (stderr) none/tests/fdleak_fcntl (stderr) none/tests/fdleak_fcntl_xml (stderr) none/tests/fdleak_ipv4 (stderr) none/tests/fdleak_open (stderr) none/tests/fdleak_pipe (stderr) none/tests/fdleak_socketpair (stderr) none/tests/linux/getdents_filter (stdout) none/tests/rlimit64_nofile (stderr) none/tests/rlimit_nofile (stderr) none/tests/track_high (stderr) none/tests/track_yes (stderr) should be (according to the official Fedora x86_64 builds) == 835 tests, 4 stderr failures, 0 stdout failures, 0 stderrB failures, 0 stdoutB failures, 0 post failures == memcheck/tests/descr_belowsp (stderr) helgrind/tests/tc22_exit_w_lock (stderr) drd/tests/std_thread2 (stderr) drd/tests/tls_threads (stderr) See here for details. macOS See the macos-VERSION-expected.txt in .github/ for more details about which tests pass on which version. Some tests are a bit flaky and might fail randomly, see .github/flaky-tests.txt for more details. Contributing Suppressions Valgrind is a very thorough program and can often report false positives. There are wide range of reasons why those come up (e.g. Valgrind not tracking some OS-specific part of the memory). Moreover, Valgrind might also report issues inside standard libraries, which are relevant for maintainers of such projects, but not to the end-user. While fixing those issues would be better, it isn't always possible. This is why Valgrind supports a system called "suppressions", which is a special file format instructing which errors to ignore so the end-user doesn't see them. Because some of those errors only show in special conditions, you might be asked to provide a "suppressions" file to be added to the repository. You can also keep those local to the project you are debugging and use them when running Valgrind. To create a "suppressions" file, simply run: valgrind YOUR_VALGRIND_OPTIONS --gen-suppressions=all YOUR_PROGRAM YOUR_PROGRAM_ARGS # for example: valgrind --trace-syscalls=yes --gen-suppressions=all ls -la # if you want to choose on a case-by-case basis instead of generating all the suppressions, you can do: valgrind --trace-syscalls=yes --gen-suppressions=yes ls -la You will then see a few extra entries in your output, they will look something like that: { <insert_a_suppression_name_here> Memcheck:Cond fun:_platform_strlen fun:_mh_execute_header fun:(below main) } or { <insert_a_suppression_name_here> Memcheck:Param write(buf) fun:write$NOCANCEL obj:/dev/ttys002 fun:_swrite fun:__sflush fun:__sfvwrite fun:puts fun:_mh_execute_header fun:(below main) } You can then add them to a new file, e.g. one called my.supp, replace the name <insert_a_suppression_name_here> with a description of the issue for later use. You can also use # to comment out lines, for documentation or disabling specific suppressions. Check any of the .supp files in this repository for examples, e.g. darwin19.supp. Acknowledgements tyrael9: for their work around porting Valgrind to iOS armv7 which was used as part of the port to arm64 (see here) Footnotes Supported as part of upstream Valgrind ↩ PowerPC is unsupported (#62) ↩ macOS 15 arm64 is experimental (#123) ↩翻译
11-15
评论
成就一亿技术人!
拼手气红包6.0元
还能输入1000个字符
 
红包 添加红包
表情包 插入表情
 条评论被折叠 查看
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值