Beefy Boxes and Bandwidth Generously Provided by pair Networks
Your skill will accomplish
what the force of many cannot
 
PerlMonks  

Re: Improve perlfaq5: How can I translate tildes (~) in a filename?

by halley (Prior)
on Jun 10, 2008 at 18:47 UTC ( #691304=note: print w/replies, xml ) Need Help??


in reply to Improve perlfaq5: How can I translate tildes (~) in a filename?

I'm not sure what the actual beef might be with that solution. Here is an explanatory paragraph to introduce the FAQ, which may be all it needs.
On systems which follow Unix shell conventions, a user may supply a pathname with the tilde (~) character to refer to the user's home directory (e.g., <c>~/file</c>), or another user's home directory (e.g., <c>~user/file</c>). This works in many Unix shells, but often does not work in scripts or applications by default. If your script would like to support this convenient but optional notation, then the built-in <c>getpwnam()</c> function and <c>%ENV</c> hash are the best places to refer, or use the newer globbing features that support them automatically.
On non-Unix systems, it might be broken. On non-Unix systems, though, the users are less likely to want to use Unix-isms like shell notations that scan /etc/passwd for data. Wrap the whole thing in a $^O if you like.

--
[ e d @ h a l l e y . c c ]

Log In?
Username:
Password:

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://691304]
help
Chatterbox?
[choroba]: yeah, sounds like one of the strings is not flagged as UTF-8
[choroba]: which usually means its input wasn't handled correctly
[Corion]: choroba: Yeah, I think that would be the good solution
[LanX]: I suspect the first string which comes from the DB ...
[LanX]: ... but this part is already in production for a year now
[Corion]: LanX: The "good" approach here would be to use the appropriate DBI parameters to make the driver decode strings properly. But that will have a ripple-on effect of messing up all the places where manual decoding happens ;)
[LanX]: which means albeit being broken UTF8 it'll be handled correctly
[LanX]: and the problem only occurs since we changed the emails to base64
[LanX]: my main problem will be to cnvince my colleagues that our productive code is broken oO ... so in the end I will just make a workaround :-/
LanX hates UTF8 for causing knots in his brain and stomach

How do I use this? | Other CB clients
Other Users?
Others cooling their heels in the Monastery: (9)
As of 2017-01-16 14:00 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?
    Do you watch meteor showers?




    Results (150 votes). Check out past polls.