Logtalk is an object-oriented logic programming language that can use most Prolog implementations as a back-end compiler. As a multi-paradigm language, it includes support for both prototypes and classes, protocols, component-based programming through category-based composition, event-driven programming, and multi-threading programming. hr / strongLicense:/strong Artistic License hr / strongChanges:/strongbr / This release improves support for using Prolog module libraries, provides several examples of using constraints within objects, optimizes multi-threading performance, adds support for using the ensure_loaded/1 and the set_prolog_flag/2 directives in source files, corrects several bugs, and updates support for the ECLiPSe, GNU Prolog, and SWI-Prolog compilers. pa href="http://feedads.googleadservices.com/~a/5iD3Xj7-4R01rCa06FzTW6Sp8SQ/a"img src="http://feedads.googleadservices.com/~a/5iD3Xj7-4R01rCa06FzTW6Sp8SQ/i" border="0" ismap="true"/img/a/pimg src="http://feedproxy.google.com/~r/freshmeat/feeds/fm-releases-unix/~4/soUwrpLMyXw" height="1" width="1"/

Logtalk is an object-oriented logic programming language that can use most Prolog implementations as a back-end compiler. As a multi-paradigm language, it includes support for both prototypes and classes, protocols, component-based programming through category-based composition, event-driven programming, and multi-threading programming. hr / strongLicense:/strong Artistic License hr / strongChanges:/strongbr / This release improves support for using Prolog module libraries, provides several examples of using constraints within objects, optimizes multi-threading performance, adds support for using the ensure_loaded/1 and the set_prolog_flag/2 directives in source files, corrects several bugs, and updates support for the ECLiPSe, GNU Prolog, and SWI-Prolog compilers. pa href="http://feedads.googleadservices.com/~a/9Cmj8oBzaMipR-0dsiDqgqSju3o/a"img src="http://feedads.googleadservices.com/~a/9Cmj8oBzaMipR-0dsiDqgqSju3o/i" border="0" ismap="true"/img/a/pimg src="http://feedproxy.google.com/~r/freshmeat/feeds/fm-releases-global/~4/soUwrpLMyXw" height="1" width="1"/

Logtalk 2.33.1Logtalk is an object-oriented logic programming language that can use most Prolog implementations as a back-end compiler.

As a multi-paradigm language, Logtalk includes support for both prototypes and classes, protocols, component-based programming through category-based composition, event-driven programming, and multi-threading programming.
WHAT'S NEWVersion 2.33.1:

• Added a syntax construct for easy access to parametric object proxies represented as Prolog facts when sending a message ({Proxy}::Message). Updated the "proxies" example to illustrate this new functionality.
• Improved the Logtalk built-in debugger to print clause numbers for static predicates at the unification ports ("fact" and "rule").
• Modified the built-in methods create_category/4, create_object/4 and create_protocol/3 to accept a variable as the first argument, which will be instantiated to the identifier generated for the new entity.
• Modified the database built-in methods to allow initialization of static predicates for dynamic objects when the predicates are declared in "this". These changes simplify the initialization of dynamic objects when writing constructors. The dynamic objects must be descendants of "this".
• Fixed a bug in the Logtalk compiler that would result in failure to restore the operator table in case of compilation error.
• Removed support for the deprecated mutex_create/1 Prolog built-in predicate.
• Updated the XSB config file by switching off the use of multifile/1 directives when compiling Logtalk source files as a workaround for know bugs in the implementation of this directive for dynamic predicates.
• Updated the ECLiPSe 6.0 config files in order to switch on the use of multifile/1 directives.
• Update the CxProlog config file to work with and require version 0.97.2.
• Updated the Windows installer to warn the user when it fails to detect the installation of the selected Prolog compilers. Fixed a bug where the creation of the K-Prolog integration shortcut could fail when performing a custom installation. Fixed a bug in detecting a CxProlog installation.
• Added a library for descriptive statistics. For details, see the file "library/statistics.notes".
• Added a new library object, "pairs", defining predicates over lists of pairs (key-value terms).
• Added a new library object, "gensym", defining predicates for generating unique atoms (object protocol based on the "gensym" module of SWI-Prolog).
• Added a predicate partition/4 to the library entities "metap" and "meta".
• Added predicates plus/3 and succ/2 to the library object "integer".
• Added predicates is_ascii/1, is_white_space/1, is_quote/1, is_period/1, is_punctation/1, and parenthesis/2 to the library entities "characterp" and "character".
• Modified the implementation of the predicate product/2 in the library object "numberlist" to fail for empty lists.
• Added an example, "people", illustrating a simple implementation solution for object constructors.
• Improved "metainterpreters" example.
• Improved performance of the object initialization and release predicates defined in the category "initialization" of the "roots" example.

REQUIREMENTSMac OS X 10.3.9 or later, compatible Prolog compiler.
DEVELOPERPaulo Moura
DOWNLOADS1242
DOWNLOAD NOW (631 K)
More information

H3The Useless Introduction You Used To :)/H3 PThis post has taken so long to be started in writing. I’ve been busy with many events in my life lately. Suffering from frequent limited internet access lately, and, all this moving between companies thing has been eating me. And yes, I admit, I' have been as tired and more honestly lazy as you expected me to be!/P PHey, there’s a little warning. This post is not exactly for my usual audience. I’m sorry, but introducing A title=Wikipedia target=_blank href="http://en.wikipedia.org/wiki/Domain-driven_design" mce_href="http://en.wikipedia.org/wiki/Domain-driven_design"Domain Driven Design/A is not one of the goals for this post. There’re many interesting resources and books (even FREE: A target=_blank href="http://weblogs.asp.net/controlpanel/blogs/Domain%20Driven%20Design%20Quickly"InfoQ, Domain Driven Design Quickly/A) on the topic. STRONGHowever, if you leave me a comment telling me to make a write-up on the topic, of course I will :) :)./STRONG/P POne more thing. Another reason I’m working on this is that I’m preparing for an internal session here in Raya about Practical Lightweight Domain Driven Design. This session is truly internal yet. It should be recorded though but I’m not sure whether it’ll be possible to publish the videos (Yeah, I will see how we can have our public sessions of possible sure!). STRONGIf you have a user group and would like me to give this session in a group meeting, I’ll be glad to do./STRONG/P H3Introduction Still: The Messages, The ORM/H3 PThis post was originally A target=_blank href="http://tech.groups.yahoo.com/group/altdotnet/message/16324" mce_href="http://tech.groups.yahoo.com/group/altdotnet/message/16324"a couple of messages I’ve sent recently/A to the A target=_blank href="http://tech.groups.yahoo.com/group/altdotnet/" mce_href="http://tech.groups.yahoo.com/group/altdotnet/"ALT.NET Yahoo Group/A. In which I discuss using Domain Driven Design with an ORM, more specifically, my favorite ORM, A target=_blank href="http://www.llblgen.com/" mce_href="http://www.llblgen.com/"LLBLGen/A./P PQuoting from the first message:/P BLOCKQUOTE PEMFor now, we're going towards LLBLGen Pro 2.6 for DAL generation and such (using Self-Serving mode probably). Yes, we're going for database first design, and not using NHibrernate. I'm hoping that we can keep those two issues for other threads :). /EM/P PEMRight now, I'm going for other Domain Driven practices. I want to make sure using POCO classes is worth it, and then see how to have those in LLBLGen (which -LLBLGen main template- is in its internal not much different design than Active Record, which in many times is handy, it's VERY rare t change DAL when one fits different DB providers with good performance), and what are common patterns to do Domain Driven Design at all when having LLBLGen as DAL (if it makes any difference - again: and if effort to make it encapsulated enough to make no difference is worth it)./EM/P/BLOCKQUOTE PMaking this choice alone is worth its own article. Maybe should title it “In Search For The Perfect ORM” as well :-D./P PSTRONGUUPDATE:/U/STRONG Fransnbsp;Bouma has A href="http://weblogs.asp.net/fbouma/archive/2004/10/09/240225.aspx" mce_href="http://weblogs.asp.net/fbouma/archive/2004/10/09/240225.aspx"a nice write-up about what is an ORM and different types on an ORM/A. It's quite old (2004), but the concepts themselves are still valid./P PMy original question was:/P BLOCKQUOTE PEMSo, is anybody here doing DDD and uses LLBLGen as DAL generator ?How does the experience look like ? What are common practices across all projects and what have been pitfalls ? etc... These are the kinds of questions I'd love to see somebody here with something to share about./EM/P/BLOCKQUOTE H3Domain Driven Design At Work/H3 PThis is not really an LLBLGen issue. It is questioning the Domain Driven Design productivity itself. I like DDD. I see it as the natural next step after 3-tier deisgn. This whole separation of concerns, models, repositories, factories, infrastructure, and services paradigm just fits my mentality and view of how the world looks like. However, not all the practices in DDD are similar in terms of return of investment, the customer business value that Agile emphasizes. The trick is to know which are and which aren’t, and how to do the balance./P PIn the second message, I go through an example of typical usage for DDD that has tried just a little bit to be lightweight in some areas but not others, and my own overview about what needs improvement:/P P mce_keep="true"nbsp;/P BLOCKQUOTE DIVEMI've been on a project that leverages DDD once before myself. The project has been frozen for a while for other priorities, etc...Maybe I start with my own take on the subject!!/EM/DIV DIVEM/EMnbsp;/DIV DIVEMWe've been using the "Adapter" model. I thought it was for seeking some sort of more control/flexibility. Reading Fran Bouma’s blog (/EMA target=_blank href="http://weblogs.asp.net/fbouma" mce_href="http://weblogs.asp.net/fbouma"EMhttp://weblogs.asp.net/fbouma/EM/AWBR/WBREM, the creator of LLBLGen), I see how he's so much of an "Entity Design" guy. Well, makes sense, he owns the best entity design I've seen so far having considered EF and CSLA./EM/DIV DIVEMClearly he sees the "Self Servicing" as the core for entity design rather than model design. You know, the "entity.Save();" style. This makes me have two thoughts at a time actually. 1- That "Adapter" model is the right choice for DDD (I'll get to that just below), 2- That maybe DDD fully is not what I really want (the entity Self Servicing style is so powerful. It has saved my day so many times before)./EM/DIV DIVEM/EMnbsp;/DIV DIVEMLooking at the project I've been working on, We had something like those namespaces / VS projects (and others ... ):/EM/DIV DIVEMCompany.Project.Adt (for models that may be reused in other projects, like Language, Currency, ...)/EM/DIV DIVEMCompany.Project.Model (for project business domain specific models)/EM/DIV DIVEMCompany.Project.Data (for LLBLGen stuff, we have also "DataDBSpecific" and such related to Adapter mode)/EM/DIV DIVEMCompany.Project.Repositories (have interfaces and implementations for repositories, let's put aside why the two in one project for now)/EM/DIV DIVEM/EMnbsp;/DIV DIVEMA repository load method could probably look like:/EM/DIV DIVEMnbsp; Category Repository: /EM DIV style="FONT-FAMILY: consolas; BACKGROUND: black; COLOR: white; FONT-SIZE: 9pt"PRE style="MARGIN: 0px"SPAN style="COLOR: #ff8000"public/SPAN SPAN style="COLOR: #ff8000"static/SPAN SPAN style="COLOR: yellow"ReadOnlyCollection/SPANlt;SPAN style="COLOR: yellow"Category/SPANgt; LoadByShop(SPAN style="COLOR: yellow"Shop/SPAN shop, SPAN style="COLOR: #ff8000"bool/SPAN includeDisabledCategories)/PRE/DIV/DIV DIVEM/EMnbsp;/DIV DIVEMOr for internal use:/EM/DIV DIVEMnbsp; Shop Repository:/EM/DIV DIV DIV style="FONT-FAMILY: consolas; BACKGROUND: black; COLOR: white; FONT-SIZE: 9pt"PRE style="MARGIN: 0px"SPAN style="COLOR: #ff8000"internal/SPAN SPAN style="COLOR: #ff8000"static/SPAN SPAN style="COLOR: yellow"Shop/SPAN Load(SPAN style="COLOR: #2b91af"Guid/SPAN shopKey, SPAN style="COLOR: #ff8000"bool/SPAN loadCategories, SPAN style="COLOR: #ff8000"bool/SPAN loadProducts)/PRE/DIVEMnbsp; /EM/DIV DIVEMWhat I want to highlight here is the "include...", "load..." parameters. I'm not sure whether this is the best way to do it./EM/DIV DIVEM/EMnbsp;/DIV DIVEMAlso, what really hits me is the mapping. You know, from LLBLGen entities to our domain models. We have been doing this in factories which live in the Repository space. Each factory had methods similar to this:/EM/DIV DIVEM/EMnbsp;/DIV DIV DIV style="FONT-FAMILY: consolas; BACKGROUND: black; COLOR: white; FONT-SIZE: 9pt"PRE style="MARGIN: 0px"SPAN style="COLOR: #ff8000"public/SPAN SPAN style="COLOR: #ff8000"static/SPAN SPAN style="COLOR: yellow"Shop/SPAN CreateShopModel(SPAN style="COLOR: yellow"ShopEntity/SPAN entity)/PRE/DIV/DIV DIVEM/EMnbsp;/DIV DIV DIV style="FONT-FAMILY: consolas; BACKGROUND: black; COLOR: white; FONT-SIZE: 9pt"PRE style="MARGIN: 0px"SPAN style="COLOR: #ff8000"public/SPAN SPAN style="COLOR: #ff8000"static/SPAN SPAN style="COLOR: yellow"ShopEntity/SPAN CreateShopEntity(SPAN style="COLOR: yellow"Shop/SPAN shop/PRE/DIV/DIV DIVEM/EMnbsp;/DIV DIVEMRegardless of the "public" access modifier (this is all very well hidden behind a service layer, but let's put the whole issue aside as well), the idea of having to go through all the mapping has been just a boring ugly task, that has been there for long./EM/DIV DIVEMTo be honest, we didn't get so much benefit of it. It should have good promises, but how good compared to the cost of implementing them for complex object graphs ? That is the question!/EM/DIV DIVEM/EMnbsp;/DIV DIVEMThings got just worse when we wanted to implement our service layer. That's a service in the classic sense of "web" service layer (REST), we wanted to created DTOs that can correspond to XML and JSON responses of our choice, and again, we had to do the mapping from and to the domain models and DTOs. Want more ? The DTOs wouldn't convert to XML strings automatically (to JSON it would), we had to have another mapping layer from and to the DTOs and the actual XML./EM/DIV DIVEMOf course we had much time defining XML specifications and writing so many unit tests for this. I know not every project can go in this direction to this extent, but, I wanted to show where going in this path can take you./EM/DIV DIVEM/EMnbsp;/DIV DIVEMSo, even without service layer complications. You still have the model mapping tasks that (and this is what worries me) in many situations does not correspond to a "business" need. Note that I want to be doing Agile as well, and this makes the issue of delivering business value a true concern./EM/DIV DIVEM/EMnbsp;/DIV DIVEMYou can talk about automated generation for mapping. This may be something. We know it'll not be this direct or one to one of course anyway, but it may help./EM/DIV DIVEM/EMnbsp;/DIV DIVEMWould you do Domain Driven Design with "entity" models assuming the developers will stick to calling the repository's "Persist" method instead of "entity.Save();"? You just can't do that! How about new developers ? How about inconsistencies ?/EM/DIV DIVEMIs mapping really that bad and much of an effort ? First look at it, I say it isn't. But given complex scenarios I've been though I have to wonder about things like "complex object graph" and "caching" (in memory, on different levels, etc...)./EM/DIV DIVEM/EMnbsp;/DIV DIVEMIt's all about trying to calculate the costs indeed./EM/DIV/BLOCKQUOTE P mce_keep="true"nbsp;/P PThat’s what I’m trying to make out of this, the trick for the right cost./P H3Conclusion: How Aboutnbsp;YOU ??/H3 PLet me repeat the end of those messages:/P BLOCKQUOTE PEMAnyway, would love to hear your takes and what you have :) :) :)./EM/P/BLOCKQUOTE PIf you have any thought on the topic, those will be most appreciated. You can comment here or in A target=_blank href="http://tech.groups.yahoo.com/group/altdotnet/message/16324" mce_href="http://tech.groups.yahoo.com/group/altdotnet/message/16324"the topic messages page/A on A target=_blank href="http://tech.groups.yahoo.com/group/altdotnet/" mce_href="http://tech.groups.yahoo.com/group/altdotnet/"ALT.NET Yahoo Group/A. This is an open discussion area, and I do not expect it to be closed soon./P PSame, if you want to hear more ramblings on the topic, or just want me to shut it up all, send me a line./P PWould love to see what others have to say about this..../P DIV style="PADDING-BOTTOM: 0px; MARGIN: 0px; PADDING-LEFT: 0px; PADDING-RIGHT: 0px; DISPLAY: inline; FLOAT: none; PADDING-TOP: 0px" id=scid:0767317B-992E-4b12-91E0-4F059A8CECA8:e3f2848f-5fbf-40cf-bcff-c69f6a2ac024 class=wlWriterEditableSmartContentTechnorati Tags: A href="http://technorati.com/tags/.NET" rel=tag mce_href="http://technorati.com/tags/.NET".NET/A,A href="http://technorati.com/tags/Domain+Driven+Design" rel=tag mce_href="http://technorati.com/tags/Domain+Driven+Design"Domain Driven Design/A,A href="http://technorati.com/tags/DDD" rel=tag mce_href="http://technorati.com/tags/DDD"DDD/A,A href="http://technorati.com/tags/AlT.NET" rel=tag mce_href="http://technorati.com/tags/AlT.NET"AlT.NET/A,A href="http://technorati.com/tags/AltNET" rel=tag mce_href="http://technorati.com/tags/AltNET"AltNET/A,A href="http://technorati.com/tags/altnetconf" rel=tag mce_href="http://technorati.com/tags/altnetconf"altnetconf/A,A href="http://technorati.com/tags/agile" rel=tag mce_href="http://technorati.com/tags/agile"agile/A,A href="http://technorati.com/tags/ORM" rel=tag mce_href="http://technorati.com/tags/ORM"ORM/A,A href="http://technorati.com/tags/LLBLGen" rel=tag mce_href="http://technorati.com/tags/LLBLGen"LLBLGen/A,A href="http://technorati.com/tags/Frans+Bouma" rel=tag mce_href="http://technorati.com/tags/Frans+Bouma"Frans Bouma/A,A href="http://technorati.com/tags/Mohamed+Meligy" rel=tag mce_href="http://technorati.com/tags/Mohamed+Meligy"Mohamed Meligy/A,A href="http://technorati.com/tags/Local+Events" rel=tag mce_href="http://technorati.com/tags/Local+Events"Local Events/A/DIVimg src="http://weblogs.asp.net/aggbug.aspx?PostID=6674036" width="1" height="1"div class="feedflare" a href="http://feeds.feedburner.com/~f/GuruStop?a=5ktom"img src="http://feeds.feedburner.com/~f/GuruStop?i=5ktom" border="0"/img/a a href="http://feeds.feedburner.com/~f/GuruStop?a=TDvim"img src="http://feeds.feedburner.com/~f/GuruStop?i=TDvim" border="0"/img/a a href="http://feeds.feedburner.com/~f/GuruStop?a=5AWPm"img src="http://feeds.feedburner.com/~f/GuruStop?i=5AWPm" border="0"/img/a a href="http://feeds.feedburner.com/~f/GuruStop?a=iDCzM"img src="http://feeds.feedburner.com/~f/GuruStop?i=iDCzM" border="0"/img/a /divimg src="http://feeds.feedburner.com/~r/GuruStop/~4/418292079" height="1" width="1"/

div class="center"div class="image"a href="http://pixhost.ws/avaxhome/big_show.php?/avaxhome/22/63/00096322.jpeg" target="_blank"img src="http://pixhost.ws/avaxhome/22/63/00096322_medium.jpeg" id="external_img_615202"//a/divbr/ bScience and Its History: A Reassessment of the Historiography of Science/bbr/ 500 pages | Springer; 1 edition (October 2008) | ISBN: 1402056311 | PDF | 3 Mb/divbr/ Professor Joseph Agassi has published his Towards an Historiography of Science in 1963. It received many reviews by notable academics, including Maurice Finocchiaro, Charles Gillispie, Thomas S. Kuhn, Geroge Mora, Nicholas Rescher, and L. Pearce Williams. It is still in use in many courses in the philosophy and history of science. Here it appears in a revised and updated version with responses to these reviews and with many additional chapters, some already classic, others new. They are all paradigms of the author’s innovative way of writing fresh and engaging chapters in the history of the natural sciences.