Details
Improvement
Open
Critical
Description
The following script demonstrates the problem with the System.Resources::ResourceReader and System.Resources::ResourceWriter included in the .NET 2.0+ Base Class Library:
{{import System}}
{{import System.IO}}
{{import System.Resources}}
{{import System.Text}}
{{using ms = MemoryStream(Encoding.UTF8.GetBytes("Parent, may I?")):}}
{{ using writer = ResourceWriter("mother-may-i.resources"):}}
writer.AddResource("mami?", ms)
writer.Close()
{{using writer = ResourceWriter("father-may-i.resources"):}}
{{ using reader = ResourceReader("mother-may-i.resources"):}}
for res in reader:
writer.AddResource("papi?", res.Value)
reader.Close()
writer.Close()
This means that, given any .resources file with a MemoryStream saved to it, the Boo compiler will fail because of code similar to this in the FileResource.cs of Boo.Lang.Compiler. The submitted patch allows for the Boo compiler to include the resources from such .resources files. For those that want to use Boo in their compiled XAML development, this functionality is necessary.
For further information regarding this issue, I've finished a thread on the BooLang group list at <http://groups.google.com/group/boolang/browse_frm/thread/7b244c6e6c3807e>.
Attachments
Activity
Scott,
I haven't received any communication regarding this patch since I created it a little over ten months ago.
Actually, none of my patches have made it into trunk, yet. I'm a Boo pariah. 
Curtis.
Curtis. >Actually, none of my patches have made it into trunk, yet. I'm a Boo pariah.
Eheh, actually yeah your patches completely slipped under the radar though they look completely worthy.
I feel guilty about it since I assigned BOO-1010 and BOO-1023 to myself and then forgot about it 
Maybe it's time to add another pariah committer to the party, Rodrigo?
As long as you add testcases to any compiler patch (such as BOO-1023) and run the testsuite successfully (nant test) everything's fine I guess 
Eheh, actually yeah your patches completely slipped under the radar though they look completely worthy.
I feel guilty about it since I assigned BOO-1010 and BOO-1023 to myself and then forgot about it
Maybe it's time to add another
As long as you add testcases to any compiler patch (such as BOO-1023) and run the testsuite successfully (nant test) everything's fine I guess
I've seen the work that you've done on behalf of the Boo project and having some patches slip under the RADAR is completely understandable.
In response to your comment, I'd incorporate some new test cases and ensure everything lit up green. That's the only way to make open source work well, right? 
As an avid fan of the language, I'd appreciate the chance to assist in its maintenance.
As an avid fan of the language, I'd appreciate the chance to assist in its maintenance.
Must have patch
.