Xotcl January 2015

xotcl@alice.wu.ac.at

4 participants
4 discussions

Announcement: Next Scripting Framework 2.0.0 available
by Gustaf Neumann 09 May '19

09 May '19

Dear Community, Since releasing the Next Scripting Framework (NSF) 2.0b5, we have received more feedback from early adopters. Many thanks for the helpful and the constructive comments! Since the release of 2.0b5, there have been more than 450 commits to our code repository. The implementation is very stable and has been used for more than two years in production of our large-scale, multi-threaded web environment inside NaviServer. Most of the changes happened in NX and, therefore, on the NSF scripting level, without the need to modify the NSF C layer. The implementation of XOTcl 2 has changed very little. The Next Scripting Framework was tested with Tcl 8.5.17 and Tcl 8.6.2 on Linux, Mac OS X, and in Windows enviroments (MinGW, VC12). Below are the most notable differences in NSF/NX 2.0 final relative to 2.0b5: a) Pluralism reform: Use plural names for structural features of objects and classes, whenever potentially multiple elements are provided or returned. This rule applies now consistently throughout NX. Here are examples from the introspection interface: /cls/ info superclasses /cls/ info subclasses /cls/ info mixins /obj/ info object mixins /cls/ info filters /obj/ info object filters Similarly, there the plural is used for configure options, e.g.: nx:create create Foo -superclasses {C D} Note that abbreviations are allowed as well: nx:create create Foo -superclass {C D} b) Dispatch by arity is gone in NX. XOTcl and earlier versions of NX supported a dispatch-by-arity mechanism for relation slots: o mixin; # arity 1: get value o mixin M1; # arity 2: set value o mixin add M1; # arity 3: use arg 2 for slot methods The problem with this approach is that it is not straight forward to provide meaningful error messages. In addition, one might be irritated about the result of e.g. "o mixin add" (leaving out a class to be added). In the final release, we removed the entailed complexity by relying on a fixed arity of 3 (last form above) for the default slot methods: add, clear, delete, get, guard, set c) Support for querying computed parameters of methods. Earlier versions of NX had several methods to query the parameters for configuring objects of different classes. The configure parameters are determined by the inheritance order in the class hierarchy and are relevant during object creation (e.g. methods "create" or "new"). Now, these configure parameter can be queried using the standard parameter introspection interface for e.g. "new", "create", or "configure", such as in: nx::Object info lookup parameters create The above command call returns the parameters which can be provided to an "nx::Object create ..." invocation. Furthermore, these computed parameters are returned in error messages. d) Support abbreviations of non-positional parameter names (for plain methods, nsf::proc, or "... configure..."). To avoid surprises, especially for computed argument lists, the minimal number of optional trailing characters is set to 4. e) Updated MongoDB interface: The interface was extended in various ways and is now based on mongo-c-driver 1.0.2 and was tested with MongoDB 2.6.5. The driver can be used nicely with e.g. Naviserver by using the c-driver supported connection pool. f) API changes: nx::Object info lookup parameters create /cls/ mixins ... /obj/ object mixins ... /cls/ filters ... /obj/ object filters ... Simplified info methods for interceptors: /cls/ info mixin classes -> /cls/ info mixins /cls/ info filter methods -> /cls/ info filters /obj/ info object mixin classes -> /obj/ info object mixins Dropped methods: /cls/ info mixin guard /obj/ info object mixin guard /cls/ info filter guard /obj/ info object filter guard Instead, use the "-guards" option of "... info ?object? mixins|filters ...". Added methods: /cls/ mixins classes /cls/ filters methods /obj/ object filters methods /obj/ object mixins classes g) Added API documentation: Using tcllib's doctools markup and dtplite, we now provide manpages for: nx::Object nx::Class nx::current nx::next nx::configure The Next Scripting Framework 2.0.0 (containing NX and XOTcl 2.0.0) can be obtained from https://next-scripting.org/ The detailed ChangeLog can be downloaded from https://next-scripting.org/xowiki/download/file/ChangeLog-2.0b5-2.0.0 Best regards - Gustaf Neumann - Stefan Sobernig

1 3

nextto
by Victor Mayevski 23 Jan '15

23 Jan '15

Recently I looked over TclOO and noticed a "nextto" feature. It appears to be pretty useful and I supposed it should be trivial to implement it in NX. Any ideas how? Thanks, Victor

2 1

Announcement: XOTcl-Light Available XOTcl on top of TclOO
by mail＠xdobry.de 23 Jan '15

23 Jan '15

Hi! I have created XOTcl-Light package. It is pure Tcl package on TclOO that provide XOTcl compatible system. https://github.com/xdobry/xotcl-light It is not full compatible and slower (more or less 50% slower than original XOTcl) but enough to run my own XOTcl programs. All XOTcl-Light object are TclOO objects and can be modified introspected and extended by TclOO code. Incompatiblities * no complex slot attributes. Only simple parameter similar to earlier XOTcl versions. * no complex forward syntax only TclOO forward * no unknown mechanism for creating object from class (MyClass create myinst, can not be written as MyClass myinst). It can be easy simulated but I do not use it * many introspection command does not support all options * self is not modified and work like in TclOO It is early version the work is ongoing. Please report bugs. Best Regards Artur

1 0

Suggestion needed
by Victor Mayevski 22 Jan '15

22 Jan '15

Using NX, over some period of time, I have find myself customizing nx::Object (adding my own methods to it) in order to adapt NX to my personal needs. It works and is a nice way to extend NX globally but I would rather not pollute the nx:: namespace. Can there be a better way of doing it, like, for example "nx copy nxcustom" and then using nxcustom::Object and nxcustom::Class? I have tried making a copy of the nx.tcl source file and renaming the "nx" namespace in it. That does work nicely but might not be the best way of doing it. Any suggestions? Thanks

3 5

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

2000

Xotcl January 2015