[dev-context] beta

2011-12-21 Thread Hans Hagen

Hi Wolfgang et al,

I cleaned up mkiv'd pack-rul, meta-ini, anch-pgr etc and for sure there 
have been bugs introduced. A couple of mkii artefacts have been removed 
and some speedups were possible (important as framed is a core macro so 
especially backgrounds have been redone a bit). I still have to look 
into framed using the commandhandler but let's first check if the 
current variant is ok.


I'll put a beta on the ftp server, so you might want to test,

Hans

PS. A few observations: \vbox -> hbox (less callback overhead), kern -> 
glue (less memory and calback overhead) i.e. some boxing has changed but 
hopefully for the best.


PS. I hope that in 2012 I've redone all the code (consistency, mkiv'd, 
namespaces, etc).



-
  Hans Hagen | PRAGMA ADE
  Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com
 | www.pragma-pod.nl
-
___
dev-context mailing list
dev-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/dev-context


Re: [dev-context] beta

2011-12-21 Thread Wolfgang Schuster

Am 21.12.2011 um 23:26 schrieb Hans Hagen:

> Hi Wolfgang et al,
> 
> I cleaned up mkiv'd pack-rul, meta-ini, anch-pgr etc and for sure there have 
> been bugs introduced. A couple of mkii artefacts have been removed and some 
> speedups were possible (important as framed is a core macro so especially 
> backgrounds have been redone a bit). I still have to look into framed using 
> the commandhandler but let's first check if the current variant is ok.
> 
> I'll put a beta on the ftp server, so you might want to test,

pack-rul.mkiv \startframed nice:)

Tested with a large document and a few test files and they run fine.

> Hans
> 
> PS. A few observations: \vbox -> hbox (less callback overhead), kern -> glue 
> (less memory and calback overhead) i.e. some boxing has changed but hopefully 
> for the best.
> 
> PS. I hope that in 2012 I've redone all the code (consistency, mkiv'd, 
> namespaces, etc).

Can we now consider the following prefixes for registers as the suggested 
method to name them:

\newcount: \c_…
\newdimen: \d_…
\newskip: \s_…
\newbox: \b_…
\newtoks: \t_…

Wolfgang
___
dev-context mailing list
dev-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/dev-context


[dev-context] type-mar.mkvi

2011-12-21 Thread Wolfgang Schuster
Hi Hans,

the \margindata commands still used the no longer available \dosetupstrut 
command.

Wolfgang
___
dev-context mailing list
dev-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/dev-context


Re: [dev-context] beta

2011-12-21 Thread Aditya Mahajan

On Thu, 22 Dec 2011, Wolfgang Schuster wrote:


PS. I hope that in 2012 I've redone all the code (consistency, mkiv'd, 
namespaces, etc).


Can we now consider the following prefixes for registers as the suggested 
method to name them:

\newcount: \c_…
\newdimen: \d_…
\newskip: \s_…
\newbox: \b_…
\newtoks: \t_…


I hope you don't converge to LaTeX3 syntax after all the rewrite is over 
:)


Aditya___
dev-context mailing list
dev-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/dev-context


Re: [dev-context] beta

2011-12-21 Thread Wolfgang Schuster

Am 22.12.2011 um 01:19 schrieb Aditya Mahajan:

> On Thu, 22 Dec 2011, Wolfgang Schuster wrote:
> 
>>> PS. I hope that in 2012 I've redone all the code (consistency, mkiv'd, 
>>> namespaces, etc).
>> 
>> Can we now consider the following prefixes for registers as the suggested 
>> method to name them:
>> 
>> \newcount: \c_…
>> \newdimen: \d_…
>> \newskip: \s_…
>> \newbox: \b_…
>> \newtoks: \t_…
> 
> I hope you don't converge to LaTeX3 syntax after all the rewrite is over :)

Don’t you already use your own syntax?

Wolfgang
___
dev-context mailing list
dev-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/dev-context


Re: [dev-context] beta

2011-12-21 Thread Aditya Mahajan

On Thu, 22 Dec 2011, Wolfgang Schuster wrote:



Am 22.12.2011 um 01:19 schrieb Aditya Mahajan:


On Thu, 22 Dec 2011, Wolfgang Schuster wrote:


PS. I hope that in 2012 I've redone all the code (consistency, mkiv'd, 
namespaces, etc).


Can we now consider the following prefixes for registers as the suggested 
method to name them:

\newcount: \c_…
\newdimen: \d_…
\newskip: \s_…
\newbox: \b_…
\newtoks: \t_…


I hope you don't converge to LaTeX3 syntax after all the rewrite is over :)


Don’t you already use your own syntax?


No. I reverted to the new internal syntax last week. Now I am using 
\modulename@macro_name etc.


Aditya___
dev-context mailing list
dev-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/dev-context


Re: [dev-context] beta

2011-12-21 Thread Wolfgang Schuster

Am 22.12.2011 um 01:19 schrieb Aditya Mahajan:

> On Thu, 22 Dec 2011, Wolfgang Schuster wrote:
> 
>>> PS. I hope that in 2012 I've redone all the code (consistency, mkiv'd, 
>>> namespaces, etc).
>> 
>> Can we now consider the following prefixes for registers as the suggested 
>> method to name them:
>> 
>> \newcount: \c_…
>> \newdimen: \d_…
>> \newskip: \s_…
>> \newbox: \b_…
>> \newtoks: \t_…
> 
> I hope you don't converge to LaTeX3 syntax after all the rewrite is over :)

No, i think there code is too complicated to understand without an knowledge 
about the syntax.

The original purpose of the underscore in context was for modules to provide a 
namespace for macros. With the prefixes for registers there is a easy method to 
see whether a register is a counter, a dimension or a box (i know \c_… could 
also stand for a conditional and \s_… for a signal) but they are only used for 
internal code.

All public command which can be used should remain without underscores, e.g. 
\doifelsenextbgroup etc.

Wolfgang
___
dev-context mailing list
dev-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/dev-context