Terence Parr wrote:
dhaval yoganandi wrote:I was thinking internal languages of companies as DSL.
By internal, Martin Fowler means written with in the constraints of another language. More like a library than new syntax.
Dang. I thought I was getting the hang of it. So are you saying that when creating a DSL in Java we need to pass one or more Strings to an interpreter/renderer so that we're not using the Java syntax?
Burk Hufnagel wrote:
dhaval yoganandi wrote:Then the question is why they prefer DSL ?
Does that make sense?
Burk Hufnagel wrote:Dhaval,
Sorry about misspelling your name (I went back and edited the post to correct it) I guess I wasn't quite awake when I first replied.
I think DSLs and proprietary languages can be a good thing for a company, but at the same time they definitely have a cost. Other than previous employees, you won;t find people who already know the language you're using so you have to spend the time and money to train each new developer. In addition, some excellent developers won't be interested in the job because the knowledge and skill they gain with the proprietary language is mostly useless to other potential employers. Another concern is that after training your new hire, it may be that they aren't very good with the new language because the programming model just doesn't fit with how they think - though you can probably screen those folks out during the hiring process.
All in all I see it as another trade-off.
Burk Hufnagel wrote:Dhavai,
That's a trap we as developers can fall in to, but it's not fair to blame the DSL. I've worked for several companies that had their own proprietary language, and the trick I've found is to either be on projects that don't use it or to keep involved in a community (user group) that's focused on a general purpose language like C or Java.
Tim McGuire wrote:It seems pretty clear that the tables are not identical. Could you post the DDL for each table so we can compare them?
David O'Meara wrote:the error message is pretty informative. have you looked at that?
EXCEPTION IN RESULTSET WRAPPER WHILE EXECUTING QUERY: java.sql.SQLException: All tables in the MERGE table are not identically definedjava.sql.SQLException: All tables in the MERGE table are not identically defined
at com.mysql.embedded.api.api.mysql_real_query(Native Method)
Paul Clapham wrote:But isn't the GNU JavaMail API the same as Sun's JavaMail API? In which case you're just looking at bugs in the GNU version. And based on what Ulf says, those bugs aren't going to be fixed unless you do it yourself.
Ulf Dittmer wrote:The tutorial talks about multipart at length. The MimeMultipart javadocs go into more detail; specifically, check out the setSubType method.