Date: Mon, 2 Feb 2009 03:56:44 -0500 From: Garance A Drosihn <drosih@rpi.edu> To: Garrett Cooper <yanefbsd@gmail.com> Cc: giffunip@tutopia.com, freebsd-current@freebsd.org Subject: Re: Alternatives to gcc (was Re: gcc 4.3: when will it becomestandard compiler?) Message-ID: <p06240804c5ac650b47be@[128.113.24.47]> In-Reply-To: <7d6fde3d0902020020n3d5aac5cu4f3381a195d6fdcf@mail.gmail.com> References: <87223.61659.qm@web32707.mail.mud.yahoo.com> <p06240803c5ac33499e88@128.113.24.47> <7d6fde3d0902020020n3d5aac5cu4f3381a195d6fdcf@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
At 12:20 AM -0800 2/2/09, Garrett Cooper wrote: >On Sun, Feb 1, 2009, Garance A Drosihn <drosih@rpi.edu> wrote: > > While it could be made compile-time compatible with readline, it >> wasn't a completely adequate replacement for this program of ours. >> >> The guy who tried this said it was because our program takes >> advantage of knowing some of the internals of what readline is > > doing, so it can implement a few extra features. >It's *mostly* feature complete. The only thing that's really missing >is libhistory, which is required for some things like python's >readline support. Other programs like MySQL happily used libedit >embedded into their source without issues. Well, our program does include history, so that's probably where we ran into trouble with libedit. (I should add that I really do mean to fix the program so libedit can be used as an option, it's just that I've got too many other projects ahead of it in my list of projects to-do). -- Garance Alistair Drosehn = gad@gilead.netel.rpi.edu Senior Systems Programmer or gad@freebsd.org Rensselaer Polytechnic Institute or drosih@rpi.edu
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?p06240804c5ac650b47be>