Thanks for the reply, Alex.
I need to use Windows without cygwin dlls for an application I'm working on
now. So, I had been using miniPicoLisp in my application, which compiles ok
under mingw. That let me avoid even trying to compile regular PicoLisp using
mingw, and the porting issues that would involve.
But now I might have to take a look at trying PicoLisp with mingw. I know the
file locking will probably be an issue, but not sure what else might be a snag
with PicoLisp under mingw.
On the other hand, I was able to hack in some support for line numbers and file
names for error messages in miniPicoLisp, relatively quickly.
--- On Sun, 9/4/11, Alexander Burger <a...@software-lab.de> wrote:
> From: Alexander Burger <a...@software-lab.de>
> Subject: Re: error message line numbers
> To: firstname.lastname@example.org
> Date: Sunday, September 4, 2011, 11:29 PM
> Hi Doug,
> > Is there a way I can make (mini)PicoLisp give me line
> numbers from .l source files in error messages? There
> are lots of gnu and/or linux tools (like vim) and IDEs etc.,
> that want error messages in a format similar to what gcc
> spits out, like:
> > Baz.cpp:321: error: 'foobar' was not declared in this
> > (I poked around in the code and on the site looking,
> but missed it if it is there.)
> All other PicoLisp implementations (64-bits, 32-bits and
> Ersatz) have
> this feature. They keep track of the file name and line
> number in the
> 'inFile' structure (or LineNumberReader in case of Java).
> For MiniPicoLisp this is difficult, because it uses plain
> stdio instead
> of a dedicated 'inFile' structure.
> - Alex
> UNSUBSCRIBE: mailto:email@example.com?subject=Unsubscribe