On 24/09/13 23:28, Neil Van Dyke wrote:
Anyway, I'm thinking of starting a side business of developing
general-purpose Racket packages on demand -- modules that satisfy all
clients' requirements and are incidentally open-sourced. Perhaps with
some discount over normal rates in consideration of
On 09/09/13 07:19, Stephen Chang wrote:
Konrad's exactly right. Your filtered-nums blows up because you named
the stream and then traversed the entire thing. In general, if you
hang onto the head of the stream while traversing then the GC can't
collect anything because since you have a pointer to
Hello,
I'm trying to understand how memory is allocated and collected when
working with streams.
I recently asked a question about how to limit memory when using streams
on Stackoverflow
and got two good answers:
http://stackoverflow.com/questions/18629188/how-to-limit-memory-use-when-using-a-
On 08/31/13 13:46, Matthew Flatt wrote:
I've added license information to all of the packages in the main
distribution.
That was quick, I hope it wasn't too much of an ordeal to go through them.
Lorry
Racket Users list:
http://lists.racket-lang.org/users
Hello,
I have been trawling through the packages at:
http://pkg.racket-lang.org
And have found that very few of the packages have any licensing information
and are effectively proprietary software, despite what their authors may
have
intended. I can therefore study them, but not use them
On 29/08/13 20:14, Matthew Flatt wrote:
Package versions are intended to be like semver, but they differ
syntactically because
* the major number should be part of the package name, and
* the major number "1" is written "".
So, write xdgbasedir version 0.1.0 as package name "xdgbasedir0"
On 28/08/13 18:21, Greg Hendershott wrote:
To the extent this is relying on package providers to do the right
thing -- relying somewhat on convention and best practices:
I think now would be a great time for a blog post (and maybe a
RacketCon presentation) stating the best practices.
Including
On 28/08/13 16:33, Matthias Felleisen wrote:
On Aug 28, 2013, at 1:51 AM, Lawrence Woodman wrote:
I have used: Ruby, Tcl, Shared C Libraries under Linux, Various Linux Distros,
etc. All of these either
started without distinct version control, or started with a single version
package model
On 28/08/13 12:27, Matthew Flatt wrote:
At Wed, 28 Aug 2013 09:45:23 +0200, Konrad Hinsen wrote:
Lawrence Woodman writes:
> I have seen problems with version control crop up for so long and
> so often that I can't see why people think Racket and it's
> third-part
On 08/27/13 13:55, Matthew Flatt wrote:
For what it's worth, I think you're worried about problems that will
have simple solutions in practice. For example, I don't think you
should rely a package whose author isn't invested enough to at least
put it on GitHub or otherwise archive old versions.
On 08/27/13 12:34, Sam Tobin-Hochstadt wrote:
I think the right approach to running multiple Racket applications at
once that all rely on packages that might conflict is to use multiple
installations of Racket. Then you can install packages
installation-wide and not have them conflict.
This
On 08/26/13 14:27, Matthew Flatt wrote:
A _package name_ is something like "mischief", which you use for
installing and declaring dependencies. A _package implementation_ is
something that you download from, say,
https://github.com/carl-eastlund/mischief/tarball/
fe7119517a4dcd3f5c50973
On 08/26/13 13:36, Jay McCarthy wrote:
On Mon, Aug 26, 2013 at 12:57 AM, Lawrence Woodman
wrote:
I have been really impressed with Racket after using it for a month, but am
worried about the move away from a central repository for storing each
version of a package. I can see the advantage and
On 26/08/13 10:32, Jens Axel Søgaard wrote:
> One easy improvement, when using github, is to allow/ensure package
owners point to a
> specific release/tag .zip file and not worry about the checksum as
nothing is going to
> change until a new release/tag is specified.
It is not as easy as it se
On 26/08/13 08:09, Grant Rettke wrote:
On Mon, Aug 26, 2013 at 2:57 PM, Lawrence Woodman
wrote:
This is such a cause for concern to me because I'm developing an open source
application to be used commercially and need to be able to maintain a
certain level of stability. I could just
Hello,
I have been really impressed with Racket after using it for a month, but am
worried about the move away from a central repository for storing each
version of a package. I can see the advantage and simplicity of the new
system, but worry that relying on package creators to manage their pac
ase a package whose structure needs v5.90.x but which
doesn't require v5.90.x to run the code it contains. I'll therefore
revert to the
previous structure.
Thanks for your help
Lorry
At Fri, 16 Aug 2013 07:27:02 +0100, Lawrence Woodman wrote:
Hello,
In a previous thread about docum
On 13/08/13 18:15, Lawrence Woodman wrote:
On 13/08/13 13:44, Matthew Flatt wrote:
At Tue, 13 Aug 2013 11:15:10 +0100, Lawrence Woodman wrote:
However, despite being able to render the docs with scribble, I still
can't render with
raco setup/ raco pkg install. When I try, I get the foll
Hello,
In a previous thread about documentation, I was given the advice
that there was no need to have a collection subdirectory in packages
with a single collection.
I therefore went from:
. Package root
info.rktPackage info.rkt
xdgbasedir/
On 13/08/13 13:44, Matthew Flatt wrote:
At Tue, 13 Aug 2013 11:15:10 +0100, Lawrence Woodman wrote:
However, despite being able to render the docs with scribble, I still
can't render with
raco setup/ raco pkg install. When I try, I get the following error:
raco setup: --- bui
On 13/08/13 13:57, Jay McCarthy wrote:
On Tue, Aug 13, 2013 at 3:47 AM, Lawrence Woodman
wrote:
On 12/08/13 15:08, Jay McCarthy wrote:
Packages do not have documentation, but collections inside of packages
may have documentation.
However, if you have a single collection package, then the
Hello all,
Thanks for the suggestions and for directing me to raco docs, which I
hadn't come
across previously.
I have been able to render the scribble files and push them to github
pages. I then
pointed to this from the README file and set the project's homepage link
to also
point here. T
On 12/08/13 15:08, Jay McCarthy wrote:
Packages do not have documentation, but collections inside of packages
may have documentation.
However, if you have a single collection package, then the info file
is for both the package and the collection metadata.
In my package I have the following dir
the directory the package was installed in and find
the doc/
directory?
Thanks
Lawrence Woodman
--
vLife Systems Ltd
Registered Office: The Meridian, 4 Copthall House, Station Square, Coventry,
CV1 2FL
Registered in England and Wales No. 06477649
http://vlifesystems.com
On 08/06/13 19:07, Jay McCarthy wrote:
If you decide to create a Racket package (rather than a Planet
package) for your software and host it on Github, then only files you
explicitly add to the repository will be included in the package. More
details can be found here:
http://docs.racket-lang.or
On 08/06/13 16:32, Neil Van Dyke wrote:
Lawrence Woodman wrote at 08/06/2013 11:15 AM:
So I now know what will be in the archives, but is there anyway of
restricting
what goes into a package?
If you use McFly to build your PLaneT archive file, there is a feature
for this. The "mcfly-
Hello,
I'm having problems omitting files when creating packages with:
raco planet create .
running from the root of the package directory.
As you can see from the mess I have made of:
http://planet.racket-lang.org/package-source/lwoodman/xdgbasedir.plt/1/0/
Which contains my swap files. I
uld
find the tests for prefix-out and contract-out.
bfn
Lorry
Carl Eastlund
On Sat, Aug 3, 2013 at 2:51 AM, Lawrence Woodman
mailto:lwood...@vlifesystems.com>> wrote:
Hello,
I would like to prefix the functions that I want to export from a
module and
provide a con
Hello,
I would like to prefix the functions that I want to export from a module and
provide a contract for each exported function. I tried the following style:
(provide
(prefix-out mymodule-
(contract-out
[func-a (-> string? any)]
[func-b (->
29 matches
Mail list logo
