Hmm...
I've never really had an issue with simply doing
My string is really really really really really really really really
really +
really really really really really really really really really really
really really +
really really really long.
The extra 's and +'s are a non-problem in my
tell me how the compiler could possibly sort this out? The only way is
for the compiler to hand off the entire process of TOKENIZING this
stream to the DSL provider for 'longString', which is an entirely
different architecture - right now all java parsers do the fairly
usual thing of
Casper: I don't think you grokked my point.
I'm saying it's impossible to build any java, vanilla or otherwise,
that can handle this. For the reasons I stated: You'd have to flip the
architecture upside down and resolve 'DSL' properly midway through
tokenizing it. Be aware that this
The issue goes a little deeper than your simple use case though. The
Java enterprise world, due to the lack of expression trees, has to
work with many thousands lines of embedded DSL (JPQL/HQL/SQL etc.).
This poses several problems:
- How do you format/indent it?
- How do you copy-paste between
Hi Folks,
After listening to Java Posse #275 I just HAD to share this Hindenburg
image.
http://www.flickr.com/photos/ulrichp/1362599/
Cheers
Kerry
PS: First post! -- the only way is up now :-)
--~--~-~--~~~---~--~~
You received this message because you are
Hi,
or just do it like html does it...
@DSL(lang=Brainfuck) {
/*
++[
+-]++.+.+++..+++.++.+++
..+++.--..+..
*/
}
javac ignores the comment, preprocessors like projectlombok.org could
do whatever they want with the comment (convert to
Casper Bang wrote:
The issue goes a little deeper than your simple use case though. The
Java enterprise world, due to the lack of expression trees, has to
work with many thousands lines of embedded DSL (JPQL/HQL/SQL etc.).
This poses several problems:
- How do you format/indent it?
- How
Annotations are the recommended way however, as it facilitates
validation. If you use em.createQuery(...) everything is late-bound
and even less type checked than using a namedQuery. For SQL though,
you are absolutely right but sadly SQL is no longer considered trendy.
/Casper
On 3 Sep., 01:53,
