You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@velocity.apache.org by Daniel Rall <dl...@finemaltcoding.com> on 2000/12/13 00:11:33 UTC
Re: cvs commit: jakarta-velocity/xdocs vtl-reference-guide.xml texen.xml install.xml
"Geir Magnusson Jr." <ge...@optonline.net> writes:
> Jon Stevens wrote:
> >
> > on 12/12/2000 1:36 PM, "Jose Alberto Fernandez" <JF...@viquity.com>
> > wrote:
> >
> > > Why? I see no need for the "(" be together with the directive name.
> > > I see no need for such rigid grammar, I do not see the current grammar to
> > > be ambiguous or anything else. Why does this smplify explaining the
> > > directives?
> > >
> > > Jose Alberto
> >
> > I agree.
> >
> > #foo (
> > #foo (
> > #foo(
> >
> > should all work.
>
> The do all work. We are talking about documentation...
>
> For the documentation, which was the original post of this thread, a
> single consistant style might be nice and easier to read.
I agree with you, but there should be a note saying that variations
are in fact functional. :)
Daniel
Re: cvs commit: jakarta-velocity/xdocs vtl-reference-guide.xml
texen.xml install.xml
Posted by "Geir Magnusson Jr." <ge...@optonline.net>.
Daniel Rall wrote:
>
> "Geir Magnusson Jr." <ge...@optonline.net> writes:
>
> > Jon Stevens wrote:
> > >
> > > on 12/12/2000 1:36 PM, "Jose Alberto Fernandez" <JF...@viquity.com>
> > > wrote:
> > >
> > > > Why? I see no need for the "(" be together with the directive name.
> > > > I see no need for such rigid grammar, I do not see the current grammar to
> > > > be ambiguous or anything else. Why does this smplify explaining the
> > > > directives?
> > > >
> > > > Jose Alberto
> > >
> > > I agree.
> > >
> > > #foo (
> > > #foo (
> > > #foo(
> > >
> > > should all work.
> >
> > The do all work. We are talking about documentation...
> >
> > For the documentation, which was the original post of this thread, a
> > single consistant style might be nice and easier to read.
>
> I agree with you, but there should be a note saying that variations
> are in fact functional. :)
Maybe we could have random amounts of spaces inserted at render time in
the directive examples in the docs on the site :)
(And they are functional...)
geir
--
Geir Magnusson Jr. geirm@optonline.com
Velocity : it's not just a good idea. It should be the law.
http://jakarta.apache.org/velocity
Re: cvs commit: jakarta-velocity/xdocs vtl-reference-guide.xml
texen.xml install.xml
Posted by Christoph Reck <Ch...@dlr.de>.
I mean't a consistent documentation giving the hint of a recommended
coding style.
> > > #foo (
> > > #foo (
> > > #foo(
> > >
> > > should all work.
> >
> > The do all work. We are talking about documentation...
> >
> > For the documentation, which was the original post of this thread, a
> > single consistant style might be nice and easier to read.
>
> I agree with you, but there should be a note saying that variations
> are in fact functional. :)
+1 Sure, the doc should contain a hint that any spaces between the
directive and opening paren are optional (but beware - were not
speaking whitespaces! - '\n' is not allowed!).
P.S. I forgot to state that the velocimacro declaration example int
the doc is buggy:
#macro( vmname arg1 arg2 )
should be:
#macro( vmname $arg1 $arg2 )
to be compatible with the #set declaration...
:) Christoph