On 06 Apr 2000 20:30:27 CDT, the world broke into rejoicing as
Rob Browning <[EMAIL PROTECTED]> said:
> Dave Peticolas <[EMAIL PROTECTED]> writes:
>
> > Right now, reports are represented in guile as a vector containing a
> > version, name, option generator, and renderer. Some things I'd like
> > to add in the future include a help text generator, and
> > report-specific toolbar buttons and menu items. To eliminate the
> > need to change each report every time we add a new feature, I'd like
> > to move the report representation to the "key->value" style scheme
> > closure.
>
> Do you mean the SICP style object stuff? If so, then I'm just fine
> with that - it's a really nice model. I think my only remaining
> concern with that approach was performance, and if that's not an
> issue, then it's not an issue :>
At least in this case, speed should be an utter non-issue.
All this is for is the representation of the structure that contains
the metadata about the report. Its name, the option function, the
renderer function.
For any given invocation of a report, this stuff gets looked at *once,*
which means that it's the 2ms of "overhead" at the start. Make it a
50 times slower and that's 100ms, which is a barely perceptible period
of time.
More likely, using a Guile record to represent this would make *more*
sense, and would allow it to become marginally *faster.* Make it twice
as fast, and 2ms falls to 1ms. Completely imperceptible.
--
Did you hear about the Buddhist who refused his dentist's novocaine
during root canal work? He wanted to transcend dental medication.
[EMAIL PROTECTED] - <http://www.hex.net/~cbbrowne/lsf.html>
--
Gnucash Developer's List
To unsubscribe send empty email to: [EMAIL PROTECTED]
