Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

code massaging #11

Open
bnemec opened this issue Apr 8, 2012 · 0 comments
Open

code massaging #11

bnemec opened this issue Apr 8, 2012 · 0 comments

Comments

@bnemec
Copy link
Member

bnemec commented Apr 8, 2012

I'm assuming that we'll have some code massaging in addition to the meta-data, do deal with thing like {} in VAST (where Monticello Importer comments out the code and adds an exception stub). Or is the expectation that file-out code is always dialect neutral?

I've started on the port of PDF4Smalltalk 'Values' package from VW to VAST and I'm using it as a test bed for what I think I'll need on the VAST side. That package has few of the namespace and code issues that the PDF and Fonts package have, but it's a good start.

Are we advocating the use of Grease? We've had some discussion on the PDF4Smalltalk forum about the best 'dialect neutral code' technique. I like using Grease to avoid things like #asString variations, but there is a concern that having Grease as a pre-req (too big, perhaps?). My bias is to use Grease, probably because I do a lot of cross-dialect Seaside code (VW & VAST).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant