tag:blogger.com,1999:blog-7290642316743338665.post1332821131595829578..comments2023-09-20T05:23:44.886-05:00Comments on behind the times: Is it really a domain specific language?Hamlet D'Arcyhttp://www.blogger.com/profile/04008870357169725586noreply@blogger.comBlogger9125tag:blogger.com,1999:blog-7290642316743338665.post-29907476585341943372010-02-22T21:25:38.553-06:002010-02-22T21:25:38.553-06:00This comment has been removed by a blog administrator.木須炒餅Jerryhttps://www.blogger.com/profile/11813785579307536291noreply@blogger.comtag:blogger.com,1999:blog-7290642316743338665.post-80782685837823579802008-08-19T14:24:00.000-05:002008-08-19T14:24:00.000-05:00This comment has been removed by a blog administrator.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-7290642316743338665.post-74599168281184670652008-07-17T12:42:00.000-05:002008-07-17T12:42:00.000-05:00"A domain specific language is a vocabulary for di..."A domain specific language is a vocabulary for discussing a specific problem you have. Excel functions are a darn good vocabulary for working with spreadsheet data. They may not be easy to learn, but they are an extremely powerful language to solve the problem of expressing complex formulas in spreadsheets."<BR/><BR/>By this example, can we infer "Java" is a DSL for the problem of programming? I think we got to see the problem domain in perspective. In the end, it all boils down to what one thinks is the domain that they are dealing with. <BR/><BR/>I feel fluent interfaces just a way to make the languages read easier, probably targeting domains with users who are not realy programmers, but say analysts and domain expects.<BR/><BR/>BTW, great blog post.<BR/><BR/>-AravindAravind Ajad Yarrahttps://www.blogger.com/profile/08983476122353391285noreply@blogger.comtag:blogger.com,1999:blog-7290642316743338665.post-75207617190166114382008-07-17T12:40:00.000-05:002008-07-17T12:40:00.000-05:00This comment has been removed by the author.Aravind Ajad Yarrahttps://www.blogger.com/profile/08983476122353391285noreply@blogger.comtag:blogger.com,1999:blog-7290642316743338665.post-24760266439303935602008-05-18T18:21:00.000-05:002008-05-18T18:21:00.000-05:00Great blog with lots of useful information and exc...Great blog with lots of useful information and excellent commentary! Thanks for sharing. <A HREF="http://www.1-satellite-tv-facts.com/Satellite-DSL.html" REL="nofollow">DSL high speed internet access</A>vAnonymousnoreply@blogger.comtag:blogger.com,1999:blog-7290642316743338665.post-49592592010244525432008-01-10T04:44:00.000-06:002008-01-10T04:44:00.000-06:00Totally agree that the term DSL is sufferting from...Totally agree that the term DSL is sufferting from a very dangerours abuse. Industry’s big players are looking for the next big thing and since visionaries are talking about this all sort of ‘DSL toolkit’ pops up. I’ve been to one presentation by Neal Ford on the waffles example and eve not being something geeky it is a pretty good way of teaching about DSLs. Actually I found that talking in examples is better to get make people understand why DSLs are a natural way of thinking.<BR/><BR/>I have a different view of Fluent Interfaces but I liked yours. I only wouldn’t attach that with sentences, Fluent Interfaces are readable. Some times this means an English-like sentence, sometimes not. <BR/><BR/>I think EasyMock uses <A HREF="http://fragmental.tw/research-on-dsls/language-adaption/" REL="nofollow">language adaptation</A> and JMock uses DSL. JMock has evolved an internal language fr years.<BR/><BR/>Cheers<BR/>Phillip Calcado<BR/>http://fragmental.twPai Ricohttps://www.blogger.com/profile/09131234192943604958noreply@blogger.comtag:blogger.com,1999:blog-7290642316743338665.post-57201333234968213022008-01-10T02:24:00.000-06:002008-01-10T02:24:00.000-06:00Classical strawmen attack."Using EasyMock's API in...Classical strawmen attack.<BR/><BR/>"Using EasyMock's API in my project didn't solve the problem of writing better unit tests, it created a problem of how to work with record/playback frameworks. Since this fluent interface does not provide a vocabulary for unit testing, it is therefore not a DSL."<BR/><BR/>EasyMock is not a DSL for unit testing but for mock expectations. So obviously it can't solve the unit test problem. And it can't be a unit test DSL. But it does solve the mock expectation problem by introducing a new language to setup expectation specific to the domain of mocks. Therefore it's a mock DSL. qed.<BR/><BR/>Peace<BR/>-stephan<BR/><BR/><BR/>-- <BR/>Stephan Schmidt :: stephan@reposita.org<BR/>Reposita Open Source - Monitor your software development<BR/>http://www.reposita.org <BR/>Blog at http://stephan.reposita.org - No signal. No noise.Stephan.Schmidthttps://www.blogger.com/profile/03845125686370893937noreply@blogger.comtag:blogger.com,1999:blog-7290642316743338665.post-76984356476215328742007-10-21T12:10:00.000-05:002007-10-21T12:10:00.000-05:00One suggestion is to not use mocks for everything....One suggestion is to not use mocks for everything. http://hamletdarcy.blogspot.com/2007/10/mocks-and-stubs-arent-spies.html<BR/><BR/>Otherwise, some of the behavior driven development test frameworks look promising. I'll try to look into this more in the future and formulate a better answer. (I don't have a good one just now!)Hamlet D'Arcyhttps://www.blogger.com/profile/04008870357169725586noreply@blogger.comtag:blogger.com,1999:blog-7290642316743338665.post-6846850533570472402007-10-18T22:16:00.000-05:002007-10-18T22:16:00.000-05:00Great blog post! I really like your analogy betwe...Great blog post! I really like your analogy between ordering food and easymock. What changes would you make to help bring mock testing to a DSL?Unknownhttps://www.blogger.com/profile/03751361435741375555noreply@blogger.com