[ANNOUNCE] link-grammar version 4.7.1 is now available

[Linas Vepstas]

Link-grammar version 4.7.1 is now available.

Link-grammar is a parser of the English language. See the website

http://www.abisource.com/projects/link-grammar/

for details. The latest version may be downloaded from:

http://www.abisource.com/downloads/link-grammar/4.7.1/link-grammar-4.7.1.tar.gz

This version fixes several bugs introduced by the conjunction-handling
rework of 4.7.0. Several Windows-related compile fixes are included as well.

Changelog:

* Fix: dictionary: Add "x" as synonym for "times".
* Fix: compilation failure due to lack of termios support on Windows.
* Fix: if not set, then force-set locale to UTF-8 in the java library.
* Fix: Explicitly include <stddef.h> for Windows builds.
* Fix: "John imagines himself lost".
* Fix: predicative adjectives w/misc verbs: "You are driving me crazy"
* Fix: "judge innocent", etc.
* Fix: many, many conjoined present tense verbs.
* Fix: conjoined verbs with negations.
* Fix: "to" as post-nominal modifier: "the inability to laugh"

[Simon J Stuart]

Linas,
Any functions added/depreciated/removed, or parameters/return types thereof
that I need to know about (to keep my Delphi wrapper up-to-date)?

Thanks,
Simon J Stuart

http://www.abisource.com/projects/link-grammar/

http://www.abisource.com/downloads/link-grammar/4.7.1/link-grammar-4.7.1.tar
.gz

Changelog:

--
You received this message because you are subscribed to the Google Groups
"link-grammar" group.
To post to this group, send email to link-g...@googlegroups.com.
To unsubscribe from this group, send email to
link-grammar...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/link-grammar?hl=en.

[Simon J Stuart]

Linas,
Just to clarify, I meant only methods exported by the DLL (API methods), not
internal methods.

Regards,
Simon

[Linas Vepstas]

On 11 December 2010 11:34, Simon J Stuart <kra...@greycascade.com> wrote:
> Linas,
> Any functions added/depreciated/removed, or parameters/return types thereof
> that I need to know about (to keep my Delphi wrapper up-to-date)?

No.

Please note that I try hard to adhere to industry-standard version numbering:
4==major version
7==minor version
1==revision

Functions removed, or function signatures/return types changed: bump
MAJOR version number

Functions added: bump MINOR version number

Bug fixes, no API change: bump up REVISION number.

There are MANY software distributors who seem to not understand/adhere to this
industry-standard version numbering system. The biggest offenders seem to come
from the Java world. Please think about what the above version numbering scheme
really means, and encourage others to use it!

-- linas

[Simon J Stuart]

Linas,
Duly noted and added to my development vocabulary... to be honest I've never
adhered to a version numbering standard in such a strict manner, though I
don't change Major or Minor when releasing bug fixes only.

Thanks for the info :)

Regards,
Simon

-----Original Message-----
From: link-g...@googlegroups.com [mailto:link-g...@googlegroups.com]
On Behalf Of Linas Vepstas
Sent: 11 December 2010 17:44
To: link-g...@googlegroups.com
Subject: Re: [Link Grammar] [ANNOUNCE] link-grammar version 4.7.1 is now
available

No.

-- linas

--

[Linas Vepstas]

On 11 December 2010 12:05, Simon J Stuart <kra...@greycascade.com> wrote:
> Linas,

> Duly noted and added to my development vocabulary... to be honest I've never
> adhered to a version numbering standard in such a strict manner, though I
> don't change Major or Minor when releasing bug fixes only.

When programming in C, or in any language that supports dll's (dynamically
loaded libraries) aka "shared libraries", the above versioning scheme allows
automated tools to ensure that compatible libraries work correctly with
one-another, as needed.

If one fails to adhere to this, things will break/not work/can't be automated.
Historical examples include the infamous "dll hell" of windows, where installing
a new dll would usually cause some other app, using an earlier version
of the dll,
to break. (I'm told that modern windows has finally solved this problem!?)

An ongoing example where "dll hell" has not been solved is Java, where,
due to lack of versioning and proper version maintenance, the "solution" is
ship all of the dependent jar files along with the app itself, thus
defeating the
whole point of having jar files to begin with. As a result, java apps are slow
to load, hog up tons of memory, chew through disk space, are hard to debug,
hard to install, hard to configure. Thus, although Java is often hyped as a
"better C/C++", it lacks the tools/automation needed to keep development sane.

--linas

[Simon J Stuart]

Never been a Java fan myself... besides I don't see it having much of a
future now that it's under Oracle.

Couldn't agree more about "dll hell", though I should point out that most
applications I build are executables, and where I produce DLLs, a strict
"reverse-compatibility" or "legacy support" regimen is adhered to.

Regards,
Simon

-----Original Message-----
From: link-g...@googlegroups.com [mailto:link-g...@googlegroups.com]
On Behalf Of Linas Vepstas
Sent: 11 December 2010 19:54
To: link-g...@googlegroups.com
Subject: Re: [Link Grammar] [ANNOUNCE] link-grammar version 4.7.1 is now
available

--linas

--