On Tue, 2004-05-25 at 10:27, DaniÃl Mantione wrote:
> On Tue, 25 May 2004, Tom Jackson wrote:
>
> > On Tue, 2004-05-25 at 08:20, DaniÃÂl Mantione wrote:
> >
> > > To those unknown to the OpenACS compiler; OpenACS has its own adp parser
> > > which is way more powerfull than the AOLserver adp parser
> On Tue, 2004-05-25 at 08:20, Daniël Mantione wrote:
> Hmmm. Are we looking at the same code? I'm quite sure it converts the
> .adp & .tcl into a Tcl script, which it then evaluates. That would be
> contradictory with ns_adp_parse. Well, time to take a closer look at it,
Look at template::adp_
On Tue, 25 May 2004, Tom Jackson wrote:
> On Tue, 2004-05-25 at 08:20, Daniël Mantione wrote:
>
> > To those unknown to the OpenACS compiler; OpenACS has its own adp parser
> > which is way more powerfull than the AOLserver adp parser.
>
> Actually the OpenACS parser doesn't exist, ATS uses ns_re
On Tue, 2004-05-25 at 08:20, DaniÃl Mantione wrote:
> To those unknown to the OpenACS compiler; OpenACS has its own adp parser
> which is way more powerfull than the AOLserver adp parser.
Actually the OpenACS parser doesn't exist, ATS uses ns_register_adptag
and ns_adp_parse. One big problem with
Hi,
While we're talking about supporting alternative languages, debuggers &
a little about compilers. How about writing an OpenACS-styled
compiler that can compile a language into Tcl.
Ok, it might sound a bit silly perhaps and it definately won't be suitable
for a lot of languages (definately no
