Re: [cc65] .import struct link_node

From: Steve Davison <64subnet1gmail.com>
Date: 2010-04-27 23:34:08
Apr 27 at 11:54 AM, Spiro Trikaliotis <ml-cc65@trikaliotis.net> wrote:
>
> Wolfgang Moser came up with another idea to do this in cbmforng
> (part of OpenCBM):
>
> C stub:
> http://opencbm.cvs.sourceforge.net/viewvc/opencbm/cbm4win/cbmforng/cbmforng.h?revision=1.2&view=markup
>
> Assembler stub (lines up to 84):
> http://opencbm.cvs.sourceforge.net/viewvc/opencbm/cbm4win/cbmforng/cbmforng.a65?revision=1.6&view=markup
>
> The header definitions:
> http://opencbm.cvs.sourceforge.net/viewvc/opencbm/cbm4win/cbmforng/cbmforng.idh?revision=1.4&view=markup

Now THAT is very interesting.  However I have a number of
suggestions that could make it _far_ more legible and
usable:

 - Instead of _CMT(str) macro consuming str, how about a _CMT()
   mac that turns the just inserts a ';' or a '//' ?
 - In order to be more than a parlor trick, I think you would
   have to have a full, standard set of macros, a la OCTETDECL,
   that are predefined in a library.  Lets everyone speak the
   same language, and avoids a lot of reinvention.
 - (..continued..) The language-specific macro defines should
   not be duplicated in every file that needs an .idh include,
   they should be in the .idh file itself.  More encapsulated,
   less clutter, less prone to errors.
 - Further, they wouldn't actually be defined in the .idh files
   themselves; the .idh would simply include the standard macro
   library as described above.  The really neat part is that
   getting the definitions for the appropriate language could
   be accomplished using Christian's method.
 - What is an octet array anyway?  Is it just a half-sized
   version of the good old hexadectet array?  Ah, now it's
   perfectly clear.  (sorry, I coludn't leave that one well
   enough alone.  :p


> (Ok, ok, he invaded the namespace of the C compiler... ;))
Could you clue me in a bit on this one?


//////// THIS IS COOL... /////////
If you haven't done it already, take Christian's duplicitous
header code and look at it with syntax highlighting, both C
and assembler.  It's kinda like turning on 2 different neon
signs that are under camouflage.

( I also viewed the code in "cascading style sheet" high-
lighting... I'll just say it was ... interesting.  Just not
_really_ interesting.  8-D )

Composing email in a C editor is also ... colorful.

// Steve
----------------------------------------------------------------------
To unsubscribe from the list send mail to majordomo@musoftware.de with
the string "unsubscribe cc65" in the body(!) of the mail.
Received on Tue Apr 27 23:34:50 2010

This archive was generated by hypermail 2.1.8 : 2010-04-27 23:34:52 CEST