Bug 24999 - InputStreamReader takes in System.IO.Stream instead of Java.IO.InputStream
Summary: InputStreamReader takes in System.IO.Stream instead of Java.IO.InputStream
Status: RESOLVED ANSWERED
Alias: None
Product: Android
Classification: Xamarin
Component: BCL Class Libraries ()
Version: 4.20.0
Hardware: PC Windows
: --- normal
Target Milestone: ---
Assignee: dean.ellis
URL:
Depends on:
Blocks:
 
Reported: 2014-12-02 11:39 UTC by Jeremy Kolb
Modified: 2015-01-05 07:08 UTC (History)
2 users (show)

Tags:
Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.


Please create a new report on Developer Community or GitHub with your current version information, steps to reproduce, and relevant error messages or log files if you are hitting an issue that looks similar to this resolved bug and you do not yet see a matching new report.

Related Links:
Status:
RESOLVED ANSWERED

Description Jeremy Kolb 2014-12-02 11:39:58 UTC
The constructor for InputStreamReader is:

[Register(".ctor", "(Ljava/io/InputStream;)V", "")]
public InputStreamReader(Stream @in)
{
...
}

But in this case Stream is resolving to System.IO.Stream instead of Java.IO.InputStream
Comment 1 Jonathan Pryor 2014-12-02 15:16:24 UTC
This is by design. We "hide" many Java types in public APIs to more readily consumable .NET equivalents. In this case, we're replacing InputStream with System.IO.Stream (similarly OutputStream), we'll replace many Android XML parser types with System.Xml equivalents, etc.

This is to facilitate code reuse, so that you can more easily pass existing .NET code to Java code.

...though we should probably expose the "original" Java members for methods and constructor parameters.
Comment 2 Sadik Ali 2015-01-05 07:08:15 UTC
As per the comment 1, this is by design. Hence I am marking this issue as "Resolved Answered".