No registered users in community xowiki
in last 10 minutes
in last 10 minutes
Re: [Xotcl] xotcl::nonposArgs
From: Stefan Sobernig <stefan.sobernig_at_wu.ac.at>
Date: Thu, 16 Jul 2015 11:47:24 +0200
> PS: For novices the "mixture" of ::nx and ::xotcl is a bit unexpected, for
> example when serializing ::xotcl::MetaSlot on my OpenACS instance, one can
> see, that e.g. the superclass of ::xotcl::MetaSlot is ::nx::MetaSlot et
> cetera. My intuitive expectation was that both XOTcl 2 and NX exist as
> different languages within NSF, but more or less completely isolated from
> each other.
XOTcl building on NX (esp. slots) is hinted at some spots in the
migration guide at
https://next-scripting.org/xowiki/docs/nx/nx-migration/index1#_parameters_2.
> I suppose the reason is to keep the source code required to
> support the "legacy" XOTcl syntax as small as possible?
So it is.
Stefan
Date: Thu, 16 Jul 2015 11:47:24 +0200
> PS: For novices the "mixture" of ::nx and ::xotcl is a bit unexpected, for
> example when serializing ::xotcl::MetaSlot on my OpenACS instance, one can
> see, that e.g. the superclass of ::xotcl::MetaSlot is ::nx::MetaSlot et
> cetera. My intuitive expectation was that both XOTcl 2 and NX exist as
> different languages within NSF, but more or less completely isolated from
> each other.
XOTcl building on NX (esp. slots) is hinted at some spots in the
migration guide at
https://next-scripting.org/xowiki/docs/nx/nx-migration/index1#_parameters_2.
> I suppose the reason is to keep the source code required to
> support the "legacy" XOTcl syntax as small as possible?
So it is.
Stefan