You were closer the first time. What happened was I was using a compile that didn't have these features, so when I needed them, I put in a new framework. Sadly, when I put it in, xcode (rightly so) erased my copy phase for the framework, so I was getting an older framework.
My compile is for 10.4, and now I have an actual non-null pointer for the function. Thanks for all the help, [>] Brian On Jun 10, 2010, at 5:42 PM, Brent Fulgham wrote: > Bryan, > > I just realized what your problem was during a WWDC session. > > Double check your compiler settings. If you are building to target Leopard > (maybe Tiger?) Mac OS will null out features that don't exist in those older > OS versions. > > Maybe someone from Apple can tell us when Safari 4 support kicks in based on > build OS target. > > -Brent > > Sent from my iPhone > > On Jun 10, 2010, at 8:38 AM, Brent Fulgham <bfulg...@gmail.com> wrote: > >> Hi Brian, >> >> On Jun 5, 2010, at 4:37 PM, Brian Barnes wrote: >> >>> I would like to save the state of several scripts. My system is event >>> driven so there is never any script in an executing state when I save/load. >>> This means all I need to save is the global object. Looking through the >>> headers I found: >>> >>> JSValueCreateJSONString/JSValueMakeFromJSONString >>> >>> This, of course, is perfect for me, but it doesn't seem to be implemented >>> in my build (which is pretty recent.) This might be a mis-understanding on >>> my part about how to get these features in, or it's just not implemented >>> yet (the actually function address is NULL.) >>> >>> Is this me not understanding the code or is this a feature I'll have to >>> wait for? I should point out that I'm just grabbing the nightly build and >>> pulling out the framework. Is there another way to serialize/de-serialize >>> an object in a script? >> >> Are you sure you are linking against your recent build? JavaScriptCore is a >> core component of Mac OS, so you might be inadvertently linking against the >> system version. I've made this mistake before, and even trashed my OS by >> clobbering the system JavaScriptCore with my build in an effort to force >> things to link properly! :-) >> >> I'm not sure which OS you are running on (or which version of Safari is >> installed). The header indicates this feature should be present as of >> Safari 4.0, so it seems likely that even the system WebKit would have it, >> but it's worth double-checking. >> >> Aside from that, I would expect the feature to be present. I'll see if I >> can try this out myself and suggest anything else. >> >> -Brent
_______________________________________________ webkit-help mailing list webkit-help@lists.webkit.org http://lists.webkit.org/mailman/listinfo.cgi/webkit-help
