381521 - unfrozen API usage in migration-to-frozen-linkage documentation

Status: RESOLVED FIXED

(Developer Documentation Graveyard :: General, defect)

Description

[James Schneider]

User-Agent:       Mozilla/5.0 (X11; U; Linux i686 (x86_64); en-US; rv:1.8.1.3) Gecko/20070309 Firefox/2.0.0.3
Build Identifier: not applicable

I would fix the documentation myself if I knew of a simple way to accomplish loading an nsIInputStream from string content (like the nsIStringInputStream) inside the frozen API.

(Some way that does not involve implementing an extended nsIInputStream interface.)

I asked around on #developers and #devmo and no-one was interested in this problem, so I will continue a little uncertainly, and perhaps foolishly.

Maybe the docs should just mention that the nsIStringInputStream isn't available in the headers in the sdk.  Maybe adding nsIStringInputStream to the frozen API should be bugged.  Maybe the appropriate unfrozen headers/includes should be referenced, with a note that such headers are only available in mozilla's source (and unavailable in the sdk).

Sorry to create a bug for such a trifle!  Maybe I can be forgiven....

Reproducible: Always

Steps to Reproduce:
not applicable
Actual Results:  
not applicable

Expected Results:  
not applicable

not applicable

Comment 1

[Nickolay_Ponomarev]

I don't think 'migrating to frozen linkage' means 'restricting yourself to frozen interfaces', but bsmedberg should know better.

Comment 2

[Benjamin Smedberg]

It doesn't, but we should probably note that that interface isn't frozen in the docs.

Comment 3

[Nickolay_Ponomarev]

James, do you have enough information to fix the wiki page now?

Comment 4

[James Schneider]

Maybe.  I thew something in there that aptly demonstrates my inadequacy in this regard.

Comment 5

[Nickolay_Ponomarev]

Thanks!