Visual Prolog 7.4 Commercial Edition Crack
Sharif Garmon
As a commercial user you are allowed to evaluate the Personal Editions, with the purpose of deciding whether you want to purchase a Commercial Edition or not. Any other commercial usage is prohibited.
XSB, Inc. uses Prolog for knowledge extraction and standardization and for ontology representation. They found that Prolog code is more stable and they spend less on maintaining it than with Java code. www.xsb.com/
The Nokia N900 phone used prolog to do UI state management
Prosyn: chemical process design consultant. The system is mainly implemented in Prolog. www.process-design-center.com
Australian company developing stock brokering toolswww.securitease.com/
Budapest company specialized in developing and providing microscale flow instruments for chemistrywww.thalesnano.com/
Watson by IBMwww.cs.nmsu.edu/ALP/2011/03/natural-language-processing-with-prolog-in-the-ibm-watson-system
Cohors LLC uses an automatic test framework written in Prolog and wrote auto test sets for different companies products including AVG.
U.S. Customs and Border Protection (CBP) uses prolog for various purposes central to its mission. This is a complex application in a high-volume large data environment, mixed with C, Java, C++.
v7.4 [Dec 8, 2012]
The main feature in Visual Prolog 7.4 is the ability to generate 64 bit programs (Commercial Edition only), making it possible to write programs that exploit more of the computers resources.
Program Point
Support for exceptions handling improvement (programPoint type and attribute, implicit programPoint argument). See also programPoint.
Syntax & Warnings
Better handling of comma (,) before then, elseif, else, end if, do and end foreach
Error c550 for inlining a field from a null pointer
Warning c647 if bound/1 is applied to a variable which is always free
Warning if scope is only opened but is not actually used (unused open for class core is ignored). Removing such excessive open-directives makes the Optimal Includes more effective. This warning is switched off by the default (option /w:231 turns it on).
PFC
PFC have been updated to be 64 bit compatible. A few packages have not been updated, but have instead been deprecated and replaced by new packages.
vpiEditor is deprecated
regExp is deprecated
PFC/GUI
sciLexer New editor control based on the Scintilla editor with lexers (including Visual Prolog lexer).
webBrowser New control control comprehensive wrapping of the Internet Explorer WebBrowserControl
Improved clipboard handling (with HTML support)
ribbonControl and command system and controlSerialization; with a run-time visual designer that simplifies the process of making ribbons
toolboxControl control
headerControl control
rebar statusBar packages
shellNotificationIcon for handing notifications in the shells notification area Demo
toolTip package and toolTip functionality on standard controls Demo
splitControl control for multi-split management; with a run-time visual designer that simplifies the process of making splits
splitterControl control for the split in windows
dragNdrop class for (in-program) drag and drop functionality Demo
Object oriented GDI support
Object oriented GDI support for:
bitmap
brush
font
palette
pen
deviceContext
icon
gui_native::createDialogIndirectParam Update for font handling
window::listenUntilDestroy New predicate for listening to an event, but detach the listening when the window is destroyed
messageLoop for SDI applications
PFC (non-GUI)
regEx package based on [www.boost.org/libs/regex boost regular expression library]
mapM_hash & setM_hash New classes for hash table implementations of maps and sets
arrayM uses pointer to memory instead of binary: makes it possible to interpret non-binaries as arrays and is more efficient
arrayM_inline New class for interpretation of C/C struct arrays
arrayM_boolean New class for compact boolean arrays (1 bit per boolean).
array2M New class for 2 dimensional arrays
socket New class for object oriented WinSock2 support
event0 - event7 New classes for general/generic event handling (notify listener)
iStream_stream class for mapping a Visual Prolog stream as an IStream com object (CE-only)
improved ISAPI support
json (pfc/web/json) and jsonRpc New packages for JSON and JSON RPC 2.0 support (CE-only)
memory allocate functions with argument for atomic/non-atomic
ODBC auto parameter binding get the size from the database by means of SQLDescribeParam
shell_api::sHCreateStreamOnFileEx new predicate for creating an IStream com object from a file
xhtmlWriter class for writing xhtml/xhtml5 using an xmlWriter
xmlReader & xmlWriter based on the xmlLite API (CE-only) Demo
internetExplorer class for automating an out-of-process Internet Explorer
IDE
Simplified settings dialog
Add "No To All" button to the dialog for removing file from a project
Create empty clause if there is compiler error for absent clause for a predicate
Global unreachability support
History of Run Arguments
Improved Browse View
Improved the manifest handling
Load browse info in a separate thread (performance optimization)
SDI applications support
Tools entries in project-tree popup menu
Debugger
Soft/hard breakpoints
Add current class facts into the variable window
Show class facts in the Variable Window for a class predicate
Give names to objects
Show gmtTimeValue and localTimeValue as dates and times.
Show the error description for hResult values.
Watch Window improvement
Copying the entire debug tree to the clipboard
Improve memory view for 64bit and break points handling
Others
win32.lib win32.x64.lib updated to Windows Software Development Kit (SDK) for Windows 8
PFC, VPI, IDE: Help button in the title bar
SolutionManager. A utility for better handling of a collection of projects
VipBuilder: Add /platform option for target machine
VPI: Support DDE in SDI application
Switch to Mercury. The type system is more powerful, the code is
blindingly fast, it isn't tied to 80*86s, it handles DCGs, and it's free.Of course you don't get the "visual" bit. PDC Prolog's user interface
stuff shouldn't be too hard to emulate; what does Visual Prolog offer?--
Fifty years of programming language research, and we end up with C++ ???
Richard A. O'Keefe; ok; RMIT Comp.Sci.
I think Thomas Lindgren is pointing out something I heared around
from a fairly large number of people involved in logic programming.
Basically, giving away expressiveness for speed is _wrong_.
Giving up Prolog for less expressive languages for reasons
of speed, types/modes, proprietary visual tools etc. is _wrong_ too.
Some history might help on this.For many `real' Prologers today Turbo-Prolog is `out' and Mercury `in'.
Novelty and Fregus Henderson's well-targeted postings have definitely
helped Mercury, as well as our fascination with speed on some popular
functional-programs-in-relational-form (tak and friends) benchmarks :-)I should agree that there's a lot of inventive implementation skill and
talent involved in Mercury. I do not know about the latest version of
Turbo-PDC-Visual `Prolog'. Except for the fact of not supporting
meta-programming and having a too limitative type system it also seemed
to be a well implemented language with its own merits. It had a fairly
effective mode inference algorithm, among other things. And it was
really `in', for a while.I think that the two languages have much more in common than what
separates them from Prolog. Basically, they have given away
expressiveness for speed. By the way, the two languages should, at
some point, be compared empirically on speed, program size and size of
standalone executables on both functional style and nondeterministic
programs. Any volunteers having both implementations around? Mercury
on Linux vs. PDC on W95 or NT looks fair enough to me.It is likely that the designers/implementors of the two languages have
(independently?) got attempted to push static compilation techniques to
their limit while giving away, little by little, some of the key
features that make `real' Prolog so appealing: logical variables,
unification, the 5 lines meta-interpreter etc.Not only purity was given away but the fancy parts of impure stuff as
well: if I remember well, only ground facts were allowed in Turbo
Prolog's dynamic data-base. Mercury, being a `purely declarative'
`new language', (despite the fact that it still runs under
SICStus:-), does not have such a beast at all.The few mode and type declarations, usually less than the size of the
clauses themselves :-), are enough to break meta-programming once for
all. The same did happened with Turbo Prolog. A 100-times slower
meta-interpreter for real Prolog gave back `Edinburgh Prolog
functionality', of course :-). A little bit smaller and a lot
slower than in C.Wanting to know `too much' statically is not worth its price when half
of the code will travel on the net (to end up executed in the Java-chip
in your TV set:-) Overall, the main strength of logic programming as a
practical programming tool is expressiveness. A factor of 2-3 in speed
is simply not enough to give it away. Modes and types are helpful to
manage complexity but without inference they are tedious enough not to
be excused for killing out convenient meta-programming.To leave some hope, I would gladly switch to Visual Prolog if it had
type inference and to Mercury if it had at least as much mode inference
as Visual Prolog :-). Combined with a first order representation of
type and mode declarations and a 10 lines meta-interpreter around.Until then, the slim Prolog kernel which successfully survived ISO
standardization looks just too hard to beat. Visual programming is not
an issue as most modern Prologs have at least a Tcl/Tk interface and
Java interfaces are coming. Learning a home brewed visual language
with Prolog syntax when you already know a generic one is not worth
it. I think that Prolog as an embedded logic engine in a multi-paradigm,
net aware environment is still the way to go for the next few years.
Paul Tarau--
Paul Tarau, PhD. Associate professor Phone: (506) 858-4120
Dept. of Computer Science University of Moncton FAX: (506) 858-4541
Moncton N.B. CANADA E1A-3E9 ta...@info.umoncton.ca