the upstream doesn't bump the major
number (change the soname) every time they break backward binary
compatibility.
HTH
--
Rob Browning
rlb @defaultvalue.org and @debian.org; previously @cs.utexas.edu
GPG starting 2002-11-03 = 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4
versions in the names, and then also
provide a symlink for dlopen/dynamic-link:
/usr/lib/libfoo.so.N
/usr/lib/libfoo-N.so -> libgw-guile-foo.so.N
Given that, you can still use (dynamic-link "libgw-guile-foo-N"), but
nothing else has to deal with the versioned name. Of course if you
w
ahead and modularize the rest of the reports (for consistency), and
then any other files that need it. These fixes won't show up in
1.6.0, but look for a (hopefully) large --nofile startup speedup in
1.6.X.
Thanks for the report.
--
Rob Browning <[EMAIL PROTECTED]> PGP=E80E0D04F5
ybe it is stalling on
> something really stupid like name resolution.
There was apparently also some issue with guppi -- I think maybe it
was reading from /dev/random, and so it won't finish until the entropy
pool has been full enough to generate all the random numbers it
needs. If th
an instatiated report to the
> menus.
Well, if I were using rsync or vpn+NFS to allow me to work on the same
file from work and home, I'd probably want my changes to automatically
show up both places, wrt to reports *and* window config, and this is
one place, that unless we go to some lengt
that an awful lot of the config data belongs in
the data store. Delete the "file" and the config data goes with it.
Also, if we do eventually have a multi-user, remote access,
user-travelling-from-machine-to-machine, setup, then storing most of
the config data in the data store prob
und forever -- not a scalable approach, really.
One solution would be for Gnome MDI to have an API that allows you to
tell it to give you the data it wants stored, and to ask you for that
data when it needs it (i.e. at file open time). That seems like a
much cleaner approach for situat
;...
I've sort of toyed with the idea of an emacs or terminal interface for
a while. Not necessarily anything full-blown, but "M-x
gnc-add-transaction" would be nice :>
--
Rob Browning <[EMAIL PROTECTED]> PGP=E80E0D04F521A094 532B97F5D64E3930
_
Derek Atkins <[EMAIL PROTECTED]> writes:
> Um, you can certainly perform MD5 in Java... Look at www.cryptix.org
And make sure your input is at least as random as gnucash's. There
should be as close to no chance that you'll accidentally generate
duplicate keys as possible
s some
documentation too, so I'd rather write something up and submit a patch
than describe it several times, but if you need info *now*, I'd be
happy to oblige :>
--
Rob Browning <[EMAIL PROTECTED]> PGP=E80E0D04F521A094 532B97F5D64E3930
___
se is near, the longer we can delay, the
better, because as time passes, the set of issues we'd need to address
constantly changes.
WRT RH 6.2, for now I think you can rest easy. AFAIK, Dave has made
it clear he plans for us to support 6.2, much to my guile
s, you'll then be
able to query the pricedb for the latest price for a given commodity
with:
price = gnc_pricedb_lookup_latest(db, commodity);
--
Rob Browning <[EMAIL PROTECTED]> PGP=E80E0D04F521A094 532B97F5D64E3930
___
gnucash-devel mailing list
[EMAIL PROTECTED]
http://www.gnumatic.com/cgi-bin/mailman/listinfo/gnucash-devel
/ctags issue, it should be possible to add
some tests to configure.in to actually determine which one to use
dynamically, or, as suggested, we could just allow a
--with-tags-prog=foo option.
In my experience, building the TAGS file doesn't appear to add
appreciable build time when compared to the ove
l thing" IIRC.
there's a trademark on bookshelf. i wouldn't be surprised :)
dres: retch.
rlb: to wrap this up, maybe you could post an excerpt of this
discussion to the ML, for later reference, --- dres has changed the
topic to: Today's Gripe: People exchanging "Wh
t time you'd updated was?
What version of g-wrap are you running, and when did you last change
it?
Thanks
--
Rob Browning <[EMAIL PROTECTED]> PGP=E80E0D04F521A094 532B97F5D64E3930
___
gnucash-devel mailing list
[EMAIL PROTECTED]
http://w
27;t recognize the valid types without extra help, then I
suppose we could just require that "save/restoreable" things be tagged
somehow. I can think of half-baked schemes which might allow this,
but it's not worth dwelling on until/unless we need it.
Hope this is rele
ay to find out
when things are going to happen is to probe every possible event time.
And since I had also imagined that we might want to be able to
schedule things to the hour or to the minute, this could quickly
become very expensive.
--
Rob Br
so the configure process can pick up both
the right guile and the right guile-config.
Finally, if you've changed anything since you downloaded the source
(or if you've CVS updated lately), you should make sure and re-run
./autogen.sh YOUR-ARGS, but make sure and do it with
r/local/opt/gnucash-unstable/bin/gnucash
--
Rob Browning <[EMAIL PROTECTED]> PGP=E80E0D04F521A094 532B97F5D64E3930
___
gnucash-devel mailing list
[EMAIL PROTECTED]
http://www.gnumatic.com/cgi-bin/mailman/listinfo/gnucash-devel
ucash the same way, but I could
put some annotation about whether it was 2/1 or whatever in the memo
or notes field if I wanted/remembered.
> Can mutual funds split?
Don't know.
--
Rob Browning <[EMAIL PROTECTED]> PGP=E80E0D04F521A094 532B97F5D64E3930
___
This version should produce working rpms. The previous version had
problems with shared library symlinks.
Thanks to Derek for helping debug/fix the problem(s).
--
Rob Browning <[EMAIL PROTECTED]> PGP=E80E0D04F521A094 532B97F5D64E3930
___
g
ast have the functional problems fixed...
Thanks for the help.
--
Rob Browning <[EMAIL PROTECTED]> PGP=E80E0D04F521A094 532B97F5D64E3930
___
gnucash-devel mailing list
[EMAIL PROTECTED]
http://www.gnumatic.com/cgi-bin/mailman/listinfo/gnucash-devel
Derek Atkins <[EMAIL PROTECTED]> writes:
> Rob Browning <[EMAIL PROTECTED]> writes:
>
> > Derek Atkins <[EMAIL PROTECTED]> writes:
> >
> > > Ok, I look forward to seeing what you have to say. This is when I
> > > really wish guile
e what guile realized it needed to be
doing as of 1.3.4... so g-wrap 1.1.8 should fix your problem. It's
on the ftp site now. Lemme know.
Thanks
--
Rob Browning <[EMAIL PROTECTED]> PGP=E80E0D04F521A094 532B97F5D64E3930
___
gnucash-devel mailin
ord #f
OK, I've got a guile 1.3 g-wrap sandbox installed, and I can now
reproduce the problem. Stay tuned.
--
Rob Browning <[EMAIL PROTECTED]> PGP=E80E0D04F521A094 532B97F5D64E3930
___
gnucash-devel mailing list
[EMAIL PROTECTED]
http://www.
to the cell data and a "next" pointer to the
> remainder of the list.
And anyone who's familiar with glib, LISP lists are somewhat similar
to GSLists. GLists are actually doubly linked...
--
Rob Browning <[EMAIL PROTECTED]> PGP=E80E0D04F521A094 532B97F5D64E3930
_
that
helps. Then we'll have to decide if libgw-runtime.so.0 should be a
symlink or the actual binary. In this case, I doubt it matters.
Hope this helps.
--
Rob Browning <[EMAIL PROTECTED]> PGP=E80E0D04F521A094 532B97F5D64E3930
the output of
strace -f -o strace-dump.tmp guile
where you do the same thing at the prompt and then quit?
Thanks
--
Rob Browning <[EMAIL PROTECTED]> PGP=E80E0D04F521A094 532B97F5D64E3930
___
gnucash-devel mailing list
[EMAIL PROTECTED]
http:
e g-wrap lib-dir to your LD_LIBRARY_PATH. Could that be the
problem? i.e.
LD_LIBRARY_PATH=/usr/local/opt/g-wrap/lib gnucash ...
--
Rob Browning <[EMAIL PROTECTED]> PGP=E80E0D04F521A094 532B97F5D64E3930
___
gnucash-devel mailing list
[EMAIL PROTE
If you need any help with scheme, feel free to ask.
--
Rob Browning <[EMAIL PROTECTED]> PGP=E80E0D04F521A094 532B97F5D64E3930
___
gnucash-devel mailing list
[EMAIL PROTECTED]
http://www.gnumatic.com/cgi-bin/mailman/listinfo/gnucash-devel
ndation to the
the book people usually refer to as SICP. It's the "Structure
and Interpretation of Computer Programs" by Abelson and Sussman.
Aside from being an excellent way to learn scheme, it will
probably broaden the way you think about computer p
ully weak by comparison.
I had similar experiences with haskell, prolog, etc., but scheme is
the only one that had enough of a foot in the three worlds of power,
elegance, and practicality, to keep me committed to it for large
projects.
FWIW
--
Rob Browning <[E
er's homedir config instead, then you accumulate cruft whenever
files are deleted -- the files are gone, but their per-user settings
aren't. Further, putting these in the file eliminates the question of
which prefs go with which file.
FWIW.
-
ith the last rewrite. There'd be a few more things to be
done, but as I think about it, maybe not that much.
> I'm hitting Rob on his weak spot. Just say 'this will benefit the scheme
> language' and he gets all excited .
uppi
graph based on the data in the text embedded in our html widget
alongside the other html bits. Very clever.
--
Rob Browning <[EMAIL PROTECTED]> PGP=E80E0D04F521A094 532B97F5D64E3930
___
gnucash-devel mailing list
[EMAIL PROTECTED]
http://
y
realized I *really* wanted :>
Sounds quite right to me.
--
Rob Browning <[EMAIL PROTECTED]> PGP=E80E0D04F521A094 532B97F5D64E3930
___
gnucash-devel mailing list
[EMAIL PROTECTED]
http://www.gnumatic.com/cgi-bin/mailman/listinfo/gnucash-devel
ater when we're closer to needing to resolve it. It's
quite possible I'm not thinking of things that would make server-side
code a bad-idea(TM).
--
Rob Browning <[EMAIL PROTECTED]> PGP=E80E0D04F521A094 532B97F5D64E3930
___
gnucash-devel mailing list
[EMAIL PROTECTED]
http://www.gnumatic.com/cgi-bin/mailman/listinfo/gnucash-devel
t-type set to "stock-split". This
won't be exposed, so we can change it later if we need to, but
this slot may also be used later to distingush other types of
split (i.e. we may need one for closing the books, etc.)
--
Rob Browning <[EMAIL PROTECTED]> PGP=E
o seems fairly crucial to being able to
customize systems to integrate with a given business' existing
infrastructure. If they have a weak DB on the server, but they want
us to link to it, we could build a special version of our server-side
proxy that presents their database in the way we exp
place to add any code we need if we want to
make the encryption/authentication system more modular. Seems like a
more flexible approach in the long run, but of course it does have
it's own set of drawbacks.
FWIW.
--
Rob Browning <[EMAIL P
er than creating
categories in quicken. As long as you don't do something silly like
trying to open up one of these expense accounts, you can just go
along, blissfully pretending like they're just categories.
Is that not sufficient?
--
Rob Browning <
nother mail, I kinda think we might be better
served moving to one global, flat account list and having various
hierarchical structures pointing into that for display/organization
purposes, but even if we decide to do taht, it's probably not going to
happen in the next month or so.
FWIW.
test.
--
Rob Browning <[EMAIL PROTECTED]> PGP=E80E0D04F521A094 532B97F5D64E3930
___
gnucash-devel mailing list
[EMAIL PROTECTED]
http://www.gnumatic.com/cgi-bin/mailman/listinfo/gnucash-devel
ust require that the account
restore be nested inside a (or whatever) block that
handles ending the group's edits.
One thing that does still bother me a bit is that there's an assymetry
for groups now. We don't have an xaccGroupBeginEdit to balance the
commit edit. Perhaps we should
anges, but which ones? This is getting messy.
I defintely don't know enough right now to know what the "constants"
here are. Company name changes are obviously ephemeral, but, thinking
about it, it seems like ticker symbols, and perhaps even exchanges
could be too...
--
Rob Browni
r that?
In point of fact, I don't really care which way we go, and I think you
know me well enough to know that difficulty in implementation isn't
usually at the top of my criteria list. I'd just like to make sure we
pick the best answer given what we know and where we think we might
even sure there
was any consensus that it was the right thing to do. Hoever, I
thought David might want to a least be aware of the discussion.
--
Rob Browning <[EMAIL PROTECTED]> PGP=E80E0D04F521A094 532B97F5D64E3930
___
gnucash-devel mailing li
ew projects we
can beg/borrow from.
--
Rob Browning <[EMAIL PROTECTED]> PGP=E80E0D04F521A094 532B97F5D64E3930
___
gnucash-devel mailing list
[EMAIL PROTECTED]
http://www.gnumatic.com/cgi-bin/mailman/listinfo/gnucash-devel
one could, in confidence, pick one dbms and adopt it
> without reservation, the discipline of building an API to separate
> it from the rest of the application generally results in a cleaner,
> more maintainable system.
Agreed.
Thanks again for all the input.
--
Rob Browning
rver-proxy and gnc-client
ourselves.
> That will be the nature of the first implementation. I always design
> way farther than I implement, so that when the later stuff gets
> implemented it has already been planned for. At some point probably
> weeks from now, I will put much more ser
t be very efficient if stored in a
table with a bunch of other fixed length fields. In that situation,
perhaps we make a table of all the fixed length (the more
computational/indexable fields), and another table of blobs that are
indexed to the first table by GUID.
I think this is the kind of quest
es anyone have any
objections to this? If not, then unless someone else wants to do it,
I'll start working on this, and fixing up the file read code to
properly convert old "zero-price" splits -> split quotes immediately.
Speak now...
Thanks
--
Rob Browning <[EM
it; I'm human. If it's not, then I think it
> should be.
Well, we're using the standard md5sum code, and AFAIK, that's on very
solid mathematical footing. I don't have references handy ATM,
though. (Anyone?)
--
Rob Browning <[E
Dave Peticolas <[EMAIL PROTECTED]> writes:
> It should be splits -- I wasn't being very specific in that email.
No problem, just wanted to make sure I was thinking straight myself.
--
Rob Browning <[EMAIL PROTECTED]> PGP=E80E0D04F521A
Dave Peticolas <[EMAIL PROTECTED]> writes:
> Rob Browning is going the price database, so he will be posting a
> requirements/design doc soon.
Getting started on this now, so it's time to talk :>
> It may be that gnucash doesn't need to use the price db to store
>
- - - -> || (gnc_engine <-> ui)
(server) || <- - - - - -> || (gnc_engine <-> ui)
and we need to be thinking about what we *require* be done where.
I.e. does the DB just serve up raw records or do we require it to be
able to "do the math"
proxy that can handle the messy details of
storing arbitrary length strings (if that's even possible) in DBs that
don't handle them natively.
--
Rob Browning <[EMAIL PROTECTED]> PGP=E80E0D04F521A094 532B97F5D64E3930
___
gnucash-devel mai
cryptic passwords like
GPG/SSH etc.
--
Rob Browning <[EMAIL PROTECTED]> PGP=E80E0D04F521A094 532B97F5D64E3930
___
gnucash-devel mailing list
[EMAIL PROTECTED]
http://www.gnumatic.com/cgi-bin/mailman/listinfo/gnucash-devel
's copyright, etc.)
rules, we certainly can't expect them to enforce our licenses when the
shoe is on the other foot.
This is not a huge issue -- I don't think we have any problems that
won't be easy to solve to everyone's satisfaction, but it is important
to get t
t thinking too much about it) we
can use whatever encryption/authentication we want -- possibly even
just GPG encrypted chunks :>
--
Rob Browning <[EMAIL PROTECTED]> PGP=E80E0D04F521A094 532B97F5D64E3930
___
gnucash-devel mailing list
[EMAIL PROTECTED]
http://www.gnumatic.com/cgi-bin/mailman/listinfo/gnucash-devel
would cause Debian or other free
> software distributors to consider gnucash to be non-free in any
> way. We cannot and will not be cavalier about software licensing.
What Bill said ... twice.
--
Rob Browning <[EMAIL PROTECTED]> PGP=E80E0D04F
laces, etc.
At least this is why we've done what we've done up to now.
--
Rob Browning <[EMAIL PROTECTED]> PGP=E80E0D04F521A094 532B97F5D64E3930
___
gnucash-devel mailing list
[EMAIL PROTECTED]
http://www.gnumatic.com/cgi-bin/mailman/listinfo/gnucash-devel
x27;t
have RATIONAL_64 as a type. :>
--
Rob Browning <[EMAIL PROTECTED]> PGP=E80E0D04F521A094 532B97F5D64E3930
___
gnucash-devel mailing list
[EMAIL PROTECTED]
http://www.gnumatic.com/cgi-bin/mailman/listinfo/gnucash-devel
ertainly
> have their own table, so there will be an 'explicit' list of them.
And I've even thought about adding such a list to gnucash from time to
time...
--
Rob Browning <[EMAIL PROTECTED]> PGP=E80E0D04F521A094 532B97F5D64E3930
Dave Peticolas <[EMAIL PROTECTED]> writes:
> My best guess is that it stands for 'debit'.
I had always thought it meant d(elta)amount.
--
Rob Browning <[EMAIL PROTECTED]> PGP=E80E0D04F521A094 532B97F5D64E3930
___
gnucash-
f the thing you have, and value it's value.
Though quantity, taken by itself, is ambiguous, I'm not sure it's so
bad when within the context of a split. It would be hard to confuse
it with any of the other fields, and it's arguably better than
damount.
In any case, better names, w
h is
available via g-wrap-config. We already have a Makefile var with that
value that's determined in configure.in that we use in generating
gnucash.c.in. We just need to add it to this Makefile.am.
--
Rob Browning <[EMAIL PROTECTED]> PGP=E80E0D04F521A094 532B97F5D64E3930
[...]
> Hopefully I've given you enough pointers to get started.
Thanks very much. I glanced at the manpage briefly, and it's quite
interesting. I appreciate the pointer, and I'll definitely have to
spend a bit of time grokking it.
--
Rob Brownin
DBMS server, sharing access with other users and
> all that.
Well it looks like David Merrill may be interested in starting work on
the SQL stuff. We'd love to have your help/input if you're
interested.
Thanks
--
Rob Browning <[EMAIL PROTECTED]> PGP=E80E0D04F521A094 532B97F5D64E3930
___
gnucash-devel mailing list
[EMAIL PROTECTED]
http://www.gnumatic.com/cgi-bin/mailman/listinfo/gnucash-devel
; problem areas. Designing the database won't be hard (I've done many
> financial apps in my time!), and writing SQL will be pretty
> straightforward (the engine does all the work, really).
I agree.
> That's the idea, anyway. :-D
Thanks much for the help.
--
Rob Br
le as allowing the user to
use the DB they've already deployed, and as we move into the
small-business arena, allowing people to stick data in *their* DB will
probably become more critical. Though, even there, as long as we have
ways to interface with other DBs (i.e. batch push/pull) tha
gy out of it. PLUS I won't have to try to
> dust off all my pitiful math skills.
[...]
> rgmerk and others, what think ye?
Sounds like an excellent idea to me.
--
Rob Browning <[EMAIL PROTECTED]> PGP=E80E0D04F521A094 532B97F5D64E3930
interest, and I hope this is the kind of feedback
you were looking for.
I figure you might also want a little more info about how/where the DB
would probably tie in to the code, but I thought I'd let you digest
this first :>
--
Rob Browning <[EMAIL PROTECTED]> PGP=E80E0D04F521A094 5
Derek Atkins <[EMAIL PROTECTED]> writes:
> Rob Browning <[EMAIL PROTECTED]> writes:
>
> > The 50MB of RAM you're worried about is a *BUG*, and it needs to be
> > fixed. Other than that, and some performance work that seems fairly
>
> Is this a bug we
s I mentioned before, this might even mean getting rid of the
arbitrary hierarchical frames stuff.
--
Rob Browning <[EMAIL PROTECTED]> PGP=E80E0D04F521A094 532B97F5D64E3930
___
gnucash-devel mailing list
[EMAIL PROTECTED]
http://www.gnumatic.com/cgi-bin/mailman/listinfo/gnucash-devel
involve defining the SQL tables
we need. I don't see how that involves a "binary data format". I
must not understand what you mean.
--
Rob Browning <[EMAIL PROTECTED]> PGP=E80E0D04F521A094 532B97F5D64E3930
___
gnucash-devel mailing list
[EMAIL PROTECTED]
http://www.gnumatic.com/cgi-bin/mailman/listinfo/gnucash-devel
shed ways for handling this kind of thing, so we may be
able to just leverage those bits. Hard to tell before we really
consider the issues carefully...
--
Rob Browning <[EMAIL PROTECTED]> PGP=E80E0D04F521A094 532B97F5D64E3930
___
gnucash-
is a reasonable
> way to store large data sets. XML is a cool technology, but just
> because a technology is cool doesn't mean that it's the right tool for
> the job.
Of course you're welcome to, but why would you waste time on this
rather than trying to go forward
we get SQL
working, so I don't see the point in worrying about anything else...
--
Rob Browning <[EMAIL PROTECTED]> PGP=E80E0D04F521A094 532B97F5D64E3930
___
gnucash-devel mailing list
[EMAIL PROTECTED]
http://www.gnumatic.com/cgi-bin/mailman/listinfo/gnucash-devel
ction,
or even if they just change the date, the quote in the database can be
deleted/updated as appropriate, and these "transaction quotes" will
need to be distinguishable from "historical quotes" (right now those
would be quotes obtained via the online-mechanism) somehow.
Aga
rd to
re-inventing that wheel.
So, presuming we keep our current frame of mind, the XML format may
very well only be the actual file format, short term.
> In any case, what follows is my brief patch which I'd appreciate if
> it were put into the CVS. Thanks!
Thanks very much for the w
Dave Peticolas <[EMAIL PROTECTED]> writes:
> That is what GnomeMDI is supposed to do -- allow the user to choose
> between windows or tabbed panes.
Nice idea. Make everybody happy. We can't have that.
--
Rob Browning <[EMAIL PROTECTED]> PGP=E80E0D04F5
y rather my window manager be in charge of
things, but I'd be happy to be proven wrong. Also, there'd be
*nothing* wrong with allowing a pane-centric approach as an option, or
is that what Gnome-MDI's supposed to do?
--
Rob Browning <[EMAIL PROTECTED]> PGP=E80E0D04F521A094 5
elpful. I'd also love to have better
documentation of related guile low-level issues like what do
GH_DEFER/ALLOW_INTS really do, and when do you need to use them?
Also perhaps a discussion of the changes that had to be made to Gtk+
with a commentary on why they helped would be really informati
dumped into a
designated pane in your custom window. This would, of course, allow
all manner of stupid pet tricks for those willing to brave the schemey
waters.
--
Rob Browning <[EMAIL PROTECTED]> PGP=E80E0D04F521A094 532B97F5D64E3930
___
gnucash-
add something like a much clearer
"brokerage" window, etc.
Hopefully you get the idea.
> You're absolutely right, though - you don't just blindly copy the
> features of your competitor's product. That's what got us commercial
> bloatwa
that
stuff available from guile, and then I think about how much less
manpower we have to implement it, and *that* leads me to think about
g-wrap (or something similar) to help automate the process, and
automatically maintain the result...
Don't get me wrong. I'd love a solution that
ts either way. To a
substantial extent, I'm not the best person to evaluate this argument,
since I have little or no experience with CORBA, though I've done
plenty of DO/RPC related work.
Thanks
--
Rob Browning <[EMAIL PROTECTED]> PGP=E80E0D04F521A094 532B97F5D64E3930
_
Derek Atkins <[EMAIL PROTECTED]> writes:
> For the record, QIF importing no longer crashes, and I can
> successfully build the GnuCash CVS Mainline.
Great.
--
Rob Browning <[EMAIL PROTECTED]> PGP=E80E0D04F521A094 532B97F5D64E3930
___
access struct members directly, you
have to write a set of helper functions that are then themselves
g-wrappable. This has it's drawbacks, but it also has the fairly
substantial advantage of keeping the semantics and implementation of
g-wrap simpler than they would be otherwise.
As a f
(in-module module)
(c-name c-typedef-name)
;; return-type and parameters as for (function)
)
Ex:
(user-function PrintFunc
(in-module (Gtk))
(parameter in (type-and-name gpointer func_data))
(parameter in (type-and-name gchar* str)))
===
(typedef new-name
(in-module m
I wanted to get this one out (which will hopefully fix the RPM
problems) before I dive into integrating the new enum support from
Robert.
2000-11-12 Rob Browning <[EMAIL PROTECTED]>
* configure.in: new version 0.9.12.
* rpm/spec.in: fix some bugs I introduced with a
directory -- RPM can do that on its own
> +- Properly build both g-wrap and g-wrap-devel (info file into -devel)
> +- currently only one info file
Actually, this mostly answers my above questions, though I still have
only a little context for what's going on. In any case, I
This version should work with Bill's new patch (adds long and
long-long). It should also generate a new -devel RPM, though I can't
test that. Please let me know if you find mistakes.
ftp.gnucash.org:/pub/g-wrap/source/g-wrap-0.9.11.tar.gz
2000-11-08 Rob Browning <[EM
ve to deal with your enum patch, but I'll do that while
working on this.
Thanks
--
Rob Browning <[EMAIL PROTECTED]> PGP=E80E0D04F521A094 532B97F5D64E3930
___
gnucash-devel mailing list
[EMAIL PROTECTED]
http://www.gnumatic.com/cgi-bin/mailman/listinfo/gnucash-devel
ray-destroy g-array)
result)
or, if we added a cleanup-arg? argument to the converter instead:
(let* ((acclist (list acct-1 acct-2 acct-3))
(g-array (frob-accounts (list->glib-glist 'Account* acclist
(glib-garray-
Available at ftp.gnucash.org/pub/g-wrap/source:
2000-11-06 Rob Browning <[EMAIL PROTECTED]>
* release new version 0.9.10.
* guile/guile-types.scm (const-string): fix bug in scm->C conversion.
2000-11-05 Rob Browning <[EMAIL PROTECTED]>
r CVS it appears that page splitting has been improved in more
> recent code. I'll have another play with it now.
Great.
--
Rob Browning <[EMAIL PROTECTED]> PGP=E80E0D04F521A094 532B97F5D64E3930
___
gnucash-devel mailing list
[EMAIL
o the crash you were mailing me
> about.
I still wonder if we have 'cleanup everywhere we're supposed to.
Also, I need to add a 'const option so we can get rid of those silly
compiler warnings...
--
Rob Browning <[EMAIL PROTECTED]> PGP=E80E0D04F521A094 532B97F5D64E3
#x27;s going to be difficult to generate
reports that know exactly what really happened...
--
Rob Browning <[EMAIL PROTECTED]> PGP=E80E0D04F521A094 532B97F5D64E3930
___
gnucash-devel mailing list
[EMAIL PROTECTED]
http://www.gnumatic.com/cgi-bin/mailman/listinfo/gnucash-devel
1 - 100 of 818 matches
Mail list logo