kimryo

Member
  • Content count

    218
  • Joined

  • Last visited

Community Reputation

100 Neutral

About kimryo

  • Rank
    Member
  1. I just wonder how it going and what extra recognition you have made about this company through the interview process. Em, I have interviewed with them recently, just want exchange some information if possible. Thanks in advance.
  2. [quote name='CableGuy' timestamp='1308580060' post='4825491'] I don't exactly get what you are trying to achieve. Are you trying to bind functions loaded from lua51.dll to a Lua state using Luabind? [/quote] Sorry, I updated question which should be more clear...
  3. luabind provides prefect object class accesses with type maps between lua and c++. Our project decides to load lua function APIs dynamically(Windows: LoadLibrary) from dll as lua51.dll. Since luabind call lua API functions directly, how to make luabind library call these lua API functions dynamically loaded from luaXX.dll? Thanks in advance.
  4. Thanks for reply. I'm just continue on seeking for the exact reason. Merry Christmas and happy new year.
  5. Quote:Original post by ApochPiQ It isn't strictly illegal, but it isn't a good idea, either. fprintf() is not type safe, and can introduce certain classes of security problems and nasty bugs if not used with extreme care. It exists in C++ solely for compatibility with legacy C code; just because it's there doesn't mean you should use it. That said: your code as posted is fine. Something else must be going on that's causing a crash. Ok, I understand the risk of using fprintf, for this example I just using it to output simple text strings, I don't think rare unsafe case been involved. And cause the main exe and dll are both very simple projects, elsewhere caused this bug also not likely possible. And cause the bug only appears when the fprintf call happens in another module other than exe itself, I just wonder if it's because the module change makes CRT lost some kind of environment(Maybe input/output redirections or something like that) which allows fprintf been called normally.
  6. Quote:Original post by LessBread Why are you using fprintf with stdout in a c++ app? fptinf(out,strMsg); //The application crashes here. Looks like a typo. Sorry for the typo, I've already corrected it. I'm just picked up a way to output string to console, and there is no rule says it is illegal to using fprintf and stdout in a c++ app...
  7. Hi, I got problem on output string to stdout of a console application. The detail situation is like following, in console application, int main(void){ //... fprintf(stdout,"OK"); // } The output is ok, but if I use something like this, it crashes with terrible shame, //In dll, void COutputStream::Output(FILE* out,const char* strMsg) { fprintf(out,strMsg); //The application crashes here. } //In console applciation. COutputStream out; out.Output(stdout,"ok"); And the call stack is -> Debug.dll@COutputStream::Output //crashed test.exe@main How I can make use of stdout of a console application as variable and pass it to other modules? Thanks in advance. [Edited by - kimryo on December 23, 2010 2:19:12 AM]
  8. Quote:Original post by frob How much bigger is 2X bigger? Jumping from 100KB to 200KB is nothing. Jumping from 12MB to 24MB would be a very different concern. Em, it's about 1.1MB grown to 2.2MB.
  9. Yes, the project is completely same thing, just upgrade them from VS2008 and compile, link. Maybe the libraries(CRT, MFC etc) provided by VS2010 are sort of quite different compare to VS2008's? Thanks.
  10. Thanks for your reply. Of course I mean both in release mode.
  11. I updated my development environment to Visual Studio 2010 recently, upgraded existing Visual Studio 2008 projects and compile and link, the same output exe file be about 2 times larger than VS2008 do, what's the difference between 2010 and 2008 on creating exe file? Thanks in advance.
  12. Ok, I think I know where is wrong, the newly updated gcc 4.2.1 is a 64bit version. And got many compatibility issues on my 32bit machine...
  13. Thanks Windryder, it is true we can made it this way, but I just wonder what changes come to the new version compare to old one that cause this error. And moreover, under older version of environment there is no include path and/or lib path need to be specified manually to compile my library; I need to figure out the right version of clock.h from a bundle of existing in miscellaneous folders and the referenced library file to do it in a manual manner. Thanks again.
  14. I have upgraded my Mac OSX to 10.6.2 and XCode to 3.2.1 to get a higher version of GCC, but the old program which compile and work fine under Mac OSX 10.5.8 and a lower version XCode can not compile now because clock.h header file can not be located, #include <kern/clock.h> //<= <kern/clock.h> no such file error. but the header is really exists on disk. Anybody encounter the same problem after update XCode? thanks. [Edited by - kimryo on December 30, 2009 7:24:19 AM]
  15. Hi, I'm totally new to cocoa framework and Mac OS X programming. Now I'm trying to link my own static library .a to a cocoa project, I have added the .a file into framework section, and set header file search directory, include library header file into project, but when building, the compiler report referenced function name can not be resolved. The .a static library was compiled by same GCC compiler under same Mac OS X system, and it can be linked to a sample program which compiled by GCC. Can anybody here give me any hint that what's wrong? Thanks in advance.