Old Logtalk discussion forums - read-only

See also this thread: viewtopic.php?f=15&t=62

Perhaps world_state isn't an object but some other entity such as a category. You need to provide more information.

Cheers,
Parker

Compile-time aliases sound good to me. I can't think of any (sensible) situation where it would be useful to change the implementation of an ADT at run-time; or any other application of run-time object aliases for that matter.

The downside of the uses/2 directive is that you have to track which predicates are being used.

I think object aliases are an elegant way to swap between ADT implementations, but I also understand that you don't want to have too many directives.

Thanks for considering it, Paulo.

Parker

Hi Paulo, I did say it wasn't urgent, but wow you've already got an initial implementation! Hmm... maybe I should try some reverse psychology for the features I really want. I'll be sending you a list of things I really really don't want very soon. :lol: Object aliases within an entity make sense to...

Here is a quick idea, not at all urgent. I recently used two tree data-structure implementations (rbtree and bintree) that both satisfy the dictionaryp protocol. When swapping from one to the other, each call had to be renamed: e.g. rbtree::lookup(Point, Value, ClassificationsTree) had to be renamed...

Hi Paulo, There is an application in SWI's plunit that does coverage analysis which is extremely useful to see if any code has been missed by unit testing. For details see http://www.swi-prolog.org/pldoc/doc_for?object=section%282%2c%20%278%27%2c%20swi%28%27%2fdoc%2fpackages%2fplunit.html%27%29%29 I...

If Logtalk's reflection capabilities are sufficient, then that is already a good start. But bear in mind there may be a number of potential uses that could benefit from a re-usable codebase. the dependency checker (as already mentioned) the loader generator (automatically find dependencies so that f...

Don't get me wrong, I'm not trying to persuade you to bump re-writing Logtalk up your priority list, I'm sure you have plenty of other more important things to do. I want to discuss the pros/cons of writing Logtalk in Prolog or Logtalk. So just see this as food for thought. Writing the Logtalk compi...

Please don't take it badly Paulo, it's only intended as constructive criticism. :-) Why is Logtalk not written in Logtalk? The Logtalk compiler is written in Prolog and is about 16,000 lines of source. It is not "programming in the small", so why isn't Logtalk written in Logtalk? There's a principle...

New ticket on trac: http://trac.logtalk.org/ticket/35

Existing cross-referencers I have seen include a parser and a list of built-ins. But this is already implemented in the logtalk compiler, so would it be sensible to use that rather than start afresh?

This has changed slightly. See http://logtalk.org/manuals/userman/inst ... g_settings

Parker

joerg wrote: (0) There is no compiler-independent way to create standalone executables from Logalk porgrams.

This is interesting. A way of creating an executable that works for all compilers that support it would be a very good development.

Parker

Hi Paulo, Could you advise me on how to implement Richard O'Keefe's retract_exactly/1? My understanding is that it is still not possible in Logtalk without reaching through to the backend Prolog. retract_exactly(Clause) :- ( nonvar(Clause) -> Clause = :-(Head,Body) ; Head = Clause, Body = true ), mu...

I also find it a bit strange to have to edit a config file to change what are essentially project-specific parameters. You don't need to edit a config file to change project-specific parameters, only to change default parameter values. The natural place to change such settings (in my opinion) would...