Is it worth persevering with Macports_Framework?
larryv at macports.org
Wed Feb 13 23:02:49 PST 2013
On Feb 12, 2013, at 3:23 PM, Landon J Fuller <landonf at macports.org> wrote:
> There have been various partial efforts to revisit the Tcl<->C/ObjC bindings question, and possibly replacing some of the MacPorts core in C/ObjC. Take a look at base/src/cflib1.0 and base/src/tclobjc1.0, for example.
> If I were ever to revisit the problem space again, I'd use this as a jumping off point to begin reimplementing portions of the stack in C/ObjC and replacing Tcl -- slowly working my way down the stack to the point that eventually only the actual port interpreter was running Tcl for the purpose of scripting port build/installation.
This is an intriguing idea, although it would no doubt require a ton of work. What would be the advantages of such a rewrite?
More information about the macports-dev