Hi Carlo,
I believe it is more appropriate to include it within ocs! Actually i
have neve understood why you initially suggested me to make a separate
package...
What you mean with glitches in the demos?

Cheers,
Marco


2012/1/12 c. <carlo.defa...@gmail.com>:
>
> On 12 Jan 2012, at 09:18, Marco Merlin wrote:
>
>> Hi everyone,
>> I have written a small package, that I would like to make available on
>> the octave forge repository. It is a parser meant to be used with the
>> already existent package ocs (octave circuit simulator), to allow for
>> use a spice-like syntax to describe the circuits.
>>
>> The package includes a small demo (spice2ocs_demo.m), along with the
>> main source code (prs_spice.m), which emulates the original test cases
>> included with ocs, using the supported spice syntax (.spc files). I
>> have tried to briefly describe the supported syntax in the README.txt
>> file
>>
>> The file is a simple archive, not an installable octave package
>> Those are credentials for my Sourceforge Account:
>>
>> User ID
>> 2819681
>> Login Name (User Name)
>> batman52
>>
>> I hope to make this available for someone else to use, as I had been
>> working on this a while ago and I am not sure how much time I could
>> spend on it in the future.
>>
>> Regards,
>>
>> Marco Merlin
>
>
> Hi Marco,
>
> It's been really a long time!
> your file looks great, I made a few style changes, added the demo
> inside the function according to the Octave coding guidelines and
> I also fixed a couple of glitches in the demos.
> The modified function is attached, for me it is fine to commit this
> function either inside OCS or as a separate package, I'll leave the
> choice to you.
>
> c.
>
>
>
>
>
>
>

------------------------------------------------------------------------------
RSA(R) Conference 2012
Mar 27 - Feb 2
Save $400 by Jan. 27
Register now!
http://p.sf.net/sfu/rsa-sfdev2dev2
_______________________________________________
Octave-dev mailing list
Octave-dev@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/octave-dev

Reply via email to