search for: dstring

(R-1.6.0 and chron 2.2, linux) I have to work with date/time values from another LOCALE on my machine. My normal locale is "de DE at euro" and the data I have to handle use AM/PM specifications for the times. dstring <- "Nov 12 2001 4:31PM" The problem now is, that strptime(dstring, "%b %d %Y %I:%M%p") [1] "2001-11-12 04:31:00" just ignores my times coming from another locale. I have a workaroud (kind of) in setting my LANG enviroment to C before starting R, but I hope for...

...XBox that seems trivial as the functions are very basic in nature. My comments on OpenStep were more meant to point to the fact that we would write our own library; really just throwing all notion of OpenStep away. Instead of NSObject we would create our own base DObject or something along with a DString, DAarry, DSet, DMap, etc. Truthfully this would be our plan anyway because we want to follow the lead of OSX and provide these objects "toll free bridged"... meaning we would implement them using a std c++ library object (e.g. std::basic_string or std::vector) as the first member of the...

...ivial as the functions are very basic in nature. >> >> My comments on OpenStep were more meant to point to the fact that we would write our own library; really just throwing all notion of OpenStep away. Instead of NSObject we would create our own base DObject or something along with a DString, DAarry, DSet, DMap, etc. Truthfully this would be our plan anyway because we want to follow the lead of OSX and provide these objects "toll free bridged"... meaning we would implement them using a std c++ library object (e.g. std::basic_string or std::vector) as the first member of the...

...seems trivial as the functions are very basic in nature. > > My comments on OpenStep were more meant to point to the fact that we would write our own library; really just throwing all notion of OpenStep away. Instead of NSObject we would create our own base DObject or something along with a DString, DAarry, DSet, DMap, etc. Truthfully this would be our plan anyway because we want to follow the lead of OSX and provide these objects "toll free bridged"... meaning we would implement them using a std c++ library object (e.g. std::basic_string or std::vector) as the first member of the...

...ons are very basic > in nature. > > My comments on OpenStep were more meant to point to the fact that we > would write our own library; really just throwing all notion of > OpenStep away. Instead of NSObject we would create our own base > DObject or something along with a DString, DAarry, DSet, DMap, etc. > Truthfully this would be our plan anyway because we want to follow > the lead of OSX and provide these objects "toll free bridged"... > meaning we would implement them using a std c++ library object (e.g. > std::basic_string or std::vector)...

...;>> >>> My comments on OpenStep were more meant to point to the fact that >>> we would write our own library; really just throwing all notion of >>> OpenStep away. Instead of NSObject we would create our own base >>> DObject or something along with a DString, DAarry, DSet, DMap, >>> etc. Truthfully this would be our plan anyway because we want to >>> follow the lead of OSX and provide these objects "toll free >>> bridged"... meaning we would implement them using a std c++ >>> library object (e.g. s...

...t;>> My comments on OpenStep were more meant to point to the fact that >>>> we would write our own library; really just throwing all notion of >>>> OpenStep away. Instead of NSObject we would create our own base >>>> DObject or something along with a DString, DAarry, DSet, DMap, >>>> etc. Truthfully this would be our plan anyway because we want to >>>> follow the lead of OSX and provide these objects "toll free >>>> bridged"... meaning we would implement them using a std c++ >>>> librar...

...the functions are very basic in nature. >>> >>> My comments on OpenStep were more meant to point to the fact that we would write our own library; really just throwing all notion of OpenStep away. Instead of NSObject we would create our own base DObject or something along with a DString, DAarry, DSet, DMap, etc. Truthfully this would be our plan anyway because we want to follow the lead of OSX and provide these objects "toll free bridged"... meaning we would implement them using a std c++ library object (e.g. std::basic_string or std::vector) as the first member of the...

llvm can output C code, but that target has bitrotted severely over the last few months and nobody seems to be interested in fixing it. You may need to do some work there. Alternatively you could implement the PPC ABI that you need. There are several examples of supporting multiple ABIs on the same hardware, x86 being the most obvious. A lot of simple stuff will probably Just Work with the

...ctions are very basic in nature. >>>> >>>> My comments on OpenStep were more meant to point to the fact that we would write our own library; really just throwing all notion of OpenStep away. Instead of NSObject we would create our own base DObject or something along with a DString, DAarry, DSet, DMap, etc. Truthfully this would be our plan anyway because we want to follow the lead of OSX and provide these objects "toll free bridged"... meaning we would implement them using a std c++ library object (e.g. std::basic_string or std::vector) as the first member of the...

Brian was kind enough to test llvmgcc against a bunch of GNU code. This exposed all kinds of bugs, fixes below. > recode -- fails (bad headers, many ICEs) Can you give me a list of headers it wants? It's usally pretty easy to add them if I know what it needs... > cpio -- fails (dstring.c -- weird ssa bug) Fixed. This was a C frontend bug (problem assigning temporary reg nums). > diffutils-- fails (analyze.c, diff.c and others) The analyze.c bug is tested here: http://mail.cs.uiuc.edu/pipermail/llvm-commits/Week-of-Mon-20021209/001957.html and fixed here: http://mail.cs.uiu...

I'm in the process of installing openssh 2.5.1p2 and the make install step fails. I did the build without problems. Now when I attempt to do the make install it fails with the output below. Software build process should have to separate steps. A build step and an install step. The install step should not create or modify any files in the tree structure as this will fail when a root user is

We are looking at using Objective-C/C++ in a new game engine.  Objective C's duality of being both very dynamic and very "C" gives us exactly what we need to make the SDK and engineering of games simpler. This means that we will need a way to compile it on all platforms our games will target.  Currently the major platforms we are concerned with include... PC, Mac, XBox 360, PS3,