> 
> Apparently you did not get a chance to comment on the change to
> vms.c:mybinmode() that was made quite a while ago.

Well, 

I was happy to get something that was at least running,
(over two 2 years ago, it was during the writing of my second perl script i
found that i needed binmode()
with a twist that it explicitly ruled out.
In needed to run binmode() on stdin. (cgilib).

So i modified the mybinmode and everything worked.
Then i got the perl source from a friend as i had 
no easy link with the internet to do bulky transfers.
(Cablemodem does change things....;-)

> 
> For anyone who relies on the current behavior of 
> VMS::Stdio::binmode() we
> could copy that code into a new xs routine.  For illustration 
> let us say
> that we turn what is the current VMS::Stdio::binmode() into a new xs
> routine called instead VMS::Stdio::oldbinmode(), then we could add your
> "ctx=bin" to the freopen in a new VMS::Stdio::binmode() and you'd be able
> to write your cross platform scripts in manner that you'd like.  Anyone
> who was dependent on the old behavior would need to call oldbinmode()
> rather than binmode().
> 
> Does anyone object to such a change?  Can anyone suggest a better name
> than "oldbinmode()", "binmode_sans_ctx_bin()", "binmode_with_ctx_bin()",
etc...?

legacy_binmode( ;-)  The term 'legacy' at least seems to
be appropriate in this case. Problem with a name change means 
that in the main script at leas something needs to appear like

sub binmode {
        legacy_binmode(@_);
}

to prevent changes to loaded modules. ?

regards,
Nico



-----------------------------------------------------------------
ATTENTION:
The information in this electronic mail message is private and
confidential, and only intended for the addressee. Should you
receive this message by mistake, you are hereby notified that
any disclosure, reproduction, distribution or use of this
message is strictly prohibited. Please inform the sender by
reply transmission and delete the message without copying or
opening it.

Messages and attachments are scanned for all viruses known.
If this message contains password-protected attachments, the
files have NOT been scanned for viruses by the ING mail domain.
Always scan attachments before opening them.
-----------------------------------------------------------------

Reply via email to