nPython, IronRuby,
F#<http://blogs.msdn.com/ironpython/archive/2008/02/25/ironpython-ironruby-and-f-openings-in-dev-test-and-pm.aspx>?
Visit http://blogs.msdn.com/ironpython/
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Ryan Riley
Sent: Thursday, May 01, 2008 6:49 AM
To: ironruby
On Thu, May 1, 2008 at 2:37 AM, Jimmy Schementi <
[EMAIL PROTECTED]> wrote:
> Splitting into different DLLs complicate things for Silverlight.
>
> On the desktop you can have the assembly loading be dynamic with a foo.rb
> wrapper for a library. However, Silverlight (today) requires the DLL would
[mailto:[EMAIL PROTECTED] On Behalf Of Tomas Matousek
> Sent: Wednesday, April 30, 2008 11:58 AM
> To: ironruby-core@rubyforge.org
> Subject: Re: [Ironruby-core] Opening up our tree to external committers
>
> That could be easily fixed by including 'zlib.rb', '
e.org
> Subject: Re: [Ironruby-core] Opening up our tree to external committers
>
> Splitting into different DLLs complicates things for Silverlight.
>
> On the desktop you can have the assembly loading be dynamic with a
> foo.rb wrapper for a library. However, Silverlight (today) re
this. Ideas?
~Jimmy
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:ironruby-core-
> [EMAIL PROTECTED] On Behalf Of Curt Hagenlocher
> Sent: Wednesday, April 30, 2008 8:50 PM
> To: ironruby-core@rubyforge.org
> Subject: Re: [Ironruby-core] Opening up our tree to external
>
On Wed, 30 Apr 2008 22:18:54 -0600, Tomas Matousek
<[EMAIL PROTECTED]> wrote:
Interesting has this e-mail just arrived?
Not sure. I've been away most of the day, so have no clue when it
officially arrived. The timestamp suggests it arrived soon after you sent
it, but that, quite obvious
er assembly names.
>
> Tomas
>
>
>
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of John Lam
> (IRONRUBY)
> Sent: Wednesday, April 30, 2008 7:01 AM
> To: ironruby-core@rubyforge.org
> Cc: Qing Ye
> Subject: [Ir
On Wed, 30 Apr 2008 19:38:02 -0600, Tomas Matousek
<[EMAIL PROTECTED]> wrote:
I need to figure out how to do loading of Ruby libraries contained in an
assembly, but I think it could be done.
Didn't we have this (or a very similar) conversation a while back?
--
/M:D
M. David Peterson
Co-Fo
er assembly names.
>
> Tomas
>
>
>
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of John Lam
> (IRONRUBY)
> Sent: Wednesday, April 30, 2008 7:01 AM
> To: ironruby-core@rubyforge.org
> Cc: Qing Ye
> Subject: [Ir
Michael Letterle:
> The only issue with this is we'll have to have some mechanism for them
> to be referenced with require 'zlib', requrie 'yaml', et. al. in order
> to maintain compatibility.
Agreed - we still have to build the require mechanism for libraries that are
hosted in different assemb
--
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Michael Letterle
Sent: Wednesday, April 30, 2008 9:06 PM
To: ironruby-core@rubyforge.org
Subject: Re: [Ironruby-core] Opening up our tree to external committers
Actually couldn't you have something like..
openssl.rb:
require &#x
On Wed, 30 Apr 2008 21:54:58 -0600, M. David Peterson
<[EMAIL PROTECTED]> wrote:
load
did I say load keyword? *YIKES*! I need to stop being such a language
whore. ;-)
I mean require and the related thread is @
http://rubyforge.org/pipermail/ironruby-core/2008-February/000858.html
-
Actually couldn't you have something like..
openssl.rb:
require 'IronRuby.Libraries.dll, version=xx, blahblabh'
and then just "require 'openssl'" in your app?
On Wed, Apr 30, 2008 at 11:58 PM, Curt Hagenlocher <[EMAIL PROTECTED]> wrote:
>
> On Wed, Apr 30, 2008 at 8:43 PM, Tomas Matousek
>
On Wed, Apr 30, 2008 at 8:43 PM, Tomas Matousek <
[EMAIL PROTECTED]> wrote:
> The only issue that needs to be solved is how to efficiently discover
> libraries embedded in .NET assemblies.
>
It's certainly the *primary* issue. :)
--
Curt Hagenlocher
[EMAIL PROTECTED]
On Wed, 30 Apr 2008 21:49:46 -0600, Curt Hagenlocher
<[EMAIL PROTECTED]> wrote:
This isn't dynamic, though. There has to be a single manifest for the
assembly that lists all the netmodules. I imagine it would be desirable
to be able to add a new library simply by copying it into the
app
On Wed, 30 Apr 2008 21:43:09 -0600, Tomas Restrepo <[EMAIL PROTECTED]>
wrote:
You can certainly do that way. I've worked with fairly large code
bases that do this, and you can certainly do the merging with link.exe
even.
Cool :) Glad to see my memory hasn't completely failed me! ;-)
That
On Wed, Apr 30, 2008 at 8:36 PM, M. David Peterson <[EMAIL PROTECTED]>
wrote:
> On Wed, 30 Apr 2008 21:14:23 -0600, Curt Hagenlocher <[EMAIL PROTECTED]>
> wrote:
>
> One advantage of having "one dll per library" is that you can make
> > decisions about which DLL to load based solely on the library
D] [mailto:[EMAIL PROTECTED] On Behalf Of Curt Hagenlocher
Sent: Wednesday, April 30, 2008 8:14 PM
To: ironruby-core@rubyforge.org
Subject: Re: [Ironruby-core] Opening up our tree to external committers
One advantage of having "one dll per library" is that you can make decisions
about whi
David,
> Why not meet half way: Generate netmodules who's primary purpose, if I am
> remembering correctly, is the ability to be merged together into a final
> assembly. Again, if I remembering correctly, the original idea was that you
> could have one team writing code in VB.NET and another in
On Wed, 30 Apr 2008 21:14:23 -0600, Curt Hagenlocher
<[EMAIL PROTECTED]> wrote:
One advantage of having "one dll per library" is that you can make
decisions about which DLL to load based solely on the library name.
Once you have multiple libraries per DLL, you need a more complicated
pro
8 4:40 PM
> To: ironruby-core@rubyforge.org
> Subject: Re: [Ironruby-core] Opening up our tree to external committers
>
>
> For consistency, can we also separate the other standard libraries such
> as digest, openssl, etc (that require explicit loading) into separate
> assemblies?
>
in an assembly, but I
think it could be done.
Tomas
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Wayne Kelly
Sent: Wednesday, April 30, 2008 4:40 PM
To: ironruby-core@rubyforge.org
Subject: Re: [Ironruby-core] Opening up our tree to external committers
For consistency, can we also separate the other standard libraries such as
digest, openssl, etc (that require explicit loading) into separate assemblies?
This of course, first requires us to be able to load such assemblies.
There will of course be an ever increasing set of such libraries, so it
I have been coding in C# for quite a while, I would love to chip in
Thanks.
- Original Message
From: Michael Letterle <[EMAIL PROTECTED]>
To: ironruby-core@rubyforge.org
Sent: Wednesday, April 30, 2008 1:47:14 PM
Subject: Re: [Ironruby-core] Opening up our tree to external comm
t;
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of John Lam
> (IRONRUBY)
> Sent: Wednesday, April 30, 2008 7:01 AM
> To: ironruby-core@rubyforge.org
> Cc: Qing Ye
> Subject: [Ironruby-core] Opening up our tree to external commi
-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of John Lam
(IRONRUBY)
Sent: Wednesday, April 30, 2008 7:01 AM
To: ironruby-core@rubyforge.org
Cc: Qing Ye
Subject: [Ironruby-core] Opening up our tree to external committers
Peter Bacon Darwin:
> It is not too late to implem
Peter Bacon Darwin:
> It is not too late to implement something like this. If a bit of work
> could be done on loading external IR libraries then projects could
> begin to be setup independently. This would have the multiple benefit
> of getting people to work on interesting and challenging proj
27 matches
Mail list logo
