On May 21, 2010, at 1:29 PM, David Duncan wrote:
> On May 21, 2010, at 10:23 AM, Patrick Rutkowski wrote:
>
>> Any API that accepts binary data needs to give at least a hint as to what
>> format the binary data should be. Saying that just it accepts "data" is
&
On May 21, 2010, at 1:31 PM, Kyle Sluder wrote:
> On Fri, May 21, 2010 at 10:23 AM, Patrick Rutkowski
> wrote:
>> Milder tone? No thanks.
>
> Awfully strong words from someone who waltzes onto a mailing list,
> lambastes the documentation, and admits in the very next sent
> On 05/21/2010 10:23 AM, "Patrick Rutkowski" wrote:
>
>> Milder tone? No thanks.
>>
>> Any API that accepts binary data needs to give at least a hint as to what
>> format the binary data should be. Saying that just it accepts "data" is
>&g
moron.
-Patrick
On May 21, 2010, at 1:07 PM, Kyle Sluder wrote:
> On Fri, May 21, 2010 at 9:39 AM, Patrick Rutkowski wrote:
>> I find it disgusting that the doc section for NSXMLParser initWithData takes
>> binary data, but doesn't tell you which encoding it's supposed t
I find it disgusting that the doc section for NSXMLParser initWithData takes
binary data, but doesn't tell you which encoding it's supposed to be?
Link:
http://developer.apple.com/mac/library/documentation/cocoa/reference/foundation/Classes/NSXMLParser_Class/Reference/Reference.html#//apple_ref/o
want.
If I link my framework dynamically against OpenSSL, then I force the clients of
my framework to use the dynamic version of OpenSSL, which I also don't want.
(correct me if I'm wrong on either of those points)
-Patrick
On May 15, 2010, at 11:29 PM, Patrick Rutkowski wrote:
&g
I'm building a Framework which internally uses OpenSSL, and exposes a sort of
OpenSSL wrapper for various small purposes.
However, when linking the framework, Xcode complains of missing symbols like:
_ERR_error_string_n
_ERR_clear_error
_SSL_CTX_free
_SSL_CTX_new
_ERR_get_error
_SSL_library_init
