Re: Interest in GSoC .NET and Mono integration

Nishant Gupta <[email protected]>
Newsgroups gmane.comp.gnome.mono.devel
Message-ID <CAFfBL0NdG52w2O0Fj42FC946ts8N7JGb6UWAvBpRdWF35MPETg@mail.gmail.com>
Is there a faster way of communication than via email?
@Ludovic - is there any specific time that you hang out on one of the mIRC
channels, i would love to talk to you there for sometime to ask all my
questions at once.

Thanks,
Nishant Gupta

On Sun, Mar 19, 2017 at 12:23 PM, Nishant Gupta <[email protected]>
wrote:

> Hi Ludovic,
>
> Thanks for your reply. So is my understanding correct that the end aim is
> to remove the Mono-specific FileStream type and replace it with the
> FileStream class defined in CoreFx (perhaps imported via a nuget package
> reference) ?
>
> What is the purpose of MonoIO ? And is there an equivalent in CoreFX?
>
> Does mono use a fork of the CoreFX code? Or is it imported directly via
> nuget?
>
> I think I want to go ahead with the FileStream project and would like to
> come up with a detailed plan of action that I can put in my proposal.
>
> Thanks,
> Rohit
>
> On Wed, Mar 15, 2017 at 9:02 AM, Ludovic Henry <[email protected]>
> wrote:
>
>> Hi Nishant,
>>
>> Our current implementation of System.IO.FileStream lives at
>> https://github.com/mono/mono/blob/master/mcs/class/corlib
>> /System.IO/FileStream.cs. It has strong dependencies on System.IO.MonoIO
>> which lives at https://github.com/mono/mono/blob/master/mcs/class/corlib
>> /System.IO/MonoIO.cs and which depends on the runtime for the different
>> icalls implemented in https://github.com/mono/mon
>> o/search?utf8=%E2%9C%93&q=filename%3Aw32file&type=Code
>> <https://github.com/mono/mono/search?utf8=✓&q=filename:w32file&type=Code>
>> .
>>
>> Out current implementation of System.Diagnostics.Process lives at
>> https://github.com/mono/mono/blob/master/mcs/class/System
>> /System.Diagnostics/Process.cs. The runtime implements the different
>> icalls in https://github.com/mono/mono/search?p=1&q=filename%3Aw32p
>> rocess&type=Code&utf8=%E2%9C%93
>> <https://github.com/mono/mono/search?p=1&q=filename:w32process&type=Code&utf8=✓>
>> .
>>
>> The end goal is to get rid of most of our mono-specific code both in
>> managed and in the runtime (System.IO.MonoIO, the w32process and the
>> w32file files), but we would first need to add support to CoreFX for the
>> different platforms that we support that they don't (Android, iOS, Haiku,
>> etc.)
>>
>> I would be the one to look over these 2 projects, so if you have any
>> question, I would be very happy to answer them.
>>
>> Thank you,
>> Ludovic
>>
>> *From:* Nishant Gupta [mailto:[email protected]
>> <[email protected]>]
>> *Sent:* Tuesday, March 14, 2017 12:22 AM
>> *To:* Xamarin FW Summer of Code <[email protected]>; mono
>> [email protected]
>> *Subject:* Re: Interest in GSoC .NET and Mono integration
>>
>> Hi,
>>
>> Any guidance here would be appreciated!
>>
>> Thanks,
>> Rohit
>>
>> On Sun, Mar 12, 2017 at 5:39 PM, Nishant Gupta <[email protected]>
>> wrote:
>>
>> Hi,
>> I am a grad student in India and I came across this board from the GSoC
>> idea page for Mono. I would love to help in the Microsoft .NET and Mono
>> integration initiative, as I have plenty of experience in C# and .NET
>> Framework/.NET Core along with other tools like NuGet. Please let me know
>> of a good way to get started!
>>
>> I was hoping to get in touch with Ludovic Henry and talk to him about a
>> plan of action. The projects that catch my eye include:
>>
>> 1) Import System.IO.FileStream from CoreFx
>> 2) Import Process from CoreFx
>>
>> I have a few boiling questions that i would love if someone could help
>> answer for me so I can start working on writing the proposal.
>>
>> It would also be great, if to get familiar in this area, someone could
>> point me to a few bugs which I can fix before GSoC to get my hands dirty.
>>
>>
>> Thanks,
>> Nishant
>>
>>
>>
>

_______________________________________________
Mono-devel-list mailing list
[email protected]
http://lists.dot.net/mailman/listinfo/mono-devel-list
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.