On 2014-05-15 13:26, Marius Liebenberg wrote:
> On 2014-05-15 13:10, andy pugh wrote:
>> On 15 May 2014 12:00, Marius Liebenberg <[email protected]> wrote:
>>> Now that frigging sucks man :(
>>> If I dont use the HAL pins it works but if I try to use any pin it
>>> falls. So much for writing modular reusable code. What do people do,
>>> write in native C instead of the comp framework?
>> It depends on what the function has to do.
>>
>> If you consider the pins as local variables to the FUNCTION(_)
>> function then I believe you can do anything that you would normally
>> do, but you need to pass the pins to the functions as values or
>> pointers, not treat them as globals.
> I will try this.

The results remain the same. Fault with vec=14, signal=11, ip= xxxxx
>> For anything "clever" it is probably better to write the component in
>> C, especially for any component that creates pins on the fly according
>> to input arguments. (of course then you also have to manually write
>> the manpage, which is often more painful than the coding.)
> The man page can be done with a comp that only contains the defines and
> framework. The clever code is in the C file than.
>

-- 

Regards /Groete

Marius D. Liebenberg
+27 82 698 3251
+27 12 743 6064
QQ 1767394877


------------------------------------------------------------------------------
"Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE
Instantly run your Selenium tests across 300+ browser/OS combos.
Get unparalleled scalability from the best Selenium testing platform available
Simple to use. Nothing to install. Get started now for free."
http://p.sf.net/sfu/SauceLabs
_______________________________________________
Emc-developers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/emc-developers

Reply via email to