Hi all,
Sometime around January I finished bugging everyone here on building a
bridge between the Objective-C runtime and an scripting interpreter I
had come across. I was a newbie to both languages, so the project
alternated between fun, frustrating and educational. Being a
fledgling attempt, however, I wasn't completely satisfied with the
results.
I'm thinking of making another go of it, but would like some advice.
In the previous attempt I essentially packed everything into one .m
file. It wasn't even particularly object-oriented. I just sort of
worked it out as I went along, deleted what I thought was bad and
inserted what I thought worked. I figured I'd clean things up later.
What I'd like to do now is instead wrap the interpreter's C code
inside an Objective-C object. Then I'd like use the tutorials on
Apple's site and elsewhere to create some kind of plug-in system so
that I can create separate modules for functionality instead of
packing it all together. I'm hoping this will make future maintenance
and modification easier.
Before I start,though, I thought I'd ask about any pros and cons of my
intended approach. Is it even a good idea?
Much thanks for your help,
Erik
|
