https://github.com/starlink/tcldict

Starlink patched version of tcldict
https://github.com/starlink/tcldict

Last synced: 3 days ago
JSON representation

Starlink patched version of tcldict

• Host: GitHub
• URL: https://github.com/starlink/tcldict
• Owner: Starlink
• License: other
• Created: 2012-07-24T04:22:31.000Z (over 12 years ago)
• Default Branch: master
• Last Pushed: 2012-07-24T21:48:36.000Z (over 12 years ago)
• Last Synced: 2023-04-21T08:51:00.797Z (over 1 year ago)
• Language: Shell
• Size: 254 KB
• Stars: 1
• Watchers: 1
• Forks: 1
• Open Issues: 0
• Metadata Files:
  • Readme: README
  • Changelog: ChangeLog
  • License: license.terms

Awesome Lists containing this project

README

        

Updated: 17 November 2005.

The original dict extension from May 2004 has been updated with todays code

from the Tcl CVS repository.

This version doesn't have support for mp_int, because 8.4 has no such support.

April 2004.

This is a backport of the Tcl 8.5 [dict] command for Tcl 8.4. 

Most code was taken straight from from the Tcl-core CVS HEAD and

sampleextension on 14 April 2004. I glued it together with the help of

Donal K. Fellows, Don G. Porter and others to make this extension.

Perhaps the most significant change in the code is that it is slighly

less efficient than the real thing, mostly because some optimization

tricks are only available when linking against tclInt.h, not tcl.h.

- Pascal Scheffers.

UNIX BUILD

==========

Building under most UNIX systems is easy, just run the configure script

and then run make. For more information about the build process, see

the tcl/unix/README file in the Tcl src dist. The following minimal

example will install the extension in the /opt/tcl directory.

	$ cd tclDict

	$ ./configure --prefix=/opt/tcl

	$ make

	$ make install

WINDOWS BUILD

=============

The recommended method to build extensions under windows is to use the

Msys + Mingw build process. This provides a Unix-style build while

generating native Windows binaries. Using the Msys + Mingw build tools

means that you can use the same configure script as per the Unix build

to create a Makefile.

If you have VC++ then you may wish to use the files in the win

subdirectory and build the extension using just VC++. These files have

been designed to be as generic as possible but will require some

additional maintenance by the project developer to synchronise with

the TEA configure.in and Makefile.in files. Instructions for using the

VC++ makefile are written in the first part of the Makefile.vc

file.