The main point I think about guile, fluids and smobs is that fluids allow safely sharing variable between threads. Since guile is multithreading this can be critical.
If you print to stdout from both within libgeda and from within a scheme script you will see that there is no guarenty that you can predict the order of the print statements apearing. I am curious about how the data is protected within a fluid? semiphores? Steve Meier On Thu, 2008-01-10 at 15:29 +0200, Bernd Jendrissek wrote: > On Jan 9, 2008 8:25 PM, Peter TB Brett <[EMAIL PROTECTED]> wrote: > > Please review and comment. Any proposed changes as diffs against the .txt > > file, preferably. [1] > > How much of this fluidity is necessary due only to the fact that there > ARE global variables in libgeda / gschem / others? I would rather > spend some effort at eliminating these atrocities against humanity > than at making access to them from guile more safe. > > I have no further comments on your proposal as I don't really even > understand what a fluid is. I'll try to re-parse later. > > FWIW, I have already implemented a SMOB for libgeda's TOPLEVEL. I > can't give you a commit id now, but it's somewhere inside my geda fork > on repo.or.cz. Should be greppable from the commit messages on branch > berndj/abstract-symbols. > > > _______________________________________________ > geda-dev mailing list > [email protected] > http://www.seul.org/cgi-bin/mailman/listinfo/geda-dev _______________________________________________ geda-dev mailing list [email protected] http://www.seul.org/cgi-bin/mailman/listinfo/geda-dev
