Re: [Rd] #include_next not found

Yes, this did the trick, thanks very much! I’m cc’ing r-devel just for the record. Roger Koenker r.koen...@ucl.ac.uk Department of Economics, UCL London WC1H 0AX. On Aug 7, 2019, at 4:55 PM, Steven Dirkse mailto:sdir...@gams.com>> wrote: Roger, Updating Xcode

Re: [Rd] #include_next not found

Hi Roger: This came up in the r-sig-mac list. Try removing the CPPFLAGS. Updates to Xcode appear to erase the headers where you are pointing to. The CRAN flags that Simon uses point elsewhere. Look at the r-sig-mac under topic "Xcode 10.3 and header flles". HTH, -Roy > On Aug 7, 2019,

[Rd] #include_next not found

Dear All, Just when I thought I had the plague of gfortran-9 under control, I made the tactical error of allowing my mac mini to “upgrade” to macOS 10.14.6 which apparently also upgraded Xcode to 10.3. In consequence I’m having difficulty building my packages. The current symptom is: /usr/lo

[Rd] NextMethod() and argument laziness

Hi all, I'd like to ask if the following behavior is a bug. To me it certainly feels surprising, at the very least. In this example, I would like to call NextMethod() from my `child` object, have `cols` be left untouched, and then substitute(cols) in the parent method. It works when you use a `pare