fopen_input works, as does fopen_output, however I don't understand WHY.
There should be two copies of these functions each: one for C FILE* and
one for C++ iostreams. It happens the implementation instance for C++
iostreams is bugged and uses C FILE* by mistake, but this shouldn't
be related to the fact that the binding
var f = fopen_input "filename";
binds without ambiguity.. It should be ambiguous.
I ran across this when in flx_iscr I was thinking that if no input
filename is given to use standard input (a common unix idiom).
Then I wanted to find out which one to use (the C stdin or the
C++ cin) that would work with the rest of the code. That would
be determined by which fopen_input is called ..
The existence of both these functions with the same name isn't a bug!
You're supposed to choose which using explicit qualification like this:
Input_text_file[ifile]::fopen_input ...
or similar.
Hmm ...
--
john skaller
skal...@users.sourceforge.net
http://felix-lang.org
------------------------------------------------------------------------------
Rapidly troubleshoot problems before they affect your business. Most IT
organizations don't have a clear picture of how application performance
affects their revenue. With AppDynamics, you get 100% visibility into your
Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro!
http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk
_______________________________________________
Felix-language mailing list
Felix-language@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/felix-language
