unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: Max Polk <ux9i003@triad.rr.com>
Subject: Newbie - desigining apps
Date: Thu, 07 Oct 2004 21:12:45 -0400	[thread overview]
Message-ID: <4165E98D.3090304@triad.rr.com> (raw)

I'm intending on moving forward with free software development and 
understand Guile is the official extensibility language of GNU, and that 
I ought to support it in my application.  Makes sense, fine.

Now for this to be useful at all, my application has to be designed from 
the beginning to accommodate external control.  That's a big thing, 
writing an app that controls itself by traditional design, versus 
writing an app that is controlled from the outside.

Have others found that supporting Guile in an application means 
rethinking how it runs at it's very core?  For example, instead of 
writing use cases and designing from that, now I have a use case like 
"let the user call any higher-level function".

Even worse, what about object orientation?  Is it possible to let the 
user create, then assemble together, use, then destroy various program 
objects, all from Guile?  And how is even that done, returning C++ 
objects back to Guile -- I assume you would have to return a handle 
representing the internal program object, then add some management layer 
that maps these handles to internal objects.

WOW!  This is a radically new approach to software development!

Can someone can start me off on the right foot?



_______________________________________________
Guile-user mailing list
Guile-user@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-user


             reply	other threads:[~2004-10-08  1:12 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-08  1:12 Max Polk [this message]
2004-10-08  2:49 ` Newbie - desigining apps Julian Graham
2004-10-08 18:43 ` Anthony Kozar
2004-10-09 21:47 ` Neil Jerram

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/guile/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4165E98D.3090304@triad.rr.com \
    --to=ux9i003@triad.rr.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).