Weblog Page

From: Fabrice Pardo <Fabrice.Pardo_at_Lpn.cnrs.fr>
Date: Wed, 23 Feb 2005 12:19:22 +0100 (MET)

This is a minor bug, 1.3.3 returns 1.3 instead of 1.3.3

package require XOTcl ;# -> 1.3
package versions XOTcl ;# -> 1.3.3

-- 
Fabrice Pardo

From: Victor Mayevski <vitick_at_gmail.com>
Date: Sat, 19 Feb 2011 19:26:10 -0800

Thank you Stefan. That clarifies it.

On Fri, Feb 18, 2011 at 3:58 AM, Stefan Sobernig
<stefan.sobernig_at_wu.ac.at> wrote:
> Victor,
>
>>  Am I doing something wrong?
>
> No, what you scripted is perfectly fine (by intention), you just revealed a
> collateral (in my understanding):
>
> Right now, there is no ::nx::Object->unknown() defined, which would be the
> [next] target. Therefore, [next] does not give you what you expect. If you
> look in nx.tcl, it is simply commented out.
>
> In the commit
> http://fisheye.openacs.org/changelog/xotcl/?cs=//xotcl/67ad561b71e208451454fc1d71e591e75e4f3a71
> changes where applied to make a scripted unknown method on the root class
> (::nx::Object) unnecessary.
> however, these changes do not cover the case of refining this built-in
> unknown "method".
>
> a quick workaround for the scope of your application is to define
> ::nx::Object->unknown() at an early stage:
>
> ::nx::Object protected method unknown {m args} {
>  error "[::nsf::self]: unable to dispatch method '$m'"
> }
>
> or simply signal the error in your application-level unknown:
>
> C method unknown {m args} {
>  if {$args eq "test"} {
>    puts "found test";
>    return
>  }
>  error "[::nsf::self]: unable to dispatch method '$m'"
> }
>
>
> for an authorative fix i would need to understand why these changes happened
> in the first place which i don't, frankly. was the intention to remove
> unknown from ::nx::Object method record entirely? i hope not ... but gustaf
> is the authority here.
>
> //stefan
>

From: SImon Millward <simon_at_tcbventures.com>
Date: Wed, 4 Aug 2010 17:50:10 +0100

Isn't it fair to say that by design, any dynamic language has such possible traps and pitfalls... (although this one is especially awkward). You don't need to try very hard to make TCL fall over in all sorts of ways like this.

The question I always ask my teams when something like this comes up is
- Why didn't the unit tests catch it
- What 'stock' unit test will we add in future to catch it

> It's very easy to miss, as it's quite natural for a coder to pass in arguments directly to constructors.

Its quite hard to miss if you TDD it...

Over a fairly short period of time you soon have a nice set of unit test classes that always try an throw up these sorts of problems. Probably about half a dozen small tests that pump in 'iffy' stuff to a method covers it.. and because of the beauty of typeless (or stringly typed) languages than can be readily used without modification

Anyway, just my thoughts.

Regards
Simon


On 4 Aug 2010, at 13:14, Kristoffer Lawson wrote:

>
> On 4 Aug 2010, at 12:37, Gustaf Neumann wrote:
>
>> without knowing the length of the argument list (which is in the general
>> case not possible in Tcl due to args). For me it is sometimes surprising,
>> how well it works even for large projects, with several thousand lines
>> of code and many developers involved. The XOTcl serializer
>> uses the dash notation as well, but analyses the arguments and adds the
>> lists
>> as needed.
>
> Yes, this is the first time I came across this, and it took a while to debug :-) However I'm almost certain a lot of code I have stored around is susceptible to the same thing. That's the danger with this: it's very easy to get by by just passing in arguments in the normal way, and then end up with a severe security hole. It's very easy to miss, as it's quite natural for a coder to pass in arguments directly to constructors.
>
>> Anyhow, the next incarnation of XOTcl, on which we are hard working
>> right now, has this feature dropped, and provides a much more orthogonal
>> parameterization for objects and methods. As the new framework
>> supports multiple object systems in one interpreter, one can use classical
>> XOTcl and the new object system in parallel.
>
> I think dropping it is a good decision. It'll be interesting to see what the next XOTcl is like.
>
> How much complexity will the new version be adding? The beauty with XOTcl, especially the earlier versions, was that despite the power of it, it was quite simple (unlike C++). Much like Tcl itself: power, but simplicity. I would be concerned if that gets lost along the way.
>
> --
> Kristoffer Lawson, Co-Founder, Scred // http://www.scred.com/
>
> _______________________________________________
> Xotcl mailing list
> Xotcl_at_alice.wu-wien.ac.at
> http://alice.wu-wien.ac.at/mailman/listinfo/xotcl

From: Kristoffer Lawson <setok_at_fishpool.com>
Date: Sat, 20 Jan 2001 01:52:04 +0200 (EET)

In the tutorial you have a diagram which presents how multiple inheritance
works in XOTcl. The one with Room and Kitchen etc. As far as I can tell,
the diagram has Room and 4WallsRoom the wrong way round. Ie. it shows
Room's being next after Kitchen in the next chain, when presumably it
should be 4WallsRoom.

         - ---------- = = ---------//--+
         | / Kristoffer Lawson | www.fishpool.fi|.com
         +-> | setok_at_fishpool.com | - - --+------
             |-- Fishpool Creations Ltd - / |
             +-------- = - - - = --------- /~setok/

From: <akupries_at_shaw.ca>
Date: 05 Apr 2016 20:58:19 -0700

Hello XOTcl Developers, fyi ...

23rd Annual Tcl/Tk Conference (Tcl'2016)
http://www.tcl.tk/community/tcl2016/

November 14 - 18, 2016
Crowne Plaza Houston River Oaks
2712 Southwest Freeway, 77098
Houston, Texas, USA

Important Dates:

Abstracts and proposals due September 12, 2016
Notification to authors September 19, 2016
WIP and BOF reservations open August 22, 2016
Author materials due October 24, 2016
Tutorials Start November 14, 2016
Conference starts November 16, 2016

Email Contact: tclconference_at_googlegroups.com

Submission of Summaries

Tcl/Tk 2016 will be held in Houston, Texas, USA from November 14, 2016 to November 18, 2016.

The program committee is asking for papers and presentation proposals
from anyone using or developing with Tcl/Tk (and extensions). Past
conferences have seen submissions covering a wide variety of topics
including:

* Scientific and engineering applications
* Industrial controls
* Distributed applications and Network Managment
* Object oriented extensions to Tcl/Tk
* New widgets for Tk
* Simulation and application steering with Tcl/Tk
* Tcl/Tk-centric operating environments
* Tcl/Tk on small and embedded devices
* Medical applications and visualization
* Use of different programming paradigms in Tcl/Tk and proposals for new
  directions.
* New areas of exploration for the Tcl/Tk language

Submissions should consist of an abstract of about 100 words and a
summary of not more than two pages, and should be sent as plain text
to tclconference_at_googlegroups.com no later than September 12, 2016. Authors of accepted
abstracts will have until October 24, 2016 to submit their final
paper for the inclusion in the conference proceedings. The proceedings
will be made available on digital media, so extra materials such as
presentation slides, code examples, code for extensions etc. are
encouraged.

Printed proceedings will be produced as an on-demand book at lulu.com

The authors will have 30 minutes to present their paper at
the conference.

The program committee will review and evaluate papers according to the
following criteria:

* Quantity and quality of novel content
* Relevance and interest to the Tcl/Tk community
* Suitability of content for presentation at the conference

Proposals may report on commercial or non-commercial systems, but
those with only blatant marketing content will not be accepted.

Application and experience papers need to strike a balance between
background on the application domain and the relevance of Tcl/Tk to
the application. Application and experience papers should clearly
explain how the application or experience illustrates a novel use of
Tcl/Tk, and what lessons the Tcl/Tk community can derive from the
application or experience to apply to their own development efforts.

Papers accompanied by non-disclosure agreements will be returned to
the author(s) unread. All submissions are held in the highest
confidentiality prior to publication in the Proceedings, both as a
matter of policy and in accord with the U. S. Copyright Act of 1976.

The primary author for each accepted paper will receive registration
to the Technical Sessions portion of the conference at a reduced rate.

Other Forms of Participation

The program committee also welcomes proposals for panel discussions of
up to 90 minutes. Proposals should include a list of confirmed
panelists, a title and format, and a panel description with position
statements from each panelist. Panels should have no more than four
speakers, including the panel moderator, and should allow time for
substantial interaction with attendees. Panels are not presentations
of related research papers.

Slots for Works-in-Progress (WIP) presentations and Birds-of-a-Feather
sessions (BOFs) are available on a first-come, first-served basis
starting in August 22, 2016. Specific instructions for reserving WIP
and BOF time slots will be provided in the registration information
available in August 22, 2016. Some WIP and BOF time slots will be held open
for on-site reservation. All attendees with an interesting work in
progress should consider reserving a WIP slot.

Registration Information

More information on the conference is available the conference Web
site (http://www.tcl.tk/community/tcl2016/) and will be published on
various Tcl/Tk-related information channels.

To keep in touch with news regarding the conference and Tcl events in
general, subscribe to the tcl-announce list. See:
http://code.activestate.com/lists/tcl-announce to subscribe to the
tcl-announce mailing list.


Conference Committee

   * Andreas Kupries Hewlett Packard Enterprise
   * Arjen Markus Deltares
   * Brian Griffin Mentor Graphics
   * Clif Flynt Noumena Corp
   * Gerald Lester KnG Consulting LLC
   * Joe Mistachkin Mistachkin Systems
   * Ronald Fox CAEN Technologies
                     NSCL _at_ Michigan State University

Contact Information tclconference_at_googlegroups.com

Tcl'2016 would like to thank those who are sponsoring the conference:

   * Mentor Graphics
   * Tcl Community Association

From: Scott Gargash <scottg_at_atc.creative.com>
Date: Mon, 8 May 2006 17:03:58 -0600

Gustaf Neumann <neumann_at_wu-wien.ac.at> wrote on 05/08/2006 02:15:41 PM:

>
> > BTW, this will happen with any method, not just "destroy".
> >
> i know.
> >
> > Is it not considered acceptable to ever remove a mixin class?
> >
> > When is it valid to remove a mixin if removing it corrupts the method
> > chaining?
> >
>
> removing a mixin class from the mixin list does not "corrupt" the chain
> in the sense that there
> is a memory corruption etc. The current implementation does not allow to
> remove
> ***active*** mixin classes, this are the classes of which the method is
> currently executing.

I did a little more experimenting, and it's a little stronger than that. You also can't remove a
mixin from anything invoked by the active mixin. I.e., you can't forward the "mixin delete" to an
object of another class. If the mixin to be deleted is present in the call stack, it appears that
the mixin can't be deleted. Not that I expected it to work, but it seems worth noting.

> It looks quite easy to give a reasonable error message, when the
> currently active
> mixin class is deleted, it will be more expensive to handle this problem in
> a friendly way.

Is the expense something that would be encountered on every method invocation, or would it only be
paid when deleting a mixin?

I really ought to spend some time with the source...

      Scott

From: Andreas Kupries <andreask_at_activestate.com>
Date: Wed, 30 May 2012 08:45:26 -0700

[[ Notes:

   Colin Walker of F5 is confirmed as our Keynote speaker.
   http://www.f5.com

]]

19th Annual Tcl/Tk Conference (Tcl'2012)
http://www.tcl.tk/community/tcl2012/

November 12 - 16, 2012
Holiday Inn Chicago Mart Plaza
350 West Mart Center Drive
Chicago, Illinois, USA

Important Dates:

Abstracts and proposals due August 27, 2012
Notification to authors September 10, 2012
WIP and BOF reservations open August 6, 2012
Author materials due October 29, 2012
Tutorials Start November 12, 2012
Conference starts November 14, 2012

Email Contact: tclconference_at_googlegroups.com

Submission of Summaries

Tcl/Tk 2012 will be held in Chicago, Illinois, USA from November 12 -
16, 2012. The program committee is asking for papers and presentation
proposals from anyone using or developing with Tcl/Tk (and
extensions). Past conferences have seen submissions covering a wide
variety of topics including:

* Scientific and engineering applications
* Industrial controls
* Distributed applications and Network Managment
* Object oriented extensions to Tcl/Tk
* New widgets for Tk
* Simulation and application steering with Tcl/Tk
* Tcl/Tk-centric operating environments
* Tcl/Tk on small and embedded devices
* Medical applications and visualization
* Use of different programming paradigms in Tcl/Tk and proposals for new
  directions.
* New areas of exploration for the Tcl/Tk language

Submissions should consist of an abstract of about 100 words and a
summary of not more than two pages, and should be sent as plain text
to <tclconference AT googlegroups DOT com> no later than August 27,
2012. Authors of accepted abstracts will have until October 29, 2012
to submit their final paper for the inclusion in the conference
proceedings. The proceedings will be made available on digital media,
so extra materials such as presentation slides, code examples, code
for extensions etc. are encouraged.

Printed proceedings will be produced as an on-demand book at lulu.com

The authors will have 25 minutes to present their paper at the
conference.

The program committee will review and evaluate papers according to the
following criteria:

* Quantity and quality of novel content
* Relevance and interest to the Tcl/Tk community
* Suitability of content for presentation at the conference

Proposals may report on commercial or non-commercial systems, but
those with only blatant marketing content will not be accepted.

Application and experience papers need to strike a balance between
background on the application domain and the relevance of Tcl/Tk to
the application. Application and experience papers should clearly
explain how the application or experience illustrates a novel use of
Tcl/Tk, and what lessons the Tcl/Tk community can derive from the
application or experience to apply to their own development efforts.

Papers accompanied by non-disclosure agreements will be returned to
the author(s) unread. All submissions are held in the highest
confidentiality prior to publication in the Proceedings, both as a
matter of policy and in accord with the U. S. Copyright Act of 1976.

The primary author for each accepted paper will receive registration
to the Technical Sessions portion of the conference at a reduced rate.

Other Forms of Participation

The program committee also welcomes proposals for panel discussions of
up to 90 minutes. Proposals should include a list of confirmed
panelists, a title and format, and a panel description with position
statements from each panelist. Panels should have no more than four
speakers, including the panel moderator, and should allow time for
substantial interaction with attendees. Panels are not presentations
of related research papers.

Slots for Works-in-Progress (WIP) presentations and Birds-of-a-Feather
sessions (BOFs) are available on a first-come, first-served basis
starting in August 6, 2012. Specific instructions for reserving WIP
and BOF time slots will be provided in the registration information
available in June 2012. Some WIP and BOF time slots will be held open
for on-site reservation. All attendees with an interesting work in
progress should consider reserving a WIP slot.

Registration Information

More information on the conference is available the conference Web
site (http://www.tcl.tk/community/tcl2012/) and will be published on
various Tcl/Tk-related information channels.

To keep in touch with news regarding the conference and Tcl events in
general, subscribe to the tcl-announce list. See:
http://code.activestate.com/lists/tcl-announce to subscribe to the
tcl-announce mailing list.


Conference Committee

Clif Flynt Noumena Corp General Chair, Website Admin
Andreas Kupries ActiveState Software Inc. Program Chair
Cyndy Lilagan Nat. Museum of Health & Medicine, Chicago Site/Facilities Chair
Arjen Markus Deltares
Brian Griffin Mentor Graphics
Donal Fellows University of Manchester
Gerald Lester KnG Consulting, LLC
Jeffrey Hobbs ActiveState Software Inc.
Kevin Kenny GE Global Research Center
Larry Virden
Mike Doyle National Museum of Health & Medicine, Chicago
Ron Fox NSCL/FRIB Michigan State University
Steve Landers Digital Smarties

Contact Information tclconference_at_googlegroups.com


Tcl'2012 would like to thank those who are sponsoring the conference:

ActiveState Software Inc.
Buonacorsi Foundation
Mentor Graphics
Noumena Corp.
SR Technology
Tcl Community Association

From: <vitick_at_gmail.com>
Date: Sat, 9 Oct 2010 12:05:49 -0700 (PDT)

Don't know if the mailing list is the best place to post bug reports. Let me know the correct way to do it.

On a clean 32 bit debian based system, fresh compilation of TCL 8.5.9 and XOTcl/Next, TCL will crash when calling "obj info has type" without arguments or with wrong arguments:

nx::Class create C
C create obj
obj has type
tclsh: ./generic/nsf.c:9853: IsSubType: Assertion `cl && subcl' failed.

From: Gustaf Neumann <neumann_at_wu-wien.ac.at>
Date: Sun, 28 Nov 2010 04:24:05 +0100

Rebuild the pkgIndex.tcl files with

    make libraries-pkgindex

Not sure, why and how you got the problem, but i will try to
trigger the rebuild of these files more eagerly... maybe a
pkg_mkIndex failed in your version....

i guess, part of the problem is that "pkg_mkIndex" without
the flag "-verbose" is completely silent also in cases where
an "error" occurs (often a missing dummy "namespace
declaration", just needed for building pkgIndex). If
pkg_mkIndex is called with "-verbose", it is too verbose...
I have now altered the behavior pkg_mkIndex in the build
process, problems with while building pkgIndex will be easy
detected.

Get a fresh version from git

-gn

On 28.11.10 00:07, Victor Mayevski wrote:
> Thank you Gustaf, that fixed the error. There is an additional error:
>
> can't find package xotcl::package
> while executing
> "package require xotcl::package"
> (file "./library/xotcl/library/lib/makeDoc.xotcl" line 16)
> make: *** [library/xotcl/doc/langRef-xotcl.html] Error 1
>
> The error seems to be caused by missing pkgIndex.tcl file in
> ./library/xotcl/library/lib/
>
>
> Thanks
>
>
> On Fri, Nov 26, 2010 at 7:48 PM, Victor Mayevski<vitick_at_gmail.com> wrote:
>> Hello Gustaf,
>>
>> I have the following problem when trying to compile NX on freshly
>> installed Linux x86 system against latest TCL 8.6 from SourceForge
>> CVS.
>>
>> ./generic/nsf.c: In function ‘MethodDispatchCsc’:
>> ./generic/nsf.c:6959: error: too many arguments to function
>> ‘tclIntStubsPtr->tclNRRunCallbacks’
>> make: *** [nsf.o] Error 1
>>
>>
>> Thank you
>>

From: Koen Danckaert <koen_at_retarget.com>
Date: Thu, 07 Jul 2005 10:09:21 +0200

Hello,

The XOTcl manual says that an abstract method produces an error if it is called directly. It seems that this is not always the case. E.g., in the following example there is no error:

Class C
C abstract instproc a {}
C instproc b {} {my a}

C test
test b


>From an earlier discussion on the mailing list I found that predefined.xotcl contains the following code to avoid errors when an abstract method is invoked by "next":

Object instproc abstract {methtype methname arglist} {
  if {$methtype != "proc" && $methtype != "instproc"} {
    error "invalid method type '$methtype', \
        must be either 'proc' or 'instproc'."
  }
  [self] $methtype $methname $arglist "
    if {\[self callingproc\] != \[self proc\] &&
        \[self callingobject\] != \[self\]} {
      error \"Abstract method $methname $arglist called\"
    }
  "
}

I guess the test should be "||" instead of "&&" ?
But then, it doesn't do the right thing either, because callingproc is empty in case of an invocation by "next".


Regards,
Koen Danckaert