Re: GSoC 2017: we have a slot

Compro, try to follow the items outlined in you proposal.

31-May to 11-Jun: Writing the lisp code to make simple threads and find out
where the hash table hits a corner case. Get ready with enough tests
09-Jun to 30-Jun: Write/Improve functions/macros to handle the thread
safety in the hash tables.

The preferred communication channel is this mailing list - feel free to
post code here.

At that stage I would expect to see tests hitting the problem and
ideas/plans/code trying to resolve the observed issues.



On Thu, Jun 15, 2017 at 11:00 PM, Sam Steingold <[email protected]> wrote:

> > * Sam Steingold <[email protected]> [2017-04-26 10:38:10 -0400]:
> >
> > I am not sure what you mean by "joining us", but the next critical date
> > on the timeline is June 26.
> > By this date you need to have most of the work either done or in a state
> > where we will be confident that you _will_ finish it on time.
>
> Looks like this date is closer than it appeared just a few weeks ago.
> In 10 days we will have to see most of the work done.
>
> So far I have not seen any code.
>
> --
> Sam Steingold (http://sds.podval.org/) on darwin Ns 10.3.1504
> http://steingoldpsychology.com http://www.childpsy.net http://memri.org
> http://americancensorship.org http://www.dhimmitude.org
> Beliefs divide, doubts unite.
>

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot

_______________________________________________
clisp-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/clisp-devel