Dear Associates,
Please Respond to [EMAIL PROTECTED] <[EMAIL PROTECTED]>*
If you can find matching candidates for these jobs we can proceed right
away. All required skills must be in job description.
**
**
*
*
*Senior BaaN Business Systems Analyst or Developer *
Location : OH
Duration : 4 Months
Hourly Rate : OPEN
Required :
**This is a very old ERP technology I realize but give it a shot and let me
know if you have anyone.
I am not going to hold you to a rate just let me see anyone who has this
technology.www.diebold.com)
Diebold Global IT has a contractor need for one
(1) * Senior BaaN Business Systems Analyst or Developer
**Responsible* for* functional analysis*, *technical development* and *end
user support* of *Diebold's BaaN ERP* environment (*version Baan 4c*)..
The candidate is required to have at least *5 years experience* with the
following a*pplications within BaaN: *
Module Table PrefixTable Prefix TransactionsTransactions Table
PrefixTable Prefix TransactionsTransactions
Purchasing tdpur*
Receipts
PO matches to invoices Purchase orders
Accounts Payable tfacp* ALL invoices, both matched and direct
Purchase orders
Accounts Payable tfacp* ALL
that is, the
data is out of sync.
this one looks better:
ComponentLikeModel subclasses
do: [:each | each superclass: ComponentLikeModel superclass.
ComponentLikeModel superclass addSubclass: each.
ComponentLikeModel removeSubclass: each].
But when I recompile the changed classes, it freezes the system:
toRecompile := ComponentLikeModel subclasses.
ComponentLikeModel subclasses
do: [:each | each superclass: ComponentLikeModel superclass.
ComponentLikeModel superclass addSubclass: each.
ComponentLikeModel removeSubclass: each].
toRecompile do: [:cls | cls withAllSubclassesDo: [:each | each
compileAll]]
no idea.. to tired. maybe use the ClassBuilder? I think it's there
precisely because
mutating class structure is so easy to get wrong...
Marcus
--
Marcus Denker -- [EMAIL PROTECTED]
http://www.iam.unibe.ch/~denker
_______________________________________________
Pharo-project mailing list
[email protected]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
