Re: creating classes on the fly ??
Re: creating classes on the fly ??
- Subject: Re: creating classes on the fly ??
- From: Daniel Child <email@hidden>
- Date: Wed, 26 Sep 2007 12:34:37 -0400
Wow, interesting suggestion. I have never used Python, but I will
look into. I have to say that I find working with strings in Obj-C
very tedious. Even my prototype Lexicon using NSDictionary doesn't
seem to work, as I fill it with one set of values, and when I search,
it returns something different than what I was searching for. If
Python could make things easier, that would be great.
When you say "OP" you mean "Object-Predicate"? I don't understand
your meaning when you say Core Data would be a bad match for storing
lexical data....
On 9/22/07, Thomas Engelmeier <email@hidden> wrote:
I would actually recommend to do a prototype in Python just to
understand the algorithms involved. You will also be 10x more
productive in Python since text processing is so much easier.
- Cocoa data structures -> easiest to use, might be inefficient
- C++ std:: data structures -> no serialisation buildt in, beware
std::string is not Unicode-Savy
You forgot to mention: crazy fast. Also, std::wstring will deal with
unicode just fine and Boost can provide serialization. If required.
- Core Data -> Even with an far higher abstraction layer it might be
faster due to under-the-hood paging out of unused entries.
I doubt it. The OPs use case sounds like a bad match for Core Data
actually. It is absolutely fine for doing structured queries but
analyzing parsed data that you have in memory in some handy data
structures is one of those things that maps terrible to that model.
S.
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden