What should the following REALbasic code do: #if Foobar Const Foobar = false MsgBox "Foobar!" #endif If forward referencing is allowed, then this code should not exist in the resulting application (though it should compile). If forward referencing is not allowed, then this code should fail to compile entirely. So if you're in the camp of people that claim the above code should fail to compile, then you've also placed yourselve in the camp that claims this code should fail to compile as well: Sub SomeMethod( test as Integer = kSomeConstant ) Without ubiquitous forward referencing, this code may or
December 2007 Archives
Well, another year, another Christmas holiday. This year, I'm splitting Christmas day in half -- half the day is down in Texas, half the day at an airport, and half the day in Minnesota (it's a long day!). It's great to be able to see both families. Lis' family celebrates on x-mas eve with the extended relatives. I had a blast, once I was done cooking the tenderloin. :-P Uncle Glenn brought a small portion of his impressive arsenal, which we went down to the pond and shot. I shot the 45 magnum handgun again, which is always cool. But
Every so often, there is talk about a community-driven content project that seems to come up in the REALbasic community. These ideas run the gambit from OSS projects (like the WFS and CDL) to repositories (think SourceForge for RB code), to content (like a documentation wiki), and more. They always have a huge push of "yeah, that's a great idea!" from the community when they are discussed in public forums. However, it's my personal prediction that 99.9% of them end up failing. I know I sound really negative when I say that, but I have enough years of experience watching
Wahoo! I'm done working until the end of the year (actually, I won't be back to work until Jan 3rd or 4th). I'm both looking forward to and dreading my vacation time. Lis and I are flying in to Austin on Saturday, and then we start the parade of vendors for the wedding. For three days, we have at least two vendors to meet and discuss things with. But the hope is that by Thur morning, we will have all of the vendors for the wedding picked out and lined up (with the possible exception of a DJ). While this
While browsing around in the feedback system the other day, I ran across a feature request that caught my eye. It was asking for the ability to use arrays as the return type for computed properties. Once upon a time, I thought "hey, I really want that too!", but that was a long time ago. So I spent some time thinking about what it would actually mean to allow arrays as return types for computed properties, and I realized "ooh, that's not a good idea!" because of the aliasing problem. Imagine, if you will, some code that looks like this:
Wow, what a whirlwind of wackiness. Sorry, alliteration just isn't working for me today. ;-) What I really meant to say is that I've been super busy as of late, and so things like blog postings tend to be few and far between. In no particular order: I've been working several long days (including the entire weekend) on some really awesome new compiler features for the next beta. I'd tell you what they are, but then I'd have to kill you. But those of you who are in the betas program will probably know what I'm talking about when the
