Re: Rexsel — A simpler way of writing XSLT

Clearly I should have done some more homework on this, sighb&

The thing that prompted me to design Rexsel was all the
years spent on using OmniMark, then crossing over to XSLT,
and then needing to bpretty-printb some XSLT to make it a
bit more readable. Finally a light-bulb moment to realise I
could go the other way.

If anyone finds it an interesting approach then OK. Some of the
bextrab bits, such as the symbol table, I find useful on big scripts.
Certainly having a preprocessor stage can be tricky, something
I learnt to my cost with languages such as CORAL66.

I find the Rexsel compiler picks up a lot of errors before the XSLT
Is run, something that only intelligent XSLT editors (like oXygen)
offer.

But I take the point that once you get your head round the
XSLT syntax it is not a problem, after all 20+ years of doing it made
it second nature for me. Rexsel was somewhat of a quick experiment
to see if it could be done.

Hugh F-R

=================================
Hugh Field-Richards
hsfr@xxxxxxxxxxx
www.hopvine-music.com
www.paloose.org
www.rexsel.org

> On 30 Jun 2024, at 12:30, Michael Kay mike@xxxxxxxxxxxx
<xsl-list-service@xxxxxxxxxxxxxxxxxxxxxx> wrote:
>
> Join the club.
>
> There have been a number of attempts to do this over the years, most of
which have disappeared without trace. The most recent contribution was by
Fredrik OLhrstroLm at XML Prague 2024, see page 85 of