messages are considered statements by gcc and cannot be used safely; switching to a warning

Author: Enchufa2

ChangeLog

@@ -1,7 +1,7 @@
 2025-11-12 Iñaki Ucar <[email protected]>
 
 	* inst/include/Rcpp/macros/mask.h: Lay the ground for Rf_error masking
-	with a message at compilation time unless RCPP_NO_MASK_RF_ERROR is defined
+	with a warning at compilation time unless RCPP_NO_MASK_RF_ERROR is defined
 	* inst/include/RcppCommon.h: Include the previous file in the last place
 	* src/attributes.cpp: Use parentheses to protect call to Rf_error
 	* inst/tinytest/cpp/stack.cpp: Idem

inst/include/Rcpp/macros/mask.h

@@ -22,7 +22,7 @@
 
 #ifndef RCPP_NO_MASK_RF_ERROR
 #define Rf_error(...) \
-    _Pragma("message \"Use of Rf_error() instead of Rcpp::stop(). Calls \
+    _Pragma("GCC warning \"Use of Rf_error() instead of Rcpp::stop(). Calls \
 to Rf_error() in C++ contexts are unsafe: consider using Rcpp::stop() instead, \
 or define RCPP_NO_MASK_RF_ERROR if this is a false positive. More info:\n\
  - https://github.com/RcppCore/Rcpp/issues/1247\n\