Re: Ann: SWI-Prolog 6.5.1

> >	1. with all libraries on a common repository there is less time wasted in porting features backwards and forwards,
> >	   This would have a beneficial effect on both Swi and Yap developers' time.
> 
> Yes and no. Things that are now simple quick decisions with a few
> changes in a couple of places need to go through defining proper
> interfaces and considering the consequences on two systems. The main
> advantage is that the libraries are likely to get better, not that it
> takes less time.
> 
        
	what would take less time is propagating changes from one system to the other as
         a much larger set (dare i say all?) of libraries will be in the common repository. 
	There will be no overhead for importing things. 
	Not only for libraries but also for packages.
	Currently i suspect that 95-99% of the packs code is compatible with Yap.
	But as it currently stands someone needs to go in the sources and squeeze the last ounce
	of incompatibility out manually.
	
	I think the main technical difficulty here is Yap threads.


> >             Would a PhD position working on that make sense?
> 
> I doubt anyone can get a PhD from restructuring interfaces and setting up
> git repos ...  That is a serious disadvantage of hosting these systems in
> an academic setting.  On the one hand, the universities provide an
> inspiring and innovative environment to work in.  On the other hand,
> many tasks involved in running these projects that make them profitable
> to the community do not fit well with the way universities work.
> 
	I think there is enough academic meat on the implementation of Prolog
	with emphasis on wrapping the engine in a compatibility cocoon. 
	Issues such like threads will be extra bonus in that you have done a brilliant work
	but not necessarily published enough on that. if you add integration with web-services
	and comparative  evaluation of the SWI vs Yap implementation
        you possibly have enough material for more than one phd

> >             Integrate the mailing lists as a first step ?
> 
> I'm not against that.
> 
> >	2. a closer integration will increase the confidence of people picking up either of the two systems for
> >	   research and commercial uses
> 
> Agree
> 
> >	3. can work as a de-facto framework and vehicle for standarisation of non-core features.
> 
> Probably also true.
> 
> >         4. if the work is successful in creating an N-point API/plug-n-play-framework it might well lead to new Prolog systems
> 
> Bart always says we should have less :-)
> 
	I think we should have had less decades ago. 
	but, new systems that _are_ compatible with a core set of libraries are a very different proposition.
	_If_ here would be any, it would then be extremely easy to also import ideas/code from these back to SWI/Yap.
	I don't think we should be planning for new systems, but i note that a well worked out framework
	would make these more likely.

> >         5.  it will be a good excuse to clear up pending issues that have low priority, such as independence from XPCE code
> 
> I don't know whether that is an aim. Maybe on the long run. For now, you
> need GUI tools and XPCE might look ugly, but it is lightweight, fast,
> portable and allows for quick development from Prolog.  Except for using
> web technology, I see no clear replacement.
> 
	I was very careful in choosing my words. I said "independence" and not "scrapping". 
	As far as I understand it, there are low level dependencies of the main system to the XPCE libraries.
	For this discussion, XPCE is not the issue, the dependencies are. 
	Whatever should be served from within the core should be in the main system.

> >
> > Let me take the opportunity though, to congratulate yourself and Vitor for having brought the systems really close.
> > Your great work means that many of us (users) can now routinely use the same code on both Prologs.
> 
> Thanks for the kind words.  I've had several discussions about where to
> head for with SWI-Prolog.  I still have little clue.
> 
> 	Cheers --- Jan

	Food for thought for the holidays.

Nicos

ps. Many thanks for the instructions for running SWI on the Android you posted on the list.
I still havn't dared or found the time to root my newly arrived super-spec tablet.