Hi, just lurking here on the list and wanted to address an issue that can hopefully be fixed in future releases of Frontier (and who knows maybe there's a temp...
... With the latest changes checked in, I am now down to two GCC compiler warnings total. These come from langparser.c and require some more investigation...
... Awesome job! I did a clean recompile and got 2 warnings as well. I was wondering why you didn't simply comment out the declarations of fopen and fclose,...
I'm happily poring through the source code, giddily trying to figure out how to subvert Frontier to my own nefarious desires, and many things come to mind... ...
When I get back from BloggerCon why don't the Seattle people on this list get together. We can spend a few hours reviewing the code and I'll do a brain dump. ...
Such a brain dump would be very helpful. I'll be there. Dave L. ... this list get together. We can spend a few hours reviewing the code and I'll do a brain...
You can definitely count me in for this. In addition, we could record the session and release it as a podcast for those potential Frontier developers that...
... I think stringfunctionvalue() in stringverbs.c is probably a good starting point. If you have some experience with UserTalk scripting, you will know what...
... Yes, great job. I was waiting until you guys had finished removing all/most of the warnings before I would start merging my changes. I will take a look at...
... Just curious, what kind of changes have you been working on? ... The warnings are due to static definitions at the top of langparser.c that override...
... I would agree, and I would take it further and say that we should specifically make it so that langparser.y works with yacc or bison (which I would guess...
... Yes, I already tried that and indeed the resulting file does not rely on any stdio.h functions. However, it also look very different from the current...
Hi there, I know that I'm surely quite ahead of time about this, and maybe this is not a good time, but I'll ask anyway. I always found the Frontier website...
... While I probably won't get to it for a few days, I am still a big MPW user, so it should be no problem for me to regenerate the langparser.c file etc. I...
... warnings before I would start merging my changes. ... As I posted to this list some time ago, my changes are in the area of support for Spotlight on...
... That's the direction I am moving in. I haven't had a lot of experience with cygwin, but several LARGE open source projects I am involved in, use cygwin for...
... I just bumped the version numbers in versions.h to 10.0a2 in order to distinguish the current state of the kernel from the original release. Then I tagged...
That's not exactly right, as there is one change that I already committed previously that improves the performance of lists only (not records) by making it the...
Hello! Sorry this is probably a pretty newbie set of questions. I am running on Windows XP SP2. I am just mucking around with the posted .exe from the...
... Good (I suspected Henri's list patch was in there, not a problem). I was going to tidy up the loose ends with the application icon and Info.plist for the...
... Using Xcode v1.5, I get an Info.plist file in Frontier.app/Contents and another in Frontier.app/Contents/Resources. The latter contains the same unresolved...
... I think the best way to do this is to add a build step that does some shell script hackery to extract the string from versions.h and puts it into the...
Random thoughts... Is visiting list values truly necessary? I hope that as we fix the list type, it's as fast to do it in UserTalk as it is in C in the kernel....
I would like to know the right way to handle large string paramaters in kernel verbs. By large, I mean longer than 255 chars, i.e. longer than a pascal string...
... I ended up going in a completely different direction. I needed a cstring, and so I did the following: Handle text; if (!getreadonlytextvalue (hp1, 1,...
... If malloc returns a nil pointer, you must call memoryerror to report this to the user. If you don't, scripts will just die silently when they encounter...
Having problems with message search?
Fill out this form to ensure your group is one of the first to be migrated to the new message search system.
