Jared Putnam wrote:
--- Patrick McNamara <[EMAIL PROTECTED]> wrote:
That should be quite doable. Something like
.polarity v=+, h=-, d=+ ...
Good point. And since d will always be +, let's make + the
default.
I was thinking along the lines of
vsync assert high
but that works. Is the space between items in the list optional?
No, the space is not necessary, it was simply for readability. On the
other note, as much typing as is required to get things done in
assembler for any CPU, you will find that programmers writing such like
to type as absolutely little as possible. :) Obviously I can't speak
for everyone, just an observation.
I fixed a few bugs
along the way too.
I was a little worried about bugs. Your script is a little monolithic
for my tastes; can you vouch for its robustness? I don't know Perl at
all, so I can't just look at it.
No, I can't vouch for it's robustness. It was designed to produce
proper output for the "seemingly" proper input I was giving it. One
thing to consider is that we are talking about a compiler for a video
controller that will never have more than 512 lines, and will probably
have very little hand written code beyond the functional blocks we use
to build the actual video routine when someone sets the video mode. I
was looking at Tim's original program and trying to figure out a way to
work with the video controller model without having to manually compile
a program and convert it to Verilog code. So, I put together the
simplest chunk of code I could that served that purpose and generated
decent output.
Atilla set me up with SVN access. When I get a spare moment, I'll
commit the assembler code. Suggestions on where to put it in the
directory hierarchy? Perhaps /trunk/tools/bin? What about example
program code, where should it go?
Should I abandon my attempt at an assembler and focus on yours? I was
working on one in Haskell, and I'm aware of the problems inherent in
that...
That is up to you. I don't intend to put a whole lot more effort into
the program. It does what I need it to and works reasonably well for
someone else who is careful using it. I'll probably fix bugs as I find
them, but I'm not going to put lots of effort into syntax checking or
optimization or multiple level substitution or such things. If "We" or
you feel we need a full blown compiler, by all means please continue.
As a note, I don't know Haskell, so I would be in the same situation. I
certainly wasn't intending to squash your project. :) In true Open
Source style, I had a need and wrote a program to fill it, then decided
to share it with the community in all it's crappy glory.
Patrick M
_______________________________________________
Open-graphics mailing list
[email protected]
http://lists.duskglow.com/mailman/listinfo/open-graphics
List service provided by Duskglow Consulting, LLC (www.duskglow.com)
