JB wrote:
> On Oct 1, 2014, at 5:20 PM, Dr. Hawkins <dochawk at gmail.com> wrote:
>
>> On Wed, Oct 1, 2014 at 4:01 PM, JB <sundown at pacifier.com> wrote:
>>
>>> Code for Program to convert binary to hexadecimal in C Programming
>>
>> \begin snivel{}
>> It burns, it burns!
...
> Who do you think is sniveling and exactly
> how fun is if for you to say “it burns. it burns!”?
>
> And who are you saying it to me because the
> code does not work or LiveCode? Either way
> what makes it so fun for you?
>
> But when it comes to the error I found, that
> error and many others can destroy an good
> company and may have helped cause the
> financial problems Revolution had.
>
> I am not attacking LiveCode and have been
> supporting them for many years.
>
> The many test I have done on the Binary to Hex
> code makes me think it took some extra special
> code to cause the problem. I certainly do not
> think this was done to attack me personally.
Dr. Hawkins is a good-natured fellow, and I've known him long enough to
feel confident that his comment wasn't an attack on you, but merely on
C, and even then in a light-hearted way (or so I'm sure it was intended).
Most of us here are long-time LiveCode fans, so when we see C presented
as an alternative, the notion of having to do that level of tedious
bit-counting and then waiting for a compiler compels us to make the text
equivalent of raspberry sounds. :)
In this particular case, the code you presented is likely very similar
to the code already in LiveCode for the built-in binaryDecode function.
But in LiveCode, we not only have the advantage of being able to access
it directly in the scripting language right now, but it also runs on all
7 of the platforms LiveCode supports.
This is similar in some respects to your earlier suggestion that "we
need to have the NSFIleManager". If you review the LiveCode source
code you'll find it often uses the standard APIs on each of the
platforms it supports, but as scripters we're insulated from having to
deal with the low-level implementation details like memory allocation
and such, with the LiveCode engine providing high-level access to those
OS routines. The core problem there wasn't in LiveCode's language at
all, but merely the need to do thorough error-checking for inaccessible
file system objects, as would be the case in any language, even C.
Your familiarity with C may put you in a good position to help with the
source code, if you're inclined to consider it. The repository is here:
<https://github.com/runrev/livecode>
If nothing else, I think you'll be impressed with the thorough job the
team has been doing to provide robust and efficient access to low-level
OS routines from the comfort of a scripting language.
--
Richard Gaskin
Fourth World Systems
Software Design and Development for the Desktop, Mobile, and the Web
____________________________________________________________________
ambassa...@fourthworld.com http://www.FourthWorld.com
_______________________________________________
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode
