Hi, First of all, I truly apologise for the late reply.
ons, 22 07 2009 kl. 16:27 -0500, skrev Jeff Keacher: > Long story short, it looks like a macro in sockets.cc is using the > defunct FS ## name convention instead of the more recent G ## name > convention. Making that change and rebuilding the package results in > socket constants that work as they should. I've made this change, although I admit that I don't understand it. Thanks for looking into the issue. > There might be a better place to fix this, and I'm not sure how it > will impact the backwards compatibility of octave-sockets, but it's a > starting point. I don't understand the code in question, so I don't really know. But all help is appreciated ;-) Søren ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ Octave-dev mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/octave-dev
