Why isn't MutableString.version called MutableString.Version? That would be the
consistent naming convention, right?
The current versioning implementation is not thread-safe. A thread-safe
implementation would require using InterlockedCompareAndExchange to update
version, right? If we are
Web Reservoir wrote:
Hi,
May i know, how many months are we still far from IronRuby 1.0...?
It was july 2008 previously. It seems its delayed. I am also waiting for
a confirmed date.
I understand Asp.Net MVC preview 4 will support IronRuby.
Asp.Net MVC 4 is scheduled to be in this
Hi,
It would be great to have a small and working starter kit with Asp.Net
MVC with IronRuby, from one of those currently available starter kits
for C# and Vb.net.
Since Asp.Net MVC preview 4 supports IronRuby, there is nothing wrong in
expecting some working solutions to learn more.
--
The potential problem to this would be that the starter kits are based
on webforms, as such porting them to MVC and IronRuby would be a big
task without much benefit?
Personally, I'm not a great fan of massive starter kit projects as
they trend to take too long to get your head around. Plus they
Hmm... now that I think about it, it's really only thread safe enough if you
restrict yourself to 2 threads. With three threads performing simultaneous
access, I can work out a sequence that breaks.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Curt
The ASP.NET MVC questions should be asked on the ASP.NET MVC forums.
The current plan is to ship IronRuby early next year.
Thanks,
-John
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Rahil Kumar
Sent: Wednesday, July 09, 2008 4:54 AM
To:
IronRuby's Rakefile and context.rb calls
UserEnvironment.find_executable 'ruby.exe',
which is hopelessly wrong. (No 'ruby.exe' on Linux, etc.) I wrote a
patch to correct
this.
http://sparcs.kaist.ac.kr/~tinuviel/download/IronRuby/patch-find-executable
Please apply.
--
Seo Sanghyeon
If MRI strings are not meant to be thread-safe, we don't have to worry about
it. Has anyone confirmed that the intent is to move the synchronization
responsibility to user code? Note that Python lists guarantee thread-safety and
so IronPython had to do work to support that.
Regarding Curt's
If we use Interlocked.Increment and Interlocked.Decrement, it will
automatically wrap the value around without throwing an exception.
I don't generally think about cache coherency issues, so Shri is absolutely
right. I assume a lock statement would generate the appropriate memory
barriers?
Why not fork the RubySpec project on GitHub, apply your patches and point us
at your forked GIT repository? That way we can easily see the changes using
the tools on GitHub.
Pete
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Jim Deville
Sent: Wednesday,09 July 09, 2008 21:21
Hi
I don't really know if this is an appropriate discussion but here it goes.
Ruby and Xaml at first sight a DSL is very appropriate to get rid of the xml
syntax. I'm all for that :) However the price you pay is that at that moment
only developers can change the design of the application. Blend
11 matches
Mail list logo
