Date: 2004-04-28T07:59:24
Editor: HowardLewisShip <[EMAIL PROTECTED]>
Wiki: Jakarta HiveMind Wiki
Page: NotXMLProposal
URL: http://wiki.apache.org/jakarta-hivemind/NotXMLProposal
no comment
Change Log:
------------------------------------------------------------------------------
@@ -160,19 +160,20 @@
{{{
. . . invoke-factory (service-id=foo.bar.BeanShellServiceFactory)
{
- script <<
+ script {
+<<
return new MyServiceImpl(. . .);
->>;
+>> }
} . . .
}}}
-The {{{<< . . . >>}}} syntax is something I'm looking to add into my SDL
prototype. I like the idea of scripting, but I like line precise error
reporting much, much more. I also think scripting introduces further problems
if and when there is tool support (the tool has to parse the script, which is
not nearly so regular as the SDL or XML).
+The {{{<< . . . >>}}} syntax fills the same role as CDATA sections in XML ...
everyting inside the delimiters is passed through as-is. I like the idea of
scripting, but I like line precise error reporting much, much more. I also
think scripting introduces further problems if and when there is tool support
(the tool has to parse the script, which is not nearly so regular as the SDL or
XML).
HarishKrishnaswamy: Why do you think line precise error reporting has to be
sacrificed with a scripting language? why something like the script above would
n't work? With a scripting language the parser is already built, the tool will
simply have to work with the AST (much simpler than working with the raw
grammer). Yes, I could use a BeanShellServiceFactory, but I am still not seeing
the benefit of SDL.
-HowardLewisShip: I must be, from ignorance, misunderstanding the {{{ while
(!parser.Line() { node = parser.popNode() ... }}} stuff. I was looking at that
as "read a line, execute a line", but that's obviously not what it is doing.
I'd be interested in seeing a real, formatted example, and more detailed notes
about how line-precise error reporting is maintained. I'm not completely
stubborn, but if you want to change my mind (especially considering who ends up
doing the most work) you have to work ''really hard'' ... but when this has
happened in the past, I
+HowardLewisShip: I must be, from ignorance, misunderstanding the {{{ while
(!parser.Line()) { node = parser.popNode() ... } }}} stuff. I was looking at
that as "read a line, execute a line", but that's obviously not what it is
doing. I'd be interested in seeing a real, formatted example, and more detailed
notes about how line-precise error reporting is maintained. I'm not completely
stubborn, but if you want to change my mind (especially considering who ends up
doing the most work) you have to work ''really hard'' ... but when this has
happened in the past, I
will fully embrace the final solution (witness: implicit components, etc., in
Tapestry 3.0 --- which started with a flame by Marc Fluery).
IliaHonsali: I suggest to keep using xml for conf files, the main purpose of
xml is to store data not to be easy to view, so, once hivemind come stable
"someone" will make gui to mask the xml (with eclipse it'is easy), xml is also
something usual that not scare newbies like me.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
