Why not have a format_asm library? This breaks the rule of Jallib to keep it all JAL code, but it is clear that it is asm.
Matt. On May 8, 3:42 am, vasile surducan <[email protected]> wrote: > On Sat, May 7, 2011 at 8:22 AM, mattschinkel <[email protected]>wrote: > > > > > Avoid the use of inline Assembler. If you cannot do without it... > > > I do agree on this, however we could allow inline assembler with > > processor "IF" statements. But this would make a long messy file. > > and a shortest hex file I guess... > everything is word, dword, sword or whatever is usually create huge files. > > in my opinion, avoiding assembler can be a problem of the jallib as long the > jallib files which are indeed well structured and nice (from a pure software > point o view) are creating huge and messy assembler files and hex files > too... > > From this perspective can be nonsense to talk about using well structured > source code, as long the compiled code is a mess... > > Vasile -- You received this message because you are subscribed to the Google Groups "jallib" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/jallib?hl=en.
