[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: shared object libfl?
From: |
Andrew S Halper |
Subject: |
Re: shared object libfl? |
Date: |
Tue, 24 Jul 2001 16:03:05 -0700 |
Hmm. Although rather sketchily documented, it appears I might able to use
GLib to do this, so maybe having a dynamic libfl is not so much of a
priority after all:
http://developer.gnome.org/doc/API/glib/glib-lexical-scanner.html
Thanks,
Andy
Andrew S
Halper To: "W. L. Estes" <address@hidden>
cc: address@hidden
07/24/01 09:51 Subject: Re: shared object
libfl?(Document link: Andrew S Halper)
AM
OK, thanks. In the meantime I'll try work around it by writing my own
lexer.
Andy
"W. L. Estes"
<address@hidden To: address@hidden
.edu> cc:
Subject: Re: shared object libfl?
07/24/01
10:12 AM
> In a nutshell, I'm using flex/bison to write an SQL import parser for Dia
> (http://www.lysator.liu.se/~alla/dia/dia.html) as a plug-in, and the Dia
> plug-ins are expected to dynamically link their libraries (I believe they
> are dynamically linked modules themselves). I've seen hints on the Net
that
> there might be a way around this by using libtool and dlopen, but I'm too
> much of a linker neophyte to be able to attempt that. I was wondering if
> there is some technical reason for flex only being statically linked, or
it
> just never came up?
Well, there hasn't been a release of flex in ~5 years. And back that
long ago, shared libraries were harder to do in a meaningfully
portable way.
But, I can see some potential downfalls with making libfl into a
shared library. MOstly they are the same reasons that one doesn't want
to make anything into a shared library. I'll think about this and see
what makes sense. If you'd like to post your question to
address@hidden and explain what your motivation is in more detail
for asking, you'll probably get more feedback that way. (help-flex@ is
the official channel for all things flex.)
Thanks,
--Will