search for: return_typ

...FormatMessageA = KERNEL32.getFunction(''FormatMessageA'') LocalFree = KERNEL32.getFunction(''LocalFree'') public VERSION = ''1.0.6'' attr_reader :function_name attr_reader :prototype attr_reader :return_type attr_reader :dll_name def initialize(function, prototype=''V'', return_type=''L'', dll=''kernel32'') # Convert a prototype string to an array of characters if prototype.respond_to?(:split) prototype =...

...hundred values for m_id (see the SQL below). Because of the above error, I never see about two thirds of the results that ought to be produced. At the time that the error occurs, x contains the following SQL query: SELECT m_id,sale_date,YEAR(sale_date) AS sale_year,MONTH(sale_date) AS sale_month,return_type,0.0001 + DATEDIFF(return_date,sale_date) AS elapsed_time FROM `merchants2`.`risk_input` WHERE m_id = 361 AND return_type = 1 AND DATEDIFF(return_date,sale_date) IS NOT NULL; If I execute this SQL, I find the resultset is empty. So assigning the value returned by dbGetQuery to moreinfo works ONLY...

Hi all, I must have been testing windows-pr with an old version of windows-api, because now when I run ''rake test'' for windows-pr I get this: C:\Documents and Settings\djberge\workspace\windows-pr>rake test C:0:Warning: require_gem is obsolete. Use gem instead. (in C:/Documents and Settings/djberge/workspace/windows-pr) C:/ruby/lib/ruby/site_ruby/1.8/windows/api.rb:288:

I have a simple query as follows: "SELECT m_id,sale_date,YEAR(sale_date),WEEK(sale_date),return_type,DATEDIFF(return_date,sale_date) AS elapsed_time FROM risk_input" I can get, and view, all the data that that query returns. The question is, sale_date is a timestamp, and I need to call split to group this data by m_id and the week in which the sale occurred. Obviously, I would normally ne...

Hey folks, Here's a new spin of the pvops64 patch series. We didn't get that many comments from the last time, so it should be probably almost ready to get in. Heya! >From the last version, the most notable changes are: * consolidation of system.h, merging jeremy's comments about ordering concerns * consolidation of smp functions that goes through smp_ops. They're sharing

Hey folks, Here's a new spin of the pvops64 patch series. We didn't get that many comments from the last time, so it should be probably almost ready to get in. Heya! >From the last version, the most notable changes are: * consolidation of system.h, merging jeremy's comments about ordering concerns * consolidation of smp functions that goes through smp_ops. They're sharing

I must have missed something simple, but still, i don't know what. I obtained my basic data as follows: x <- sprintf("SELECT m_id,sale_date,YEAR(sale_date) AS sale_year,WEEK(sale_date) AS sale_week,return_type,0.0001 + DATEDIFF(return_date,sale_date) AS elapsed_time FROM `merchants2`.`risk_input` WHERE DATEDIFF(return_date,sale_date) IS NOT NULL") moreinfo <- dbGetQuery(con, x) I then made the data frame I want to use as follows: fun_m_id <- function(df) if (length(df$elapsed_time) > 5...

...ot landing pads. > > Hence, there is a need for introducing a new IR instruction. > > > The callbr instruction > ----------------- > > Our proposed approach is to introduce a new IR instruction named callbr > with the following syntax: > > callbr <return_type> <callee> (<argtype1> <arg1>, ...) to > label %normal or jump [label %transfer1, label %transfer2...] > > This syntax indicates that the callee may transfer the control flow to a > “normal” successor (generally the fallthrough in the source language code), > den...

...IR instruction. >>> >>> >>> The callbr instruction >>> ----------------- >>> >>> Our proposed approach is to introduce a new IR instruction named callbr >>> with the following syntax: >>> >>> callbr <return_type> <callee> (<argtype1> <arg1>, ...) >>> to label %normal or jump [label %transfer1, label %transfer2...] >>> >>> This syntax indicates that the callee may transfer the control flow to a >>> “normal” successor (generally the fallthrough in the...

Hi all, Just looking over fole_s_connect() in win32ole.c and I noticed this bit: hr = CLSIDFromProgID(pBuf, &clsid); ... hr = GetActiveObject(&clsid, 0, &pUnknown); ... hr = pUnknown->lpVtbl->QueryInterface( pUnknown, &IID_IDispatch, (void **)&pDispatch ); Using win32-api, that would be something like: IID_IUnknown =

....names.back().first; - if (nm.empty()) - return first; + // if (db.names.empty()) + // return first; + // if (!db.names.back()) + // return first; + node* return_type = nullptr; if (!db.parsed_ctor_dtor_cv && ends_with_template_args) { t2 = parse_type(t, last, db); if (t2 == t) return first; - if (db.names.size(...