Re: If VB.NET had CL macros....
- From: Jon Harrop <jon@xxxxxxxxxxxxxxxxx>
- Date: Sun, 30 Sep 2007 21:06:45 +0100
Dimiter "malkia" Stanev wrote:
Today I had to tweak one of our internal tools written in VB.NET, and
wish so much that there be macros... but I knew there ain't.
Here is the problem: on .NET if you want to update a GUI control from
the non-main thread, you have to make a delegate, prepare an invocation,
put the parameters and call it.
If you use F# then you just pass a function to the Invoke method:
form.Invoke(fun () -> ...)
This is also statically type checked, which Lisp macros are not.
Choice of Language Do Matter. I don't care whether it's .NET or any
other runtime, it's about the language. And VB.NET sucks big time!
Of course, but .NET is all about language interoperability, so you should be
able to develop new code in nicer languages like F# with minimal fuss.
--
Dr Jon D Harrop, Flying Frog Consultancy
http://www.ffconsultancy.com/products/?u
.
- References:
- If VB.NET had CL macros....
- From: Dimiter \"malkia\" Stanev
- If VB.NET had CL macros....
- Prev by Date: Re: Confused by behavior of LispWorks for code snippet
- Next by Date: Re: Static, dynamic and Lisp types.
- Previous by thread: Re: If VB.NET had CL macros....
- Next by thread: declare 64 bit integers?
- Index(es):
Relevant Pages
|
