search for: fufil

Displaying 8 results from an estimated 8 matches for "fufil".

Did you mean: fulfil
2010 Mar 24
1
Release plans
...t plugin, DBus, has finally been ported and works. [1] The code is currently undergoing review, and once some inconsistencies are fixed up, it looks set for inclusion into master. This means that along with this, a 2D GTK Window decorator, git changes amongst other things we are extremely close to fufilling our release criteria for an unstable 0.9.0. So we need to sort out the logistics of a release. I have written a release announcement that can be found on GObby. Feel free to edit it, it's probably not perfect by any stretch of the imagination. The next thing we need to sort out is making...
2008 Jan 17
7
1.9.4 released
Hi Just a quick note to say we released a new version, 1.9.4. The main purpose of this release is to offer an OS X gem that''s compatible with both 10.4 and 10.5 - The wxruby-1.9.3 OS X binary gem would only work with version 10.5 (Leopard). Version 1.9.4 also includes a couple of other minor fixes and enhancements, including * Some new AuiNotebook methods added in recent wxWidgets
2005 Oct 07
1
FFT
Hi, Is FFT implemented in R takes advantage of multi-processors? I ran this benchmark from from http://www.sciviews.org, and AMD Opteron 2.2 GHz performs better than AMD Opteron 1.8 GHz on all test cases, except FFT operation. Both machines run same OSs (RedHat WS 3) and 2.2 GHz has more memory (2 GB RAM) than 1.8 GHz (1 GB RAM). The only difference is that 1.8 GHz is a dual-processor
2006 Mar 29
0
Compiling codes from existing packages.
...t seem efficient to load the entire packages every time. Reading the "writing R extensions" and readme.packages leave me rather confused and disoriented, there are bits of information that seem to help, but there also seems to be lots of gap in the process which I have no idea how to fufil. I think these are good documents as a reference guide for people who know what the underlying process is, but not so useful for beginners like me, unfortunately. My question is given I have three C codes (which I can put into one file?) and series of Fortran codes in one file, (and they are al...
2005 Mar 12
2
Pretec Allegro does not appear to play Oggs
Can I change the wiki? The box claims it plays oggs, the tech. specs. in the booklet claims it plays oggs, *some* places on the website claims it supports oggs, but it doesn't actually play my oggs. Can I move it to a "misadvertised" section, or a "rumours" section, or what can I do to indicate this to other people, so they don't accidentaly buy it? Hugo
2008 Jan 30
2
Re: libgstreamer, slackware => libgconf.......???
...for a friendlier programming environment) and probably can get enough done with 1.9.2 before needing to upgrade... Please keep f ocused on the main direction of wxRuby. rob > The wxRuby 1.9.3 binaries added Wx::MediaCtrl, which requires > libgstreamer on Linux. You can either: > > 1) Fufil this dependency by installing libgstreamer > > or > > 2) Build your own wxRuby. Wx::MediaCtrl is an optional component, and if > you''re compiling your own wxRuby and it''s not found to be supported, > it''ll be skipped without error. > > hth > ale...
2020 Nov 06
2
[DebugInfo] A value-tracking variable location update
...le by DBG_VALUE variable-location tracking, although there are some bugs in picking locations. Roughly half of the dropped locations are actual false locations, the other half are due to unimplemented or limited handling of optimisations in the instruction referencing code so far. This pretty much fufils the objective of this work: we're able to save a lot more variable locations through the register allocator because we don't have to be so conservative about liveness. Plus, the default behaviour of all optimisations now is to _drop_ a variable location, as opposed to the existing situatio...
2020 Nov 06
0
[DebugInfo] A value-tracking variable location update
...-location tracking, although there are some bugs in picking > locations. Roughly half of the dropped locations are actual false locations, > the other half are due to unimplemented or limited handling of optimisations in > the instruction referencing code so far. > > This pretty much fufils the objective of this work: we're able to save a lot > more variable locations through the register allocator because we don't have to > be so conservative about liveness. Plus, the default behaviour of all > optimisations now is to _drop_ a variable location, as opposed to the ex...