Bob Ammerman wrote:

> Well, I might finally have a really good excuse for my customer
> standardizing on one editor. We are now looking at the possibility of
> implmenting compiler integration for the proprietary language. Since
> the compiler only runs on Linux this will involve me writing a tcp
> client for Windows nd server on Linux. The 'compiler' invoked by the
> editor is really the TCP client program which then sends the compile
> request to the TCP servier on Linux. After the compile completes the
> Windows app will format up the error file in the format required by
> the editor for its error list. Obviously I only want to do this once
> (or more truthfully my customer only wants to pay me to do this
> once).

A decent general-purpose coding editor can invoke custom compile
commands and parse pretty much any error file that contains the required
information in a regexp-parsable format. 

So if your TCP app has a command line interface and the generated error
file adheres to some minimal requirements, pretty much any decent coding
editor would be able to transparently work with this setup. 

("Transparently" in the sense that you couldn't tell, not in the
compiler executable and not by analyzing the source files, what editor
was used to create the sources and the binaries.)

Still no "good excuse" :)

Gerhard
-- 
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist