public inbox for kawa@sourceware.org
 help / color / mirror / Atom feed
From: Per Bothner <per@bothner.com>
To: Chuah Teong Leong <teongleong@gmail.com>
Cc: kawa@sourceware.org
Subject: Re: emacs CEDET auto-complete
Date: Fri, 19 Apr 2013 23:05:00 -0000	[thread overview]
Message-ID: <5171CD78.8040600@bothner.com> (raw)
In-Reply-To: <516EECA3.4070603@bothner.com>

On 04/17/2013 11:40 AM, Per Bothner wrote:
> What looks like a big hurdle when using CEDET is that it
> assumes a separate parser/analyzer using the Semantic tool.

http://cedet.sourceforge.net/addlang.shtml does say:

   You can also pull in an external tool like Exuberant CTags to parse
   your files. This can be handy to bootstrap support for your language.
   External parsing tools often have issues where the actual extents of
   the TAG in your buffer is unknown. They also have problems in that
   the buffer must be saved before they can work.

(NetBeans avoids the unsaved-buffers problems by giving the compiler
access to the buffer.  That is easier when they're in the same
Java process, but otherwise sockets or temporary files could be used.)

Regardless, better tool support for Kawa would be very nice.
I think it would be better someone other than me do the
heavy lifting.  However, if that someone needs extra support
from Kawa (like a symbol table dumper) I'll be happy to help.

I also very interested in helping if someone wants to
warn on NetBeans integration - that would probably
help more people.
-- 
	--Per Bothner
per@bothner.com   http://per.bothner.com/

      parent reply	other threads:[~2013-04-19 23:05 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-17  9:13 Chuah Teong Leong
2013-04-17 15:02 ` Jamison Hope
2013-04-17 18:40 ` Per Bothner
2013-04-18  2:42   ` Chuah Teong Leong
2013-04-19 23:05   ` Per Bothner [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5171CD78.8040600@bothner.com \
    --to=per@bothner.com \
    --cc=kawa@sourceware.org \
    --cc=teongleong@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).