On Thu, 12 Dec 2013, Thomas Chust wrote:
On 2013-12-12 17:53, Jan Wedekind wrote:
[...]
However when doing embedding there is no single 'run' method to
pass to 'scheme_main_setup'. Is there another simple way to do that?
[...]
Hello,
it is probably a bad idea to use any setup that doesn't ha
On 2013-12-12 17:53, Jan Wedekind wrote:
> [...]
> However when doing embedding there is no single 'run' method to
> pass to 'scheme_main_setup'. Is there another simple way to do that?
> [...]
Hello,
it is probably a bad idea to use any setup that doesn't have a single
"run" method! If you reent
Hi,
I am trying to get Racket embedded in Python. The SchemePy backend [1]
segfaults when I run it.
I managed to get the embedding example from the documentation running [2].
However when doing embedding there is no single 'run' method to pass to
'scheme_main_setup'. Is there another simple way
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I think this is only tangential to the discussion, but I have found
these series of articles very enlightening on the subject of
documentation writing:
http://jacobian.org/writing/great-documentation/
On 08/06/2011 05:17 PM, Danny Yoo wrote:
> On the
On Mon, Aug 8, 2011 at 7:26 AM, Deren Dohoda wrote:
> I'm not saying that the docs are perfect, but not-being-another-wiki is, to
> me, a feature.
The good thing about Jens' idea is that it is not a wiki; users are
not editing content, rather only commenting.
Reminds me of the Real World Haskell
I'm not saying that the docs are perfect, but not-being-another-wiki is, to
me, a feature.
Deren
On Aug 7, 2011 8:05 AM, "Jens Axel Søgaard" wrote:
> User contributions are what is needed to improve the documentation.
>
> 1. It should be *easy* to report spelling errors and/or complaints
> about
On Sun, Aug 7, 2011 at 8:01 AM, Neil Van Dyke wrote:
> * After a little thought, I've decided that I don't want random people's
> comments or discussion in my Racket manuals. A simple HTML "a" element
> feedback link on each page would be OK with me (but I'm not the person who
> would have to spe
Jens Axel Søgaard wrote at 08/07/2011 08:03 AM:
2. There should be a discussion section on the bottom of each page.
Solving 2) is easier than one might think. Disqus is a site that
hosts discussion threads. A thread is is embedded into a page
with a piece of with JavaScript. When the page is
User contributions are what is needed to improve the documentation.
1. It should be *easy* to report spelling errors and/or complaints
about a particular page.
2. There should be a discussion section on the bottom of each page.
Solving 2) is easier than one might think. Disqus i
On the Reddit thread regarding the 5.1.2 release, one of the posters
mentioned that they wanted to use the FFI, but couldn't decipher the
documentation. For someone who doesn't already know how to use the FFI, the
current docs are insuffucient. Is this problem on the radar?
__
10 matches
Mail list logo
