Thank you the LineNumberingPushbackReader is exactly what is needed.
The other metadata I can add fairly straightforwardly so good, this is
*far* more sane than that monstrosity I conjured up.
Kevin
On Apr 20, 3:15 am, Ilia Ablamonov wrote:
> I've encountered the same problem (as far as I unde
I've encountered the same problem (as far as I understood) in Fleet.
My solution is
http://github.com/Flamefork/fleet/blob/master/src/fleet/loader.clj#L55
There code comes from String, but you can use FileReader instead of
StringReader.
File path must be specified additionally, but this should be
the alternative is patching the java reader, which may not be too bad
On Mon, Apr 19, 2010 at 4:30 PM, Kevin Livingston
wrote:
> Cool, thanks. Although, the clojure reader seems fine for what I need
> - i'd like to keep it as simple as possible. (the whole reason for
> doing this is to not have
That is really nasty. :)
P.S. Clojure's equivalent of progn is called do.
-Per
On Tue, Apr 20, 2010 at 1:43 AM, Kevin Livingston
wrote:
> SO as a complete hack to get file and line number metadata I
> implemented this macro, my file of rules is now just loaded with load-
> file and the rules th
Cool, thanks. Although, the clojure reader seems fine for what I need
- i'd like to keep it as simple as possible. (the whole reason for
doing this is to not have to write a parser for a whole new rule file
format) I just wanted the extra meta data, if it was easy to grab.
Seems like there could
if you really want I have a port of LispReader to clojure, it only
adds metadata to list forms, like LispReader, but altering it should
not be too hard. I haven't made any attempt to keep the reader up to
date, but I don't believe LispReader is under going very many changes.
http://github.com/hire
SO as a complete hack to get file and line number metadata I
implemented this macro, my file of rules is now just loaded with load-
file and the rules that are define in it with RULE have the
appropriate file and line associated with them. This is compete abuse
of DEF and maybe the compiler (altho
On Sat, Apr 17, 2010 at 2:29 AM, Kevin Livingston
wrote:
> I have an application that will read in a large number of structures
> from a file. those structures will be used throughout the application
> to produce additional data etc. since they are "user" configurable,
> it would be nice to know
I have an application that will read in a large number of structures
from a file. those structures will be used throughout the application
to produce additional data etc. since they are "user" configurable,
it would be nice to know where they come from should one of them start
misbehaving. the t
