ObjFW  History of tests/OFURLTests.m of d55e95f217f3fd21

This is as per the RFC, which says the scheme and path can never be
missing, while the path can be empty. file: [e9cb46977b] check-in: [3e455c4839] user: js, branch: trunk, size: 14188 [annotate] [blame] [check-ins using] [diff]

The scheme does not allow percent encoding. file: [ba89cb38e8] check-in: [13ead1212f] user: js, branch: trunk, size: 14168 [annotate] [blame] [check-ins using] [diff]

With a dictionary the order is lost and keys cannot exist more than
once. file: [5a6871bef0] check-in: [bd6dd6dd00] user: js, branch: trunk, size: 13287 [annotate] [blame] [check-ins using] [diff]

It duplicates the functionality of -[OFMutableURI setQueryDictionary:]. file: [66101ddcf7] check-in: [f1bf64ca9f] user: js, branch: trunk, size: 13169 [annotate] [blame] [check-ins using] [diff]

ObjFW's style changed over the years, but the tests were never adjusted
to it. file: [641ece2b4e] check-in: [14f1e22d79] user: js, branch: trunk, size: 12938 [annotate] [blame] [check-ins using] [diff]

Since C guarantees minimum sizes for char, short, int, long and long
long, these can be used instead. file: [52cea266a3] check-in: [25c985fec1] user: js, branch: trunk, size: 12037 [annotate] [blame] [check-ins using] [diff]

OFAutoreleasePools have long been discouraged in favor of the runtime's
autorelease pools. file: [8adc5244fa] check-in: [09be825f88] user: js, branch: trunk, size: 10630 [annotate] [blame] [check-ins using] [diff]

This prevents forgetting to add an import to ObjFW.h, as the tests would
then not compile. file: [ac6cede6ad] check-in: [dc0c6c34ab] user: js, branch: trunk, size: 10367 [annotate] [blame] [check-ins using] [diff]

This also changes OFFileManager to use a buffer with getcwd() rather
than depending on the extension that passing NULL as a buffer will
allocate one. file: [0de5c9643a] check-in: [d133fa0a89] user: js, branch: trunk, size: 9651 [annotate] [blame] [check-ins using] [diff]

This allows retrieving it how it was originally stored, which is useful
for example for query strings, as these often URL-encode allowed
characters in order to allow pairs of the form foo=bar&bar=qux. file: [291a443212] check-in: [a15b403a11] user: js, branch: trunk, size: 4962 [annotate] [blame] [check-ins using] [diff]

This also means the parameters go away and get folded into the path. file: [96f3992920] check-in: [5f7305c659] user: js, branch: trunk, size: 4118 [annotate] [blame] [check-ins using] [diff]

This removes the special handling dependent on the scheme. file: [26f206153b] check-in: [0f995db06d] user: js, branch: trunk, size: 3260 [annotate] [blame] [check-ins using] [diff]

Forgot to add 2017, even though I already did quite some changes in
2017. file: [b43f4c978f] check-in: [44f45c2e35] user: js, branch: trunk, size: 3199 [annotate] [blame] [check-ins using] [diff]

URL decoding and reencoding is not lossless: For example, if the query
was foo=bar&qux=foo%25bar, it will be decoded to foo=bar&qux=foo&bar and
then reencoded to foo=bar%25qux=foo%25bar, which is a different thing.

The only way to solve this is to let the application handle the URL
decoding and encoding according to its own rules, as those might be
different depending on the application. file: [6d34fa57cb] check-in: [516517deb3] user: js, branch: trunk, size: 3193 [annotate] [blame] [check-ins using] [diff]

While at it, also update the mail address. file: [b3ecd6e7b1] check-in: [2a27cf3000] user: js, branch: trunk, size: 3170 [annotate] [blame] [check-ins using] [diff]

While Cocoa includes it, RFC 1738 explicitly states that the "/" between
host / port and path is not part of the path. file: [d80e8f78e3] check-in: [d2487bc7e1] user: js, branch: trunk, size: 3162 [annotate] [blame] [check-ins using] [diff]

Before, it was not clear that the object is an OFURL, which could make
debugging hard. file: [60bd347261] check-in: [e164def279] user: js, branch: trunk, size: 3157 [annotate] [blame] [check-ins using] [diff]