Em 26/9/2011 04:47, Forrest Christian escreveu:
> To tonight, CCS PIC-C has irritated me once again.   Basically had an=20
> almost impossible time hunting down a missing #endif (actually had typed=
=20
> it as #end instead).   This was primarily due to the preference of CCS=20
> to use a single compilation unit, with multiple files being handled with=
=20
> #includes..... and as such it was hiding the file that I had typoed in...
>
> And yes, I know that CCS supposedly supports multiple compilation units=20
> but I seem to recall that the last time I tried to switch my code to=20
> multiple compilation units - well, let's just say it went down in=20
> flames. =20


Same for me. Some months ago I posted here about it. One of my clients
with a huge application had to do the #include thing.
The system became unmanageable.


> Add to that that my PIC-C maintenance is due again, to the tune=20
> of $250 per year... and I've about had it with production code living in=
=20
> PIC-C.
>
> At this point, all the new code is going into at least a PIC18 - so I=20
> don't really need the PIC16 compiler which is where this code=20
> started...  BUT, the one thing which is keeping me from doing this is=20
> the dire warning when you try to start MPLAB a second time on a machine:
>
> "MPLAB IDE is already running on this machine.  It is not recommended to=
=20
> run multiple simultaneous instances of MPLAB IDE".


I simply ignore the warning.


> The problem is that I am regularly writing code that talks between two=20
> pics - the 'master' is an 18F which has it's code in MPLAB, and the=20
> 'slave' generally is written in PIC-C.   And often I'm toggling between=20
> the two for debugging purposes.    So I really need two copies of MPLAB,=
=20
> and possibly two debuggers running, and well two of everything.


I know that one ICD2 plus one ICD3 works OK, I already tested. I
remember reading somewhere that two of the same don't work together.


> And I really don't want to play either the multiple machine or multiple v=
m=20
> game....


That's a safer way for two debuggers of the same model.


> So....  I'm wondering what dire things are going to happen if I ignore=20
> that warning - or more specifically what it's warning about.   Does=20
> anyone have any experience running a couple of copies of MPLAB on a machi=
ne?
>
> Thanks.
>
> -forrest


I didn't get any specially bad side-effects.


Isaac

--=20
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist
.