MonoDevelop (or Xamarin Studio) actually uses out VS2010 project files and runs on any linux flavor that runs mono.
ltouroumov
@ltouroumov
Best posts made by ltouroumov
Latest posts made by ltouroumov
-
RE: C.S. class WTF
-
RE: Constructors must return self
Disclamer: I'm not doing iOS development actively anymore (back to higher studies)
I remember the return self being in the class file template. And it's about the first thing I learned in Obj-C that you should do that and don't ask questions about it. (Also iOS not having automatic garbage collection does not help in any way)
I never got the "Not available before ..." warning. But I know It's possible to make apps that don't generate warnings (we used to have days dedicated to doing that). There is also the code analysis tool to help you with eventual references problems. It has some false positives but it almost never misses (we had 2-3 of them but it was really some crappy code that ended up to be refactored).
But I will give you that XCode's tendency to crash is really annoying. And it could use some improvements (though the 4.x already improves the 3.x version)
-
RE: All those monkeys banging away on their keyboards and you picked the wrong one
Well thats a pretty huge bug for it not to be catched in unit tests (assuming they have those)
But again who cares about OpenGL since it's cross-platform (according to microsoft)
-
RE: Wikipedia and Their Awesome CSS Skills
At least it looks the same on all the browsers.
-
XCode can't resurrect !
This morning I was working but XCode decided it didn't wanted to so it crashed (again)
The stack trace was pretty explicit:
Process: Xcode [11993] Path: /Developer/Applications/Xcode.app/Contents/MacOS/Xcode Identifier: com.apple.dt.Xcode Version: 4.0 (99) Build Info: IDEApplication-990000~36 Code Type: X86-64 (Native) Parent Process: launchd [532]
Date/Time: 2011-03-15 08:28:37.899 +0100
OS Version: Mac OS X 10.6.6 (10J567)
Report Version: 6Interval Since Last Report: 296765 sec
Crashes Since Last Report: 46
Per-App Interval Since Last Report: 8739 sec
Per-App Crashes Since Last Report: 1
Anonymous UUID: CAF2FC67-76FB-483F-A019-9F18F7631207Exception Type: EXC_BAD_INSTRUCTION (SIGILL)
Exception Codes: 0x0000000000000001, 0x0000000000000000
Crashed Thread: 13 Dispatch queue: Garbage Collection Work QueueApplication Specific Information:
ProductBuildVersion: 4A304a
fatal resurrection error for garbage block 0x200c3c880(AMDServiceConnection[64]): over-retained during finalization, refcount = 1
objc[11993]: garbage collection is ONThread 0: Dispatch queue: com.apple.main-thread
0 libSystem.B.dylib 0x00007fff8574b2da mach_msg_trap + 10
1 libSystem.B.dylib 0x00007fff8574b94d mach_msg + 59
2 com.apple.CoreFoundation 0x00007fff82859932 __CFRunLoopRun + 1698
3 com.apple.CoreFoundation 0x00007fff82858dbf CFRunLoopRunSpecific + 575
4 com.apple.HIToolbox 0x00007fff838c893a RunCurrentEventLoopInMode + 333
5 com.apple.HIToolbox 0x00007fff838c873f ReceiveNextEventCommon + 310
6 com.apple.HIToolbox 0x00007fff838c85f8 BlockUntilNextEventMatchingListInMode + 59
7 com.apple.AppKit 0x00007fff8173be64 _DPSNextEvent + 718
8 com.apple.AppKit 0x00007fff8173b7a9 -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 155
9 com.apple.AppKit 0x00007fff8170148b -[NSApplication run] + 395
10 com.apple.AppKit 0x00007fff816fa1a8 NSApplicationMain + 364
11 com.apple.dt.Xcode 0x0000000100000eec 0x100000000 + 3820More stack trace ...
Thread 13 crashed with X86 Thread State (64-bit):
rax: 0x0000000000000000 rbx: 0x0000000200c3c880 rcx: 0x00007fff8574b2da rdx: 0x0000000000000000
rdi: 0x00000001227119f0 rsi: 0x0000000000000003 rbp: 0x0000000122711bf0 rsp: 0x0000000122711b20
r8: 0x0000000000001a0b r9: 0x0000000000000000 r10: 0x000000000000002c r11: 0x0000000000000206
r12: 0x00000001014dc000 r13: 0x0000000124d00010 r14: 0x0000000000000001 r15: 0x0000000000000002
rip: 0x00007fff874ffd5a rfl: 0x0000000000010202 cr2: 0x00000001013853c0Binary Images:
0x100000000 - 0x100000fff com.apple.dt.Xcode 4.0 (99) <1AEE2FF2-CB04-3CDF-B085-C683453BEFD7> /Developer/Applications/Xcode.app/Contents/MacOS/Xcode
More drivers ...Model: MacBookPro5,2, BootROM MBP52.008E.B05, 2 processors, Intel Core 2 Duo, 2.8 GHz, 4 GB, SMC 1.42f4
More specs ...
XCode can do a lot of things but apparently not resurrect dead objects !
Surprising fact: I almost rarely experiencec crash on my mac except for IDE's
-
RE: Why yes, yes I am.
@AngelSL said:
That is C#, not Java. Java has OutOfMemoryError, not OutOfMemoryException.
Really long time ! (I really looks like Java when you don't look too close)
@ltouroumov said:
@Weng said:
catch (OutOfMemoryException x)
{
//Well you're just fucked now, aren't you?
throw x;
}Is the comment original ?
Can't you free some resources (like useless objects etc...) in that call ? (I don't know I havent done Java since school)
I was asking if the comment was in the original code
English is not my primary language, so stupid expressions like this pop up when Im not focused
-
RE: Why yes, yes I am.
@Weng said:
catch (OutOfMemoryException x)
{
//Well you're just fucked now, aren't you?
throw x;
}Is the comment original ?
Can't you free some resources (like useless objects etc...) in that call ? (I don't know I havent done Java since school)
-
RE: Ridiculous input validation gone bad (for the some of the world)
@IronFist said:
yeah, yeah, TRWTF is you need the 'alt gr' key on sg keyboard layout to get to the vital '@' char :-((
On all keyboards layouts I have seen (French PC, Swiss PC and Mac), you need the 'alt', 'ctrl' or 'alt gr' key for "special" characters (like @ or |[]{}# on mac)
But seems on US keyboards you need 'Shift+2'
Restricting keyboard usage is a WTF.
Solution: Disable javascript ... and wait ... no form submit also in javascript
-
RE: Another report from wtf workplace
@DOA said:
Am I the only one who works with mental patients?
There's always at least one crazy person in each office/department, I think it's HR requirement.
-
RE: You really didn't see that coming?
@frits said:
Why don't you just change the logic to download the new sdf to a temporary file? If the download suceeds, start at step one (skipping the download part, of course). If not, show the error message.
He can't because he's busy fixing the app on users workstations and therefore has no time to update the app