From: Samuel Krempp (krempp_at_[hidden])
Date: 2004-01-23 11:17:50
le Thursday 22 January 2004 22:58, krempp_at_[hidden] écrivit :
> ideally, this option would have 3 settings :
> 1. ban all non ascii
> and 1' : warn instead of ban
> 2. ban characters that are found equal to any of bjam-special char in the
> current locale (saves the user from hidden traps)
> and 2' - just warn
> 3. dont restrict the charset in any way.
There might be a simple way to protect the user from stray characters with
felxibility without explicitly coping with locale work (it often turns to
be a real pain because you can't assume anything from most systems's
locales. on my linux, isspace(0xA0) returns false for a locale using
iso-8859-1 charset encoding while it should be true. In fact isalnum() even
How does bjam treat quoted strings ?
has the same effect when parsed as
, right ?
then bjam could ban all non-ascii chars out of quoted strings.
then people can use non-ascii chars as they want, inside quoted strings.
-> no risk of some special chars invisibly tricking the user
-> keeps all flexibility.
Boost-Build list run by bdawes at acm.org, david.abrahams at rcn.com, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk