Menu

#36 RFE: Split irrecord into library + client

Future
closed
nobody
irrecord (2)
fixed,
2015-01-09
2014-08-29
Alec Leamas
No

We need to split irrecord into a separate library + a client. This way we will be able to test things in an automated way. It's also the foundations if anyone steps up to write a GUI.

This is a big change, and should probably not go into next release, Marking as 2.0 (for now to be interpreted as "future")

Related

Tickets: #24

Discussion

  • Alec Leamas

    Alec Leamas - 2014-08-29
    • summary: Split irrecord into library + client --> RFE: Split irrecord into library + client
     
  • Alec Leamas

    Alec Leamas - 2014-10-08

    At a closer look, this doesn't really seems feasible. Another approach might be to refactor the output and perhaps also input parts as function pointers, keeping the control flow within current irrecord.

     
  • Alec Leamas

    Alec Leamas - 2015-01-09
    • status: open --> need-info
    • Resolution: --> fixed,
     
  • Alec Leamas

    Alec Leamas - 2015-01-09

    Making it a return-codes based API works. Fixed in [b0b70d]

     

    Related

    Commit: [b0b70d]

  • Alec Leamas

    Alec Leamas - 2015-01-09
    • status: need-info --> closed
     

Log in to post a comment.

Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.