ld expect modern Intel processors to have such fast
floating point, but probably not the iPhone's ARM processor.
Don Quixote
--
Don Quixote de la Mancha
quix...@dulcineatech.com
http://www.dulcineatech.com
Dulcinea Technologies Corporation: Soft
is made
completely explicit.
Thank you for any insight you can give me,
Don Quixote
--
Don Quixote de la Mancha
quix...@dulcineatech.com
http://www.dulcineatech.com
Dulcinea Technologies Corporation: Software of Elegance and Beauty.
___
Cocoa-dev
ander Spohr wrote:
> PS. I’d think all this info is on Apple’s site somewhere...
Actually it's not. I looked pretty carefully before I wrote to the list.
Thanks,
Don Quixote
--
Don Quixote de la Mancha
quix...@dulcineatech.com
http://www.dulcineatech.com
Dulcinea Technologie
drive of my career.
Don Quixote
--
Don Quixote de la Mancha
quix...@dulcineatech.com
http://www.dulcineatech.com
Dulcinea Technologies Corporation: Software of Elegance and Beauty.
___
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please do not
ted, but it does work if you
can figure it out.
I might have some sample code I could dig up if you're not able to
figure it out on your own.
Don Quixote
--
Don Quixote de la Mancha
quix...@dulcineatech.com
http://www.dulcineatech.com
Dulcinea Technologies Corporation: Software o
name of the program. That way you can name the
executable anything you like, and error messages will always be
correct.
Don Quixote
--
Don Quixote de la Mancha
quix...@dulcineatech.com
http://www.dulcineatech.com
Dulcinea Technologies Corporation: Softw
st doesn't, or it tries to but it is buggy.
Don Quixote
--
Don Quixote de la Mancha
quix...@dulcineatech.com
http://www.dulcineatech.com
Dulcinea Technologies Corporation: Software of Elegance and Beauty.
___
Cocoa-dev mailing list (Cocoa-dev@list
rt of
each read aligned at multiples of 2048.
Mike
--
Don Quixote de la Mancha
quix...@dulcineatech.com
http://www.dulcineatech.com
Dulcinea Technologies Corporation: Software of Elegance and Beauty.
___
Cocoa-dev mailing list (Cocoa-dev@lists.appl
ivate use of the library call, and isn't meant to make sense or be
portable.
If readdir does work on OS X, it will get you the filename as it is
actually found in the filesystem - that is, with the case preserved.
Look up "man 3 readdir" and friends.
Don Quixote
--
Don Quixo
h the whole directory
anyway. So it wouldn't be any slower to roll the code himself.
A C function that used readdir to get the case-preserved filename
shouldn't be more than ten lines of code or so.
Don Quixote
--
Don Quixote de la Mancha
quix...@dulcineatech.com
http://www.dulcineatec
files all at once.
Your realpath method while undoubtably better for a single file might
actually be slower than readdir if one uses it for many files that are
all in a single directory.
Don Quixote
--
Don Quixote de la Mancha
quix...@dulcineatech.com
http://www.dulcineatech.com
Dulcinea Technologi
st holding the file
open should prevent it from being deleted.
Don Quixote
--
Don Quixote de la Mancha
quix...@dulcineatech.com
http://www.dulcineatech.com
Dulcinea Technologies Corporation: Software of Elegance and Beauty.
___
Cocoa-dev mailing l
ime, and so is more likely to be
closer to the original release.
Don Quixote
--
Don Quixote de la Mancha
quix...@dulcineatech.com
http://www.dulcineatech.com
Dulcinea Technologies Corporation: Software of Elegance and Beauty.
___
Cocoa-dev mail
figure out any other way.
Don Quixote
--
Don Quixote de la Mancha
quix...@dulcineatech.com
http://www.dulcineatech.com
Dulcinea Technologies Corporation: Software of Elegance and Beauty.
___
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Ple
t macro in disables itself if
NDEBUG is defined. I am under the impression that the presence or
absence of NDEBUG is specified by the ANSI C definition, but I'm not
completely certain.
Don Quixote
--
Don Quixote de la Mancha
quix...@dulcineatech.com
http://www.dulcineatech.com
Dulcin
- I'll get my
Company application submitted today.
I'm going to file a Radar bug asking that Apple make it more explicit
about what each iPhone Program type includes.
Don Quixote
--
Don Quixote de la Mancha
quix...@dulcineatech.com
http://www.dulcineatech.com
Dulcinea Technologies
url/
That would probably be the easiest route.
You should file a bug with Apple at http://bugreport.apple.com/
Buffering a lot of data isn't a big deal on Mac OS X, but it's bad
news on an embedded device like the iPhone.
Don Quixote
--
Don Quixote de la Mancha
quix...@dulcineatech.com
Québec, Canada
>
>
> ___
>
> Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
>
> Please do not post admin requests or moderator comments to the list.
> Contact the moderators at cocoa-dev-admins(at)lists.apple.com
>
> He
The underlying open() system call can open documents read-only. See
man 2 open. Does Cocoa have a way to specify read-only document open
that passes the right flag to open()?
--
Don Quixote de la Mancha
quix...@dulcineatech.com
Custom Software Development for the iPhone and Mac OS X
name that your shim knows how to load. This would be a little
dangerous; if the dylib is important and you screw up, your user might
have to reinstall OS X, so make sure you get it right.
--
Don Quixote de la Mancha
quix...@dulcineatech.com
Custom Software Development for the iPhone and Mac O
This may be a bug in either iTunes or the iOS. If you think it might
be, you should file a bug report at:
http://bugreport.apple.com/
--
Don Quixote de la Mancha
quix...@dulcineatech.com
Custom Software Development for the iPhone and Mac OS X
http://www.dulcineatech.com/custom
The only way I can see to test on such early firmware is to buy a used
device from eBay or some such, that has never had a firmware update.
--
Don Quixote de la Mancha
quix...@dulcineatech.com
Custom Software Development for the iPhone and Mac OS X
http://www.dulcineatech.com/custom-software-d
t;
> Please do not post admin requests or moderator comments to the list.
> Contact the moderators at cocoa-dev-admins(at)lists.apple.com
>
> Help/Unsubscribe/Update your Subscription:
>
http://lists.apple.com/mailman/options/cocoa-dev/quixote%40dulcineatech.com
>
> This email se
alled Xcode 4.1, it blew
away my old /Developer folder.
Don Quixote
--
Don Quixote de la Mancha
Dulcinea Technologies Corporation
Software of Elegance and Beauty
http://www.dulcineatech.com
quix...@dulcineatech.com
___
Cocoa-dev mailing list (Cocoa-
eature that uses them when running on iOS builds prior to 5.0
--
Don Quixote de la Mancha
Dulcinea Technologies Corporation
Software of Elegance and Beauty
http://www.dulcineatech.com
quix...@dulcineatech.com
___
Cocoa-dev mailing list (Cocoa-dev@list
er for
small accesses but slower for large ones.
--
Don Quixote de la Mancha
Dulcinea Technologies Corporation
Software of Elegance and Beauty
http://www.dulcineatech.com
quix...@dulcineatech.com
___
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please d
ffel programming language, which
unfortunately is not as popular as I think it should be.
But Programming by Contract is not hard at all to implement as a macro
package for most other programming languages.
--
Don Quixote de la Mancha
Dulcinea Technologies Corporation
Software of Elegance and B
because Objective-C exceptions
don't work like C++ exceptions do.
You can pass result codes back to calling functions, but you have to
be quite diligent about always doing so, always checking for results
from the functions you call, then doing something sensible no matter
what results your fun
is an as-yet-unreported bug in the iOS I will be
happy to file a report, but I would be even happier if someone could
suggest a workaround. I've been beating my head against this for a
couple days now.
Thanks!
Don Quixote
--
Don Quixote de la Mancha
Dulcinea Technologies Cor
iOS memory allocator is multithreaded, and
that Apple's code would be good about checking for runtime failures.
If it does not, then that is a bug in the iOS.
--
Don Quixote de la Mancha
Dulcinea Technologies Corporation
Software of Elegance and Beauty
http://www.dulcineatech.
On Mon, Nov 7, 2011 at 3:59 PM, Jens Alfke wrote:
> On Nov 4, 2011, at 6:40 PM, Don Quixote de la Mancha wrote:
> I store the grid as an array-of-arrays rather than a two dimensional
> array. That is, I have an array of pointers which has the same number
> of elements as th
.
--
Don Quixote de la Mancha
Dulcinea Technologies Corporation
Software of Elegance and Beauty
http://www.dulcineatech.com
quix...@dulcineatech.com
___
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please do not post admin requests or moderator c
are models
will likely have more physical RAM. Also the amount that can be
safely allocated would depend on how much is left over from other
processes, and so could not be counted upon to be any particular fixed
amount.
--
Don Quixote de la Mancha
Dulcinea Technologies Corporation
Software of Eleg
with G++ and
Metrowerks CodeWarrior to spot portability problems.
I also use assert() a great deal, mostly to check the input parameters
to functions, but elsewhere as well.
C'mon man, it's not that hard!
--
Don Quixote de la Mancha
D
memory as the system required.
As it is now, I have no way at all to warn my user that the game grid
they configured might be too big. Either they get a new grid of the
desired size, or the iOS terminates my App, thereby destroying all the
user's state.
--
Don Quixote de la Mancha
Dulcinea
en it uses too much memory. While a better algorithm would
allow the effect of a much larger grid, Conway's Life patterns can
grow without bound. I need to know ahead of time when further growth
is not tolerable.
--
Don Quixote de la Mancha
Dulcinea Technologies Corporation
Software of
On Tue, Nov 8, 2011 at 10:49 PM, Kyle Sluder wrote:
> On Tue, Nov 8, 2011 at 10:44 PM, Don Quixote de la Mancha
> wrote:
>> Kids These Days.
>>
>> While the Space Shuttle exploded twice, I hasten to point out that
>> neither of those failures was due to software bu
some advanced
data structures and algorithms that might - just might - make my
overall algorithm the fastest Conway's Life algorithm in existence.
That remains to be proven though.
--
Don Quixote de la Mancha
Dulcinea Technologies Corporation
Software of Elegance and
On Tue, Nov 8, 2011 at 11:38 PM, Don Quixote de la Mancha
wrote:
> I can't figure out how to view the detailed build log. Where is that
> hidden? Google yields no insight.
Just so Google will yield insight to others in the future. To view
the detailed build log in Xcode
On Tue, Nov 8, 2011 at 11:46 PM, Greg Parker wrote:
> On Nov 8, 2011, at 10:56 PM, Don Quixote de la Mancha wrote:
>> On Tue, Nov 8, 2011 at 10:49 PM, Kyle Sluder wrote:
> No, the reason is that most end-users do not want to pay Space Shuttle prices
> (high) for Space Shuttle
ndependent atomic arithmetic and thread synchronization
primitives. It would be very easy to replace those with Cocoa's.
I'm pretty sure that part of Ogg Frog's code is published under the MIT License.
--
Don Quixote de la Mancha
Dulcinea Technologies Corporation
Software of El
On Wed, Nov 9, 2011 at 1:02 AM, Jean-Daniel Dupas
wrote:
> Le 9 nov. 2011 à 07:44, Don Quixote de la Mancha a écrit :
>> While the Space Shuttle exploded twice, I hasten to point out that
>> neither of those failures was due to software bugs.
>>
>
> No, but Ariane
et settings are meant to
accomplish, but despite having used Xcode since it was called Project
Builder, I still find these combined settings to be an endless source
of confusion.
Hope That Helps!
--
Don Quixote de la Mancha
Dulcinea Technologies Corporation
Software of Elegance and
EALLY REALLY REALLY like is a machine debugger that
worked just like MacsBug did on the Classic Mac OS. While GDB is
generally capable of doing assembler debugging, it totally sucks for
that purpose. That's not anyone's fault, really, because it is
designed for source debugging. A good asse
On Wed, Nov 9, 2011 at 9:39 AM, Don Quixote de la Mancha
wrote:
> .globl _IntNoArgs
> .align 2
> .code 16
That should actually be ".align 1". The parameter to .align is the
power to which two is raised to yield the alignment. ".code 16"
generates Thumb code,
documented to return NULL when there isn't
enough memory to satisfy the user's request. Their implementation is
simply broken if they don't do that.
--
Don Quixote de la Mancha
Dulcinea Technologies Corporation
Software of Elegance and Beauty
http://
g with a minimal test case, but Apple has not
yet responded. It usually takes them a while.
There are many other reasons to allocate memory other than to set up a
game playing field. There are lots of other kinds of resources other
than memory as well. If we cannot count on the iOS to let
ult )
return result;
[initBuf result]; // We are now certain result is not NULL
return result;
}
- (void) initBuf: (unsigned char*) bufPtr
{
assert( NULL != bufPtr ); // Correct use of assert
...
return;
}
Hope That Helps,
Don Quixote
--
Don Quixote de la Mancha
Dulcinea Tec
mal test case or a thorough regression, but
when I do I'll post them here, and will post a follow-up as a new
thread in the Xcode-Users list:
http://www.dulcineatech.com/bug-reports/xcode/4.2/llvm/
Nighty-Night! Don't Let The Code Bugs Byte.
Don Quixote
--
Don Quixot
or armv6 is broken, and
figured that even though this was armv7, but I have not yet been able
to figure out how to disable Thumb in Apple's LLVM 3.0 compiler for
Xcode 4.2. The way one does it for GCC has no effect on LLVM.
If you can enlighten me, I'll give it a try right after I get back
nation of ivars.
--
Don Quixote de la Mancha
Dulcinea Technologies Corporation
Software of Elegance and Beauty
http://www.dulcineatech.com
quix...@dulcineatech.com
___
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please do not post admin requests or mod
ccess,
because it has to go through Objective-C's message dispatch mechanism.
Focussing on interface is no excuse for weighty, bloated code!
--
Don Quixote de la Mancha
Dulcinea Technologies Corporation
Software of Elegance and Beauty
http://www.dulcineatech.com
quix...@dulcin
On Wed, Nov 16, 2011 at 8:03 AM, Kyle Sluder wrote:
> On Nov 16, 2011, at 1:00 AM, Don Quixote de la Mancha
> wrote:
>> Calling accessors is also quite slow compared to a direct iVar access,
>> because it has to go through Objective-C's message dispatch mechanism.
>
e as much memory as you want, but your
program will perform well if only a little bit of your allocation is
actually resident.
The kernel maintains a bunch of statistics about each user process. I
expect that your resident memory usage will be among those statistics,
but I'm sorry I don't kn
using cached memory,
preferring hand-rolled assembly code instead. The ARM Holdings
website has oodles of technical articles about how to do that, as do
Intel's and AMD's websites.
--
Don Quixote de la Mancha
Dulcinea Technologies Corporation
Software of Elegance and Beauty
erent people who are
representative of your target market.
--
Don Quixote de la Mancha
Dulcinea Technologies Corporation
Software of Elegance and Beauty
http://www.dulcineatech.com
quix...@dulcineatech.com
___
Cocoa-dev mailing list (Cocoa-dev@lists.a
to
use atomic operations as locking primitives. One is that they cannot
result in process context switches; if you are certain that you will
release the lock quite quickly, it is a whole lot faster, and uses
less memory, to use atomic arithmetic.
I'll send you my bill in the mail,
Don Quixot
rocessing going all the way
back to the 1940s. The problems you and I face today may well have been solved
and published decades ago. Even if the algorithms were patented those patents
may well have expired by now.
I'm sorry but I cannot recommend any reading. I expect others on this list can.
ilesystem calls.
Extra credit if you preflight the entire process without deleting
anything at all, just to check whether any unlinks would fail because
you don't have permission. The permission bits are available in the
structure returned from the stat system call.
I'll
le ranges of parameters are revised.
You can also assert the ranges of return results, but my experience is
that I get more mileage out of asserting input parameters.
--
Don Quixote de la Mancha
Dulcinea Technologies Corporation
Software of Elegance and Beauty
http://www.dulcineatech.c
On Sun, Apr 29, 2012 at 8:00 PM, Don Quixote de la Mancha
wrote:
> Place some assertions as the very first executable lines in each of
> your subroutines. The chances are quite good that the cause of the
> SIGABRTs are executable quite a long time before the crashes actually
e in the early nineties, most of our
products were what the company founder describes as "Virus-Like
Hacks", with the difference that our products' users wanted them on
theirs Macs, paid good money for them, and they were packaged in
full-color boxes with attractive, well-writ
.
But if you do find that you've introduced bugs - or really, if you
have ANY bugs at all - fix them by writing automated tests just for
the very lowest level of your heirarchy, then after fixing any bugs
you discover in just that lowest level, write tests for just the
second level.
Do no
ry little to do with anyone's Venture Backed Startup, Killer App
Idea or Insanely Great Product.
> Read.
-> Them.
-> Or.
----> Weep.
I'll send you my bill in the mail.
--
Don Quixote de la Mancha
Dulcinea Technologies Corporation
Software of Ele
64 matches
Mail list logo